Skip to content

Commit

Permalink
Reformat IANA Considerations section.
Browse files Browse the repository at this point in the history
  • Loading branch information
@msporny
msporny committed Jul 12, 2023
1 parent 5c46d79 commit eb58625
Showing 1 changed file with 117 additions and 119 deletions.
236 changes: 117 additions & 119 deletions index.html
View file
Original file line number Diff line number Diff line change
Expand Up @@ -5307,7 +5307,7 @@ <h3>JSON Web Token Claim Registrations</h3>
(IESG) for review, approval, and registration with IANA in the
"JSON Web Token Claims Registry".
</p>

<section id="vc-json-web-token-claim">
<h4>`vc`</h4>
<table>
Expand Down Expand Up @@ -5359,130 +5359,128 @@ <h4>`vp`</h4>
</section>
</section>

<section id="media-type-registrations">
<h3>Media Type Registrations</h3>
<section id="vc-ld-json-media-type">
<h4>`application/vc+ld+json`</h4>
<p>
This specification registers the <code>application/vc+ld+json</code> Media Type specifically for
identifying documents conforming to the Verifiable Credentials format.
</p>
<table>
<tr>
<th>Type name: </th>
<td>`application`</td>
</tr>
<tr>
<th>Subtype name: </th>
<td>`vc+ld+json`</td>
</tr>
<tr>
<th>Required parameters: </th>
<td>None</td>
</tr>
<tr>
<th>Encoding considerations: </th>
<td>
Resources that use the "<code>application/vc+ld+json</code>"
Media Type are required to conform to all of the requirements
for the "<code>application/ld+json</code>" Media Type and are
therefore subject to the same encoding considerations specified
in Section 11 of [[RFC7159]].
</td>
</tr>
<tr>
<th>Security considerations: </th>
<td>As defined in this specification.</td>
</tr>
<tr>
<th>Contact: </th>
<td>
W3C Verifiable Credentials Working Group
<a href="mailto:public-vc-wg@w3.org">public-vc-wg@w3.org</a>
</td>
</tr>
</table>

<p>
Note that while the Verifiable Credentials format uses JSON-LD
conventions, there are a number of constraints and additional
requirements for Verifiable Credential implementations that justify
the use of a specific media type.
</p>

<p>
This media type can be used with credentials secured using an <a>external proof</a>.
</p>
<section id="vc-ld-media-type">
<h2>application/vc+ld+json</h2>
<p>
This specification registers the <code>application/vc+ld+json</code> Media Type
specifically for identifying documents conforming to the Verifiable Credentials
format.
</p>
<table>
<tr>
<td>Type name: </td>
<td>application</td>
</tr>
<tr>
<td>Subtype name: </td>
<td>vc+ld+json</td>
</tr>
<tr>
<td>Required parameters: </td>
<td>None</td>
</tr>
<tr>
<td>Encoding considerations: </td>
<td>
Resources that use the "<code>application/vc+ld+json</code>" Media Type are
required to conform to all of the requirements for the
"<code>application/ld+json</code>" Media Type and are therefore subject to the
same encoding considerations specified in Section 11 of [[RFC7159]].
</td>
</tr>
<tr>
<td>Security considerations: </td>
<td>As defined in this specification.</td>
</tr>
<tr>
<td>Contact: </td>
<td>
W3C Verifiable Credentials Working Group
<a href="mailto:public-vc-wg@w3.org">public-vc-wg@w3.org</a>
</td>
</tr>
</table>

<p>
A [[JSON-LD]] context is expected to be present in the body of the document, and as
indicated by the presence of `ld+json` in the media type, the credential is expected
to be a valid
<a href="https://www.w3.org/TR/json-ld11/#dfn-json-ld-document">JSON-LD document</a>.
</p>
</section>
<p>
Note that while the Verifiable Credentials format uses JSON-LD conventions,
there are a number of constraints and additional requirements for Verifiable
Credential implementations that justify the use of a specific media type.
</p>

<section id="vp-ld-json-media-type">
<h4>`application/vp+ld+json`</h4>
<p>
This specification registers the <code>application/vp+ld+json</code> Media Type specifically for
identifying documents conforming to the Verifiable Presentations format.
</p>
<table>
<tr>
<th>Type name: </th>
<td>`application`</td>
</tr>
<tr>
<th>Subtype name: </th>
<td>`vp+ld+json`</td>
</tr>
<tr>
<th>Required parameters: </th>
<td>None</td>
</tr>
<tr>
<th>Encoding considerations: </th>
<td>
Resources that use the "<code>application/vp+ld+json</code>"
Media Type are required to conform to all of the requirements
for the "<code>application/ld+json</code>" Media Type and are
therefore subject to the same encoding considerations specified
in Section 11 of [[RFC7159]].
</td>
</tr>
<tr>
<th>Security considerations: </th>
<td>As defined in this specification.</td>
</tr>
<tr>
<th>Contact: </th>
<td>
W3C Verifiable Credentials Working Group
<a href="mailto:public-vc-wg@w3.org">public-vc-wg@w3.org</a>
</td>
</tr>
</table>
<p>
This media type can be used with credentials secured using an <a>external
proof</a>.
</p>
<p>
A [[JSON-LD]] context is expected to be present in the body of the document, and
as indicated by the presence of `ld+json` in the media type, the credential is
expected to be a valid
<a href="https://www.w3.org/TR/json-ld11/#dfn-json-ld-document">JSON-LD
document</a>.
</p>
</section>

<p>
Note that while the Verifiable Presentations format uses JSON-LD
conventions, there are a number of constraints and additional
requirements for Verifiable Presentation implementations that justify
the use of a specific media type.
</p>
<section id="vp-ld-media-type">
<h2>application/vp+ld+json</h2>
<p>
This specification registers the <code>application/vp+ld+json</code> Media
Type specifically for identifying documents conforming to the Verifiable
Presentations format.
</p>
<table>
<tr>
<td>Type name: </td>
<td>application</td>
</tr>
<tr>
<td>Subtype name: </td>
<td>vp+ld+json</td>
</tr>
<tr>
<td>Required parameters: </td>
<td>None</td>
</tr>
<tr>
<td>Encoding considerations: </td>
<td>
Resources that use the "<code>application/vp+ld+json</code>" Media Type are
required to conform to all of the requirements for the
"<code>application/ld+json</code>" Media Type and are therefore subject to the
same encoding considerations specified in Section 11 of [[RFC7159]].
</td>
</tr>
<tr>
<td>Security considerations: </td>
<td>As defined in this specification.</td>
</tr>
<tr>
<td>Contact: </td>
<td>
W3C Verifiable Credentials Working Group
<a href="mailto:public-vc-wg@w3.org">public-vc-wg@w3.org</a>
</td>
</tr>
</table>

<p>
This media type can be used with presentations secured using an <a>external proof</a>.
</p>
<p>
Note that while the Verifiable Credentials format uses JSON-LD conventions,
there are a number of constraints and additional requirements for Verifiable
Credential implementations that justify the use of a specific media type.
</p>

<p>
A [[JSON-LD]] context is expected to be present in the body of the document, and as
indicated by the presence of `ld+json` in the media type, the presentation is expected
to be a valid
<a href="https://www.w3.org/TR/json-ld11/#dfn-json-ld-document">JSON-LD document</a>.
</p>
</section>
<p>
This media type can be used with presentations secured using an
<a>external proof</a>.
</p>
<p>
A [[JSON-LD]] context is expected to be present in the body of the document, and
as indicated by the presence of `ld+json` in the media type, the credential is
expected to be a valid
<a href="https://www.w3.org/TR/json-ld11/#dfn-json-ld-document">JSON-LD
document</a>.
</p>
</section>

</section>

<section>
Expand Down

0 comments on commit eb58625

Please sign in to comment.