From 031f07d11367e5ab42a1e98287788278f567dbe4 Mon Sep 17 00:00:00 2001
From: Ivan Herman Credential Subject
credentialSubject
property is defined as
a set of objects that MUST contain one or more claims that are each related to a
@@ -1569,7 +1569,7 @@ issuer
property MUST be either a
URL or an object containing an id
property. It is
@@ -1650,7 +1650,7 @@ validFrom
property MUST be
an [XMLSCHEMA11-2]
@@ -1660,7 +1660,7 @@ credentialSubject
property becomes valid.
validUntil
property MUST be an
[XMLSCHEMA11-2]
@@ -1896,7 +1896,7 @@ credentialStatus
property MUST
include the following:
@@ -1996,14 +1996,14 @@ VerifiablePresentation
, but additional types MAY be included. The
related normative guidance in Section MUST be followed.
verifiableCredential
property MAY be present. The value
MUST be an array of one or more verifiable credentials, or of data
derived from verifiable credentials in a cryptographically
verifiable format.
holder
property. If present, the value MUST be either a URL or an object
@@ -2903,7 +2903,7 @@ refreshService
property MUST be one or more
refresh services that provides enough information to the recipient's software
@@ -2991,7 +2991,7 @@ termsOfUse
property MUST specify one or
more terms of use policies under which the creator issued the credential
@@ -3154,7 +3154,7 @@ evidence
property MUST be one or more
evidence schemes providing enough information for a verifier to determine
diff --git a/vocab/credentials/v2/template.html b/vocab/credentials/v2/template.html
index 3e529b349..332e3943e 100644
--- a/vocab/credentials/v2/template.html
+++ b/vocab/credentials/v2/template.html
@@ -133,7 +133,6 @@
archives).
-
This specification makes use of the following namespaces:
@@ -157,6 +156,28 @@All terms in this section are + reserved. + Implementers may use these properties, but should expect them and/or their meanings to change during the process to + normatively specify them. +
+ ++ In general the terms, i.e., properties and classes, are formally specified in Recommendation Track documents published by the W3C Verifiable Credentials Working Group or, for some deprecated or reserved terms, in Reports published by the W3C Credentials Community Group. In each of those cases the term description in this document contains a link to the specification itself (and the `rdfs:definedBy` property is used in the RDFS representations to refer to the formal specification). +
++ There are cases, however, when a local explanation is necessary to complement, or to replace, a reference to an external specification. This is the case when the term is necessary to provide a consistent structure to the RDFS vocabulary like, for example, when the term defines a common supertype for class instances that are used as objects of specific properties, or when RDF Graphs are involved. For such cases those extra definitions are included in the current document (and the `rdfs:comment` property is used to include them in the RDFS representations). +
+This specification makes use of the following namespaces:
@@ -141,7 +150,7 @@All terms in this section are reserved. @@ -179,7 +188,7 @@
All terms in this section are deprecated, and are only kept in this vocabulary for backward compatibility.
- In general the terms, i.e., properties and classes, are formally specified in Recommendation Track documents published by the W3C Verifiable Credentials Working Group or, for some deprecated or reserved terms, in Reports published by the W3C Credentials Community Group. In each of those cases the term description in this document contains a link to the specification itself (and the `rdfs:definedBy` property is used in the RDFS representations to refer to the formal specification).
+ In general, the terms — i.e., the properties and classes — used in the VCDM are formally specified in Recommendation Track documents published by the W3C Verifiable Credentials Working Group or, for some deprecated or reserved terms, in Reports published by the W3C Credentials Community Group. 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.
- There are cases, however, when a local explanation is necessary to complement, or to replace, a reference to an external specification. This is the case when the term is necessary to provide a consistent structure to the RDFS vocabulary like, for example, when the term defines a common supertype for class instances that are used as objects of specific properties, or when RDF Graphs are involved. For such cases those extra definitions are included in the current document (and the `rdfs:comment` property is used to include them in the RDFS representations).
+ 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 RDF Graphs 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).
All terms in this section are
reserved.
- Implementers may use these properties, but should expect them and/or their meanings to change during the process to
- normatively specify them.
+ Implementers may use these properties, but should expect them and/or their meanings to change during the process of
+ normatively specifying them.
New applications should not use them.
diff --git a/vocab/credentials/v2/vocabulary.yml b/vocab/credentials/v2/vocabulary.yml
index f425a22fc..bae565b04 100644
--- a/vocab/credentials/v2/vocabulary.yml
+++ b/vocab/credentials/v2/vocabulary.yml
@@ -59,6 +59,7 @@ class:
- id: VerifiablePresentation
defined_by: https://www.w3.org/TR/vc-data-model-2.0/#presentations
label: Verifiable presentation
+ comment: A Presentation is data derived from one or more Credentials, issued by one or more `issuers`, that is shared with a specific `verifier`. A Verifiable Presentation is a tamper-evident Presentation encoded in such a way that authorship of the data can be trusted after a process of cryptographic verification. Certain types of verifiable presentations might contain data that is synthesized from, but do not contain, the original verifiable credentials (for example, zero-knowledge proofs).
property:
- id: credentialSchema
From 45cabb74a1edb5b41a5103683bccf1d43aa3b704 Mon Sep 17 00:00:00 2001
From: Ivan Herman Specification of terms
Reserved terms
Specification of terms
In general, the terms — i.e., the properties and classes — used in the VCDM are formally specified in Recommendation Track documents published by the W3C Verifiable Credentials Working Group or, for some deprecated or reserved terms, in Reports published by the W3C Credentials Community Group. 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.
- 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 RDF Graphs 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). + 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 RDF Graphs 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).
All terms in this section are reserved. - Implementers may use these properties, but should expect them and/or their meanings to change during the process of - normatively specifying them. + Implementers may use these properties, but should expect them and/or their meanings to change during the process to + normatively specify them.
- +All terms in this section are deprecated, and are only kept in this vocabulary for backward compatibility. +
All terms in this section are deprecated, and are only kept in this vocabulary for backward compatibility.
New applications should not use them.