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.

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

Jump to bottom

Vocabulary improvement Phase 1 #1209

Merged
merged 9 commits into from
Jul 27, 2023
Merged

Vocabulary improvement Phase 1 #1209

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
9 commits
Select commit Hold shift + click to select a range
031f07d
Refreshed vocabulary, using back links to the main doc.
iherman Jul 19, 2023
9c7c0b0
Update the domain of validFrom/validUntil.
iherman Jul 20, 2023
e81155d
Update entries in vocabulary to match spec.
iherman Jul 21, 2023
1134b55
Fix editorial issues with v2 vocabulary.
iherman Jul 24, 2023
c885cfe
Fix missing prefix in TermsOfUse.
iherman Jul 25, 2023
4f48b5d
Add section on specification of terms.
iherman Jul 25, 2023
45cabb7
Fix grammar in specification of terms.
iherman Jul 26, 2023
bc5c957
Fix more grammar issues in template and vocabulary.
iherman Jul 26, 2023
ee9a7ff
Remove trailing space, fix grammar in vocabulary.
iherman Jul 19, 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
20 changes: 10 additions & 10 deletions index.html
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -1493,7 +1493,7 @@ <h3>Credential Subject</h3>
</p>

<dl>
<dt>credentialSubject</dt>
<dt><dfn id="defn-credentialSubject">credentialSubject</dfn></dt>
<dd>
The value of the <code>credentialSubject</code> <a>property</a> is defined as
a set of objects that MUST contain one or more claims that are each related to a
Expand Down Expand Up @@ -1569,7 +1569,7 @@ <h3>Issuer</h3>
</p>

<dl>
<dt><var>issuer</var></dt>
<dt><var id="defn-issuer">issuer</var></dt>
<dd>
The value of the <code>issuer</code> <a>property</a> MUST be either a
<a>URL</a> or an object containing an <code>id</code> <a>property</a>. It is
Expand Down Expand Up @@ -1650,7 +1650,7 @@ <h3>Validity Period</h3>
</p>

<dl>
<dt><var>validFrom</var></dt>
<dt><var id="defn-validFrom">validFrom</var></dt>
<dd>
If present, the value of the <code>validFrom</code> <a>property</a> MUST be
an [<a data-cite="XMLSCHEMA11-2#dateTime">XMLSCHEMA11-2</a>]
Expand All @@ -1660,7 +1660,7 @@ <h3>Validity Period</h3>
at which the information associated with the <code>credentialSubject</code>
<a>property</a> becomes valid.
</dd>
<dt><var>validUntil</var></dt>
<dt><var id="defn-validUntil">validUntil</var></dt>
<dd>
If present, the value of the <code>validUntil</code> <a>property</a> MUST be an
[<a data-cite="XMLSCHEMA11-2#dateTimeStamp">XMLSCHEMA11-2</a>]
Expand Down Expand Up @@ -1896,7 +1896,7 @@ <h3>Status</h3>
</p>

<dl>
<dt><var>credentialStatus</var></dt>
<dt><var id="defn-credentialStatus">credentialStatus</var></dt>
<dd>
If present, the value of the <code>credentialStatus</code> <a>property</a> MUST
include the following:
Expand Down Expand Up @@ -1996,14 +1996,14 @@ <h3>Presentations</h3>
<code>VerifiablePresentation</code>, but additional types MAY be included. The
related normative guidance in Section <a href="#types"></a> MUST be followed.
</dd>
<dt><var>verifiableCredential</var></dt>
<dt><var id="defn-verifiableCredential">verifiableCredential</var></dt>
<dd>
The <code>verifiableCredential</code> <a>property</a> MAY be present. The value
MUST be an array of one or more <a>verifiable credentials</a>, or of data
derived from <a>verifiable credentials</a> in a cryptographically
<a>verifiable</a> format.
</dd>
<dt><var>holder</var></dt>
<dt><var id="defn-holder">holder</var></dt>
<dd>
The <a>verifiable presentation</a> MAY include a <code>holder</code>
<a>property</a>. If present, the value MUST be either a <a>URL</a> or an object
Expand Down Expand Up @@ -2903,7 +2903,7 @@ <h3>Refreshing</h3>
</p>

<dl>
<dt><var>refreshService</var></dt>
<dt><var id="defn-refreshService">refreshService</var></dt>
<dd>
The value of the <code>refreshService</code> <a>property</a> MUST be one or more
refresh services that provides enough information to the recipient's software
Expand Down Expand Up @@ -2991,7 +2991,7 @@ <h3>Terms of Use</h3>
</p>

<dl>
<dt><var>termsOfUse</var></dt>
<dt><var id="defn-termsOfUse">termsOfUse</var></dt>
<dd>
The value of the <code>termsOfUse</code> <a>property</a> MUST specify one or
more terms of use policies under which the creator issued the <a>credential</a>
Expand Down Expand Up @@ -3154,7 +3154,7 @@ <h3>Evidence</h3>
</p>

<dl>
<dt><dfn>evidence</dfn></dt>
<dt><dfn id="defn-evidence">evidence</dfn></dt>
<dd>
The value of the <code>evidence</code> <a>property</a> MUST be one or more
evidence schemes providing enough information for a <a>verifier</a> to determine
Expand Down
50 changes: 40 additions & 10 deletions vocab/credentials/v2/template.html
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -133,7 +133,15 @@
<a href="https://lists.w3.org/Archives/Public/public-vc-comments/">archives</a>).
</p>
</section>
<section id="conformance"></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 @@ -142,40 +150,62 @@ <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>
</section>

<section id="property_definitions" class="term_definitions">
<h2>Property definitions</h2>
</section>

<section id="individual_definitions" class="term_definitions">
<h2>Definitions for individuals</h2>
</section>
</section>
</section>

<section id="reserved_term_definitions">
<h1>Reserved term definitions</h1>

<p>All terms in this section are
<a href="https://www.w3.org/TR/vc-data-model-2.0/#reserved-extension-points"><em><strong>reserved</strong></em></a>.
Implementers may use these properties, but should expect them and/or their meanings to change during the process to
normatively specify them.
iherman marked this conversation as resolved.
Show resolved Hide resolved
</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.
<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>New applications should not use them.
</p>

<section id="deprecated_class_definitions" class="term_definitions">
<h2>Deprecated classes</h2>
</section>

<section id="deprecated_property_definitions" class="term_definitions">
<h2>Deprecated properties</h2>
</section>

<section id="deprecated_individual_definitions" class="term_definitions">
<h2>Deprecated individuals</h2>
</section>
</section>
</section>



Expand Down
Loading