-
Notifications
You must be signed in to change notification settings - Fork 44
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
Update conformance model #478
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good idea!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I like the way this is going!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is great
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👍
This PR develops the under-specified
#conformance
model. Resolves #282 .The work herein follows the guidelines in https://www.w3.org/TR/spec-variability/ and https://www.w3.org/TR/qaframe-spec/ , and applies http://www.w3.org/ns/spec# . Future PRs will describe the other dimensions of variability and more specificity as needed (see also #480 ).
The table below can be used by reviewers to look up the changes introduced by this PR:
1
: No changes to text content2
: Corrections that do not affect conformance3
: Corrections that do not add new features (specifically "clears up an ambiguity or under-specified part of the specification...")4
: Changes that add a new functionality, element, etc.5
: Changes to the contents of a registry table.#conformance
#normative-informative-content
#normative-informative-sections
#requirement-levels
#advisement-levels
#classes-of-products
#Server
#Client
#specification-category
#interoperability
To simplify the review process, this PR focuses on the
#conformance
section and leaves out updates intended to be throughout the specification corresponding to these changes.So, reviewers may want to note that changes that are omitted here are included in PR #479 - intended to "fix" the current requirements' subject to use the new
#Server
and#Client
concepts as defined by the Solid Protocol (replacesspec:Server
andspec:Client
.Any change requests pertaining to Spec Terms should be followed up at solid/vocab#84 .
To move this PR forward in a timely fashion, I suggest reviews focus on human-readable content and get back to RDF bits when desired. We can follow up with changes to the RDF after this PR.
Preview | Diff