Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[wg/solid] describe deliverables and their dependencies more precisely #453

Open
pchampin opened this issue Oct 11, 2023 · 1 comment
Open
Assignees
Labels
AC-review Raised during the AC review phase, or otherwise intended to be treated then. formal-objection Formal objection from AC Review

Comments

@pchampin
Copy link
Contributor

Beyond the main deliverable ("Solid Protocol v1.0") adopted from the CG,
the charter should describe in more detail how it will deal with the various dependencies of that document:

  • which ones are meant to be adopted by the WG as other REC-track documents, and
  • how the WG intends to deal with other normative references with an insufficient level of maturity.

From https://lists.w3.org/Archives/Public/public-new-work/2023Oct/0007.html

  • The one normative deliverable Solid Protocol (per
    https://www.w3.org/2023/09/proposed-solid-wg-charter.html#normative) has
    dependencies
    (https://www.w3.org/2023/09/proposed-solid-wg-charter.html#dependencies) on
    specs that are all currently only in a CG and are thus unlikely to make it
    to CR or REC any time soon thus blocking progress beyond Working Draft
    (WD). It is my understanding that normative references in W3C REC-track
    documents MUST only refer to (normatively depend on) specifications at or
    at most one maturity level below. E.g. a WD can depend on EDs, but a
    Candidate Recommendation (CR) can only depend on WDs and above. Without a
    concrete plan for reducing dependencies or advancing those dependencies
    along a standards track, this appears to be a blocking issue for the one
    normative deliverable.
  • The Dependencies section
    (https://www.w3.org/2023/09/proposed-solid-wg-charter.html#dependencies) is
    misleading. That section says "Depending on the Working Group progress,
    including consideration for adequate implementation experience, the Group
    will also produce W3C Recommendations for the following documents". It is
    misleading to only put these documents in a Dependencies section. The prose
    "the Group will also produce W3C Recommendations" seems to imply these are
    actually all additional normative deliverables within scope of the Charter,
    yet they are explicitly listed outside of the Normative Specifications
    section.

and other reviews (member-visible only)

@pchampin pchampin added AC-review Raised during the AC review phase, or otherwise intended to be treated then. formal-objection Formal objection from AC Review labels Oct 11, 2023
@pchampin pchampin self-assigned this Oct 11, 2023
@pchampin pchampin changed the title [wg/solid] describe deliverable and their dependencies more precisely [wg/solid] describe deliverables and their dependencies more precisely Oct 11, 2023
@pchampin
Copy link
Contributor Author

This clarification also concerns the reference to Solid QA in the success criteria.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
AC-review Raised during the AC review phase, or otherwise intended to be treated then. formal-objection Formal objection from AC Review
Projects
None yet
Development

No branches or pull requests

1 participant