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

New specification category #27

Open
wants to merge 2 commits into
base: main
Choose a base branch
from
Open
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
88 changes: 51 additions & 37 deletions index.html
Original file line number Diff line number Diff line change
Expand Up @@ -952,47 +952,61 @@ <h3 property="schema:name">Namespaces</h3>
>
<h3 property="schema:name">Conformance</h3>
<div datatype="rdf:HTML" property="schema:description">
<p>
All assertions, diagrams, examples, and notes are
non-normative, as are all sections explicitly marked
non-normative. Everything else is normative.
</p>
<p>This section describes the <span about="" rel="spec:conformance" resource="#conformance">conformance model of the Type Index.</span>.</p>

<section id="normative-informative-content" inlist="" rel="schema:hasPart" resource="#normative-informative-content">
<h4 property="schema:name">Normative and Informative Content</h4>

<p>
The key words “MUST”, “MUST NOT”, “REQUIRED”, “SHALL”, “SHALL
NOT”, “SHOULD”, “SHOULD NOT”, “RECOMMENDED”, “MAY”, and
“OPTIONAL” are to be interpreted as described in
<a href="https://tools.ietf.org/html/bcp14">BCP 14</a>
[<cite><a class="bibref" href="#bib-rfc2119">RFC2119</a></cite
>] [<cite
><a class="bibref" href="#bib-rfc8174">RFC8174</a></cite
>] when, and only when, they appear in all capitals, as shown
here.
</p>
<div datatype="rdf:HTML" property="schema:description">
<p id="normative-informative-sections">
All assertions, diagrams, examples, and notes are
non-normative, as are all sections explicitly marked
non-normative. Everything else is normative.
</p>

<p>
Examples in this specification are introduced with the word "for example" or are set apart from the normative text with <code>class="example"</code>, like this:
</p>
<figure
class="example listing"
id="example"
rel="schema:hasPart"
resource="#example"
>
<p class="example-h">
<span>Example 1</span>
<p>
The key words “MUST”, “MUST NOT”, “REQUIRED”, “SHALL”, “SHALL
NOT”, “SHOULD”, “SHOULD NOT”, “RECOMMENDED”, “MAY”, and
“OPTIONAL” are to be interpreted as described in
<a href="https://tools.ietf.org/html/bcp14">BCP 14</a>
[<cite><a class="bibref" href="#bib-rfc2119">RFC2119</a></cite
>] [<cite
><a class="bibref" href="#bib-rfc8174">RFC8174</a></cite
>] when, and only when, they appear in all capitals, as shown
here.
</p>
<pre
about="#example"
property="schema:description"
typeof="fabio:Script"
>
<code>This is an example.</code>
</pre>
</figure>

</div>
</section>
<p>
Examples in this specification are introduced with the word "for example" or are set apart from the normative text with <code>class="example"</code>, like this:
</p>
<figure
class="example listing"
id="example"
rel="schema:hasPart"
resource="#example"
>
<p class="example-h">
<span>Example 1</span>
</p>
<pre
about="#example"
property="schema:description"
typeof="fabio:Script"
>
<code>This is an example.</code>
</pre>
</figure>

</div>
</section>

<section id="specification-category" inlist="" rel="schema:hasPart" resource="#specification-category" typeof="skos:ConceptScheme">
<h4 property="schema:name skos:prefLabel">Specification Category</h4>
<div datatype="rdf:HTML" property="schema:description">
<p property="skos:definition">The <span about="" rel="spec:specificationCategory" resource="#specification-category">Type Indexes </span> identify the following <cite><a href="https://www.w3.org/TR/spec-variability/#spec-cat" rel="dcterms:subject" resource="spec:SpecificationCategory">Specification Category</a></cite> to distinguish the types of conformance: <span rel="skos:hasTopConcept" resource="spec:NotationSyntax">notation/syntax</span>.</p>
</div>
</section>

</section>

<section
Expand Down