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

Revise conformance section #89

Closed
VirginiaBalseiro opened this issue Apr 9, 2023 · 1 comment · Fixed by #98
Closed

Revise conformance section #89

VirginiaBalseiro opened this issue Apr 9, 2023 · 1 comment · Fixed by #98
Assignees

Comments

@VirginiaBalseiro
Copy link
Member

No description provided.

@VirginiaBalseiro VirginiaBalseiro self-assigned this Apr 9, 2023
@csarven
Copy link
Member

csarven commented Jun 2, 2023

Use the Conformance sections from https://solidproject.org/TR/protocol#conformance or https://solidproject.org/TR/notifications-protocol#conformance as template.

  1. Normative and Informative Content -- this section can be copy/pasted for starters.
  2. Specification Category -- copy/paste but have a look at the concepts under http://www.w3.org/ns/spec#SpecificationCategory .
  3. Classes of Products -- work on this section alongside the Terminology section ( Add Terminology section #21 ). Reuse terms from the Terminology section. Have a look at http://www.w3.org/ns/spec#ClassesOfProducts to reuse but it should probably be new/specific concepts where the Spec Terms' concept could be a broadMatch. See notifications-protocol's source
  4. Interoperability -- pair/set of classes of products that are intended interop.

If this section is nailed down well, the rest of the spec will "write itself"(TM). I promise! :) There'll surely be revisions on the concepts and descriptions, but everything will make a lot of sense. Seeing the spec as it truly is.

matrix-seeing-it-as-it-truly-is

(I'll detail the above in solid/specification CONTRIBUTING.md later)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants