From 22e373048f96f18db8f7a8b71023dbcb1f28a924 Mon Sep 17 00:00:00 2001
From: Manu Sporny Data Schemas
If multiple schemas are present, validity is determined according to the
-processing rules outlined by each associated credentialSchema
+processing rules outlined by each associated credentialSchema
type
property.
+There are a number of digital credential formats that do not natively use the +data model provided in this document, but are aligned with a number of concepts +in this specification. At the time of publication, examples of these digital +credential formats include + +JSON Web Tokens (JWTs), + +CBOR Web Tokens (CWTs), +ISO-18013-5:2021 +(mDLs), + +AnonCreds, + +Gordian Envelopes, and + +Authentic Chained Data Containers (ACDCs). +
+ ++If conceptually aligned digital credential formats can be transformed into a +conforming document according to the rules provided in this section, they +are considered "compatible with the W3C Verifiable Credentials ecosystem". +A conforming document is either a verifiable credential serialized +as the `application/vc+ld+json` media type or a verifiable presentation +serialized as the `application/vp+ld+json` media type. Specifications that +describe how to perform transformations that enable compatibility with +the Verifiable Credentials ecosystem: +
+ ++Readers are advised that a digital credential is only considered +compatible with the W3C Verifiable Credentials ecosystem if it is a +conforming document and it utilizes at least one securing mechanism, as +described by their respective requirements in this specification. While some communities might call some digital +credential formats that are not conforming documents +"verifiable credentials", doing so does NOT make that digital credential +compliant to this specification. +
+ ++This property reservation might be deleted in favor of an existing section +in the specification if at least one specification with two independent +implementations are demonstrated by the end of the Candidate Recommendation +Phase. If that does not occur, this reservation will remain, but the existing +section in the specification will be removed. +See Verifiable Credential Confidence Methods. +
+This reserved property is at risk and will be removed from the specification if at least one specification with two independent implementations are not demonstrated by the end of the Candidate Recommendation Phase. +See Verifiable Credential Rendering Methods.
From cf429b194ff89ae255a70cf271aac45f703f96c1 Mon Sep 17 00:00:00 2001
From: Brent Zundel Reserved Extension Points
A property used for specifying one or more methods that a verifier
might use to increase their confidence that the value of an attribute in or of
a verifiable credential or verifiable presentation is accurate, including but not
-limited to attributes such `initialRecipient` (a/k/a `issuee`), `presenter`,
+limited to attributes such as `initialRecipient` (a/k/a `issuee`), `presenter`,
`authorizedPresenter`, `holder`, etc.
The associated vocabulary URL MUST be
`https://www.w3.org/2018/credentials#confidenceMethod`.
From 866b855c2305f9523c1dc6ab1d2237c2835061dc Mon Sep 17 00:00:00 2001
From: Ivan Herman