diff --git a/index.html b/index.html index 56999738e..17542ebb2 100644 --- a/index.html +++ b/index.html @@ -612,12 +612,11 @@
-This document also contains examples that contain JSON and JSON-LD content.
-Some of these examples contain characters that are invalid JSON, such as
+This document also contains examples that contain characters that are invalid JSON, such as
inline comments (//
) and the use of ellipsis (...
)
to denote information that adds little value to the example. Implementers are
cautioned to remove this content if they desire to use the information as
-valid JSON or JSON-LD.
+valid.
-Though this specification requires that a @context
property
-be present, it is not required that the value of the @context
-property be processed using JSON-LD. This is to support processing using
-plain JSON libraries, such as those that might be used when the
-verifiable credential is encoded as a JWT. All libraries or processors
-MUST ensure that the order of the values in the @context
-property is what is expected for the specific application. Libraries or
-processors that support JSON-LD can process the @context
-property using full JSON-LD processing as expected.
+This specification requires for a @context
property
+to be present; this property is defined by [[JSON-LD]].
{ @@ -2383,23 +2375,8 @@Extensibility
@@ -5220,11 +5186,9 @@ Semantic Interoperability
--This specification ensures that "plain" JSON and JSON-LD syntaxes are -semantically compatible without requiring JSON implementations to use a JSON-LD -processor. To achieve this, the specification imposes the following additional -requirements on both syntaxes: -
-
- -JSON-based processors MUST process the
-@context
key, ensuring the -expected values exist in the expected order for the credential type being -processed. The order is important because keys used in a credential, -which are defined using the values associated with@context
, are -defined using a "first defined wins" mechanism and changing the order might -result in a different key definition "winning". -- JSON-LD-based processors MUST produce an error when a JSON-LD context redefines any term in the active context. @@ -2418,17 +2395,6 @@
Semantic Interoperability
at the URL specified in the@context
property by JSON-LD implementers seeking interoperability. - --The requirements above guarantee semantic interoperability between JSON and -JSON-LD for terms defined by the
@context
mechanism. While JSON-LD -processors will use the specific mechanism provided and can verify that all -terms are correctly specified, JSON-based processors implicitly accept the same -set of terms without testing that they are correct. In other words, the context -in which the data exchange happens is explicitly stated for both JSON and -JSON-LD by using the same mechanism. With respect to JSON-based processors, this -is achieved in a lightweight manner, without having to use JSON-LD processing -libraries.Differences between Contexts, Types, and CredentialSchemas
omitting the subtype value could make it more difficult for verifiers to inform the holder which verifiable credential they require. When a verifiable credential has multiple subtypes, listing all of them in thetype
-property is sensible. While the semantics are the same in both a [[JSON]] and -[[JSON-LD]] representation, the usage of thetype
property in a -[[JSON-LD]] representation of a verifiable credential is able to enforce the semantics of the -verifiable credential better than a [[JSON]] representation of the same -credential because the machine is able to check the semantics. With [[JSON-LD]], +property is sensible. The usage of thetype
property in a +[[JSON-LD]] representation of a verifiable credential enables to enforce the semantics of the +verifiable credential because the machine is able to check the semantics. With [[JSON-LD]], the technology is not only describing the categorization of the set of claims, the technology is also conveying the structure and semantics of the sub-graph of the properties in the graph. In [[JSON-LD]], this represents the type of the node @@ -5236,12 +5200,10 @@Differences between Contexts, Types, and CredentialSchemas
The primary purpose of the
@context
property, from a [[JSON-LD]] perspective, is to convey the meaning of the data and term definitions of the -data in a verifiable credential, in a machine readable way. When encoding a pure -[[JSON]] representation, the@context
property remains mandatory and -provides some basic support for global semantics. The@context
+data in a verifiable credential, in a machine readable way. The@context
property is used to map the globally unique URLs for properties in verifiable credentials and verifiable presentations into short-form alias names, -making both the [[JSON]] and [[JSON-LD]] representations more human-friendly +making [[JSON-LD]] representations more human-friendly to read. From a [[JSON-LD]] perspective, this mapping also allows the data in a credential to be modeled in a network of machine-readable data, by enhancing how the data in the verifiable credential or verifiable