@@ -4171,81 +4171,55 @@ <h3>Securing Mechanism Specifications</h3>
41714171< h2 > Syntaxes</ h2 >
41724172
41734173< p >
4174- The data model as described in Sections
4175- [[[#core-data-model ]]], [[[#basic -concepts]]], and
4176- [[[#advanced-concepts]]] is the canonical structural representation of
4177- a [=verifiable credential=] or [=verifiable presentation=]. All
4178- serializations are representations of that data modelin a specific format. This
4179- section specifies how thedata model is realized in JSON-LD for
4180- `application/vc`, the base media type for Verifiable Credentials.
4181- Although syntactic mappings are only provided for JSON-LD, applications and
4182- services can use any other data representation syntax (such as XML, YAML, or
4183- CBOR) that is capable of being mapped back to `application/vc`. As the
4184- [=verification=] and [=validation=] requirements are defined in terms of
4185- the data model, all serialization syntaxes have to be deterministically
4186- translated to the data model for processing, [=validation=], or comparison.
4174+ The data model as described in Sections [[[#core-data-model]]],
4175+ [[[#basic-concepts ]]],and [[[#advanced -concepts]]] is the canonical structural
4176+ representation of a [=verifiable credential=] or [=verifiable presentation=].
4177+ All syntaxes are representations of that data model in a specific format. This
4178+ section specifies how the data modelis serialized in JSON-LD for
4179+ `application/vc` and `application/vp`, thebase media types for [=verifiable
4180+ credentials=] and [=verifiable presentations=], respectively. Although syntactic
4181+ mappings are only provided for JSON-LD, applications and services can use any
4182+ other data representation syntax (such as XML, YAML, or CBOR) that is capable of
4183+ being mapped back to `application/vc` or `application/vp `. As the
4184+ [=verification=] and [=validation=] requirements are defined in terms of the
4185+ data model, all serialization syntaxes have to be deterministically translated
4186+ to the data model for processing, [=validation=], or comparison.
41874187</ p >
41884188
41894189< p >
41904190The expected arity of the property values in this specification, and the
41914191resulting datatype which holds those values, can vary depending on the property.
4192- If present, the following properties are represented as a single value:
4193- </ p >
4194-
4195- < ul >
4196- < li >
4197- `id` [=property=]
4198- </ li >
4199- < li >
4200- `issuer` [=property=]
4201- </ li >
4202- < li >
4203- `validFrom` [=property=]
4204- </ li >
4205- < li >
4206- `validUntil` [=property=].
4207- </ li >
4208- </ ul >
4209-
4210- < p >
4211- All other properties, if present, are represented as either a single value
4212- or an array of values.
4192+ If present, the following properties are represented as a single value: `id`
4193+ (Section [[[#identifiers]]]), `issuer` (Section [[[#issuer]]]), and
4194+ `validFrom`/`validUntil` (Section [[[#validity-period]]]). All other properties,
4195+ if present, are represented as either a single value or an array of values.
42134196</ p >
42144197
42154198< section >
42164199< h3 > JSON-LD</ h3 >
42174200
42184201< p >
4219- JSON-LD is a JSON-based format [[!JSON-LD11]] used to serialize
4202+ This specification uses [[[JSON-LD11]]] to serialize the data model described in
4203+ this specification. JSON-LD is useful because it enables the expression of the
4204+ < a href ="#core-data-model "> graph-based data model</ a > on which [=verifiable
4205+ credentials=] are based,
4206+ < a href ="https://en.wikipedia.org/wiki/Semantic_technology "> machine-readable
4207+ semantics</ a > , and is also useful when extending the data model (see Sections
4208+ [[[#core-data-model]]] and [[[#extensibility]]]).
4209+ </ p >
4210+
4211+ < p >
4212+ JSON-LD is a JSON-based format used to serialize
42204213< a href ="https://www.w3.org/TR/ld-glossary/#linked-data "> Linked Data</ a > . Linked
42214214Data is modeled using Resource Description Framework (RDF) [[?RDF11-CONCEPTS]].
42224215RDF is a technology for modeling graphs of statements. Each statement is a
42234216single< i > subject→property→value</ i > (also known as
42244217< i > entity→attribute→value</ i > ) relationship, which is referred to as a
42254218< a > claim</ a > in this specification. JSON-LD is a technology that enables the
42264219expression of RDF using idiomatic JSON, enabling developers familiar with JSON
4227- to write applications that consume RDF as JSON. In general, subjects are
4228- expressed as JSON objects with each property and value of the subject as a JSON
4229- key and value, respectively. See
4220+ to write applications that consume RDF as JSON. See
42304221< a data-cite ="?JSON-LD11#relationship-to-rdf "> Relationship of JSON-LD to RDF</ a >
42314222for more details.
4232- </ p >
4233- < p >
4234- JSON-LD is useful when extending the data model described in this
4235- specification. The concept of the
4236- < a href ="https://www.w3.org/TR/json-ld/#the-context "> JSON-LD context</ a >
4237- is described in detail in the JSON-LD specification and its use is
4238- elaborated on in Section [[[#contexts]]] and
4239- Section [[[#extensibility]]].
4240- </ p >
4241-
4242- < p >
4243- Multiple contexts MAY be used or combined to express any arbitrary information
4244- about [=verifiable credentials=] in idiomatic JSON. The base
4245- < a href ="https://www.w3.org/TR/json-ld/#the-context "> JSON-LD context</ a > for
4246- this specification is `https://www.w3.org/ns/credentials/v2`. The associated
4247- vocabulary document for the Verifiable Credentials Data Model is available at
4248- `https://www.w3.org/2018/credentials`.
42494223</ p >
42504224
42514225< section >