Skip to content

Vocabulary pruning and improvement phase 1 #127

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.

Sign up for GitHub

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

Merged
merged 3 commits into from
Jul 28, 2023
Merged

Vocabulary pruning and improvement phase 1 #127

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
16eb6a4
Done, ready for PR...
iherman Jul 21, 2023
59c7079
Update vocab/security/vocabulary.yml
iherman Jul 21, 2023
5fd45a3
Applied the editorial changes suggested by Ted
iherman Jul 26, 2023
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
28 changes: 14 additions & 14 deletions index.html
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -463,7 +463,7 @@ <h3>Proofs</h3>
verify the proof.
</dd>

<dt>proofPurpose</dt>
<dt><dfn class="lint-ignore">proofPurpose</dfn></dt>
<dd>
The reason the proof was created MUST be specified as a string that maps to a
URL [[URL]]. The proof purpose acts as a safeguard to prevent the proof from
Expand All @@ -484,13 +484,13 @@ <h3>Proofs</h3>
by a verifier during the verification process.
</dd>

<dt>created</dt>
<dt><dfn class="lint-ignore">created</dfn></dt>
<dd>
The date and time the proof was created MUST be specified as an
[[XMLSCHEMA11-2]] combined date and time string.
</dd>

<dt>domain</dt>
<dt id="defn-domain">domain</dt>
<dd>
The creator of a proof SHOULD include a string value that indicates its intended usage, which a verifier SHOULD use to ensure the proof was intended to be used by them. The
specification of the `domain` parameter is useful in challenge-response
Expand All @@ -501,15 +501,15 @@ <h3>Proofs</h3>
`b31d37d4-dd59-47d3-9dd8-c973da43b63a` (UUID).
</dd>

<dt>challenge</dt>
<dt id="defn-challenge">challenge</dt>
<dd>
A string value that SHOULD be included in a proof if a `domain` is specified.
The value is used once for a particular <a>domain</a> and window of time. This
value is used to mitigate replay attacks. Examples of a challenge value include:
`1235abcd6789`, `79d34551-ae81-44ae-823b-6dadbab9ebd4`, and `ruby`.
</dd>

<dt>proofValue</dt>
<dt><dfn class="lint-ignore">proofValue</dfn></dt>
<dd>
A string value that contains the data necessary to verify the digital proof
using the `verificationMethod` specified. The contents of the value MUST be a
Expand All @@ -520,7 +520,7 @@ <h3>Proofs</h3>
<a href="#add-proof">Add Proof Algorithm</a>.
</dd>

<dt>previousProof</dt>
<dt><dfn class="lint-ignore">previousProof</dfn></dt>
<dd>
An optional string value that identifies another <a>data integrity proof</a>
that MUST verify before the current proof is processed. This property is used
Expand Down Expand Up @@ -818,7 +818,7 @@ <h2>Verification Methods</h2>
</p>

<dl>
<dt>verificationMethod</dt>
<dt><dfn class="lint-ignore">verificationMethod</dfn></dt>
<dd>
<p>
The `verificationMethod` property is OPTIONAL. If present, the value
Expand Down Expand Up @@ -850,7 +850,7 @@ <h2>Verification Methods</h2>
<a>verification method</a> type SHOULD be registered in the Data Integrity Specification
Registries [TBD -- DIS-REGISTRIES].
</dd>
<dt>controller</dt>
<dt><span id="defn-controller">controller</span></dt>
<dd>
The value of the `controller` property MUST be a <a
data-cite="INFRA#string">string</a> that conforms to the [[URL]] syntax.
Expand Down Expand Up @@ -1155,7 +1155,7 @@ <h2>Authentication</h2>
</p>

<dl>
<dt>authentication</dt>
<dt id="defn-authentication">authentication</dt>
<dd>
The `authentication` property is OPTIONAL. If present, the associated
value MUST be a <a data-cite="INFRA#ordered-set">set</a> of one or more
Expand Down Expand Up @@ -1225,7 +1225,7 @@ <h2>Assertion</h2>
</p>

<dl>
<dt><dfn>assertionMethod</dfn></dt>
<dt><dfn id="defn-assertionMethod">assertionMethod</dfn></dt>
<dd>
The `assertionMethod` property is OPTIONAL. If present, the
associated value MUST be a <a data-cite="INFRA#ordered-set">set</a> of
Expand Down Expand Up @@ -1281,7 +1281,7 @@ <h2>Key Agreement</h2>
</p>

<dl>
<dt><dfn>keyAgreement</dfn></dt>
<dt><dfn id="defn-keyAgreement">keyAgreement</dfn></dt>
<dd>
The `keyAgreement` property is OPTIONAL. If present, the associated
value MUST be a <a data-cite="INFRA#ordered-set">set</a> of one or more
Expand Down Expand Up @@ -1332,7 +1332,7 @@ <h2>Capability Invocation</h2>
</p>

<dl>
<dt><dfn>capabilityInvocation</dfn></dt>
<dt><dfn id="defn-capabilityInvocation">capabilityInvocation</dfn></dt>
<dd>
The `capabilityInvocation` property is OPTIONAL. If present, the
associated value MUST be a <a data-cite="INFRA#ordered-set">set</a> of
Expand Down Expand Up @@ -1399,7 +1399,7 @@ <h2>Capability Delegation</h2>
</p>

<dl>
<dt><dfn class="lint-ignore">capabilityDelegation</dfn></dt>
<dt><dfn class="lint-ignore" id="defn-capabilityDelegation">capabilityDelegation</dfn></dt>
<dd>
The `capabilityDelegation` property is OPTIONAL. If present, the
associated value MUST be a <a data-cite="INFRA#ordered-set">set</a> of
Expand Down Expand Up @@ -1567,7 +1567,7 @@ <h3>DataIntegrityProof</h3>
<dd>
The `type` property MUST contain the string `DataIntegrityProof`.
</dd>
<dt>cryptosuite</dt>
<dt><dfn class="lint-ignore">cryptosuite</dfn></dt>
<dd>
The `cryptosuite` property MUST contain a string specifying the name of the
cryptosuite.
Expand Down
45 changes: 43 additions & 2 deletions vocab/security/template.html
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -124,6 +124,26 @@
<a href="https://lists.w3.org/Archives/Public/public-vc-comments/">archives</a>).
</p>
</section>
<section>
<h2>Specification of terms</h2>
<p>
In general, the terms &mdash; i.e., the properties and classes &mdash; used in the VCDM are formally specified in
Recommendation Track documents published by the <a href="https://www.w3.org/groups/wg/vc">W3C Verifiable Credentials
Working Group</a> or, for some deprecated or reserved terms, in Reports published by the <a
href="https://www.w3.org/groups/cg/credentials">W3C Credentials Community Group</a>. In each case of such external
definition, the term's description in this document contains a link to the relevant specification. Additionally, the
`rdfs:definedBy` property in the RDFS representation(s) refers to the formal specification.
</p>
<p>
In some cases, a local explanation is necessary to complement, or to replace, the definition found in an external
specification. For instance, this is so when the term is needed to provide a consistent structure to the RDFS
vocabulary, such as when the term defines a common supertype for class instances that are used as objects of
specific properties, or when <a href="https://www.w3.org/TR/rdf12-concepts/#section-rdf-graph">RDF Graphs</a> are
involved. For such cases, the extra definition is included in the current document (and the `rdfs:comment` property
is used to include them in the RDFS representations).
</p>
</section>

<section>
<h2>Namespaces</h2>
<p>This specification makes use of the following namespaces:</p>
Expand All @@ -132,7 +152,7 @@ <h2>Namespaces</h2>
</section>

<section id="term_definitions">
<h1>Term definitions</h1>
<h1>Regular terms</h1>

<section id="class_definitions" class="term_definitions">
<h2>Class definitions</h2>
Expand All @@ -147,8 +167,29 @@ <h2>Definitions for individuals</h2>
</section>
</section>

<section id="reserved_term_definitions">
<h1>Reserved terms</h1>

<p>All terms in this section are <em><strong>reserved</strong></em>.
Implementers may use these properties, but should expect them and/or their meanings to change during the process to
normatively specify them.
</p>

<section id="reserved_class_definitions" class="term_definitions">
<h2>Reserved classes</h2>
</section>

<section id="reserved_property_definitions" class="term_definitions">
<h2>Reserved properties</h2>
</section>

<section id="reserved_individual_definitions" class="term_definitions">
<h2>Reserved individuals</h2>
</section>
</section>

<section id="deprecated_term_definitions">
<h1>Deprecated term definitions</h1>
<h1>Deprecated terms</h1>

<p class="annoy">All terms in this section are <em><strong>deprecated</strong></em>, and are only kept in this vocabulary for backward compatibility.
<br><br>New applications should not use them.
Expand Down
Loading