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

Update conformance model #478

Merged
merged 1 commit into from
Nov 17, 2022
Merged

Update conformance model #478

merged 1 commit into from
Nov 17, 2022

Conversation

csarven
Copy link
Member

@csarven csarven commented Nov 5, 2022

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:

  • Target: Unit of information that's changed.
  • Correction class: https://www.w3.org/2021/Process-20211102/#correction-classes
    • 1: No changes to text content
    • 2: Corrections that do not affect conformance
    • 3: 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.
  • Note: A summary of the change.
Target Correction class Note
#conformance 2 Add leading text.
#normative-informative-content 1 Describes the kind of language used to express normative and informative content.
#normative-informative-sections 1 Referenceable
#requirement-levels 2 Uses explicit concepts for normative content.
#advisement-levels 2 Identifies concepts used for non-normative content.
#classes-of-products 3 Defines group of products that can implement the specification.
#Server 3 Defines concept.
#Client 3 Defines concept.
#specification-category 3 Identifies generic categories for the products that will implement the specification.
#interoperability 3 Defines kinds of interoperability between products.

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 (replaces spec:Server and spec: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

Copy link
Contributor

@RubenVerborgh RubenVerborgh left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good idea!

Copy link
Member

@matthieubosquet matthieubosquet left a 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!

Copy link
Member

@acoburn acoburn left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is great

Copy link
Member

@kjetilk kjetilk left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👍

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: Done
Development

Successfully merging this pull request may close these issues.

Include conformance criteria for Solid spec
6 participants