Skip to content

Remove JSON section in lieu of application/vc+ld+json. #1088

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

Merged
merged 3 commits into from
Apr 22, 2023
Merged

Remove JSON section in lieu of application/vc+ld+json. #1088

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
4631b46
Remove JSON section in lieu of `application/vc+ld+json`.
msporny Apr 16, 2023
654b694
Fix up section on base media type.
msporny Apr 22, 2023
3ef0175
Mention that JSON-LD compact form is used.
msporny Apr 22, 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
59 changes: 8 additions & 51 deletions index.html
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -3261,15 +3261,14 @@ <h2>Syntaxes</h2>
<a href="#advanced-concepts"></a> is the canonical structural representation of
a <a>verifiable credential</a> or <a>verifiable presentation</a>. All
serializations are representations of that data model in a specific format. This
section specifies how the data model is realized in JSON-LD and plain JSON.
Although syntactic mappings are provided for only these two syntaxes,
section specifies how the data model is realized in JSON-LD for
`application/vc+ld+json`, the base media type for Verifiable Credentials.
Although syntactic mappings are only provided for JSON-LD,
applications and services can use any other data representation syntax (such as
XML, YAML, or CBOR) that is capable of expressing the data model. As the
<a>verification</a> and <a>validation</a> requirements are defined in terms of
the data model, all serialization syntaxes have to be deterministically
XML, YAML, or CBOR) that is capable of being mapped back to `application/vc+ld+json`.
As the <a>verification</a> and <a>validation</a> requirements are defined in terms
of the data model, all serialization syntaxes have to be deterministically
translated to the data model for processing, <a>validation</a>, or comparison.
This specification makes no requirements for support of any specific
serialization format.
</p>

<p>
Expand Down Expand Up @@ -3298,47 +3297,6 @@ <h2>Syntaxes</h2>
or an array of values.
</p>

<section>
<h3>JSON</h3>

<p>
The data model, as described in Section <a href="#core-data-model"></a>, can be
encoded in JavaScript Object Notation (JSON) [[!RFC8259]] by mapping property
values to JSON types as follows:
</p>

<ul>
<li>
Numeric values representable as IEEE754 SHOULD be represented as a Number type.
</li>
<li>
Boolean values SHOULD be represented as a Boolean type.
</li>
<li>
Sequence value SHOULD be represented as an Array type.
</li>
<li>
Unordered sets of values SHOULD be represented as an Array type.
</li>
<li>
Sets of <a>properties</a> SHOULD be represented as an Object type.
</li>
<li>
Empty values SHOULD be represented as a null value.
</li>
<li>
Other values MUST be represented as a String type.
</li>
</ul>

<p class="note">
As the transformations listed herein have potentially incompatible
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please translate for those of us who aren't as hip to the modern meme-lingo... (Really, please don't post things like this in technical discussions. They don't tend to advance the conversation, and they are often needlessly offensive.)

interpretations, additional profiling of the JSON format is required to provide
a deterministic transformation to the data model.
</p>

</section>

<section>
<h3>JSON-LD</h3>

Expand All @@ -3354,9 +3312,8 @@ <h3>JSON-LD</h3>

<p>
[[!JSON-LD]] is useful when extending the data model described in this
specification. Instances of the data model are encoded in [[!JSON-LD]] in the
same way they are encoded in JSON (Section <a href="#json"></a>), with the
addition of the <code>@context</code> <a>property</a>. The
specification. Instances of the data model are encoded in JSON-LD compact
form [[!JSON-LD]] and include the <code>@context</code> <a>property</a>. The
<a href="https://www.w3.org/TR/json-ld/#the-context">JSON-LD context</a>
is described in detail in the [[!JSON-LD]] specification and its use is
elaborated on in Section <a href="#extensibility"></a>.
Expand Down