Skip to content

Add "Media Type Extensions" category. #14

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 2 commits into from
Aug 9, 2023
Merged

Add "Media Type Extensions" category. #14

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
16f33f3
Add "Media Type Extensions" category.
msporny Apr 8, 2023
2f3c104
Align extensions section with current specification status.
msporny Aug 4, 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
14 changes: 13 additions & 1 deletion index.html
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -249,7 +249,7 @@ <h1>Specification Entry Format</h1>
<td>
The Verifiable Credential extension category of the specification, which can
be one of the following values: `credentialStatus`, `credentialSchema`,
`evidence`, `proof`, `refreshService`, `termsOfUse`, or `vc`.
`evidence`, `media-type`, `proof`, `refreshService`, `termsOfUse`, or `vc`.
For example: `credentialStatus`.
<p class="note">
The extensions might define a `@type`. See [[JSON-LD11]].
Expand Down Expand Up @@ -391,7 +391,19 @@ <h1>Type-based Extensions</h1>
</table>

</section>
<section>
<h1>Media Type Extensions</h1>

<table class="simple">
<thead>
<th>Specification</th><th>Description</th>
</thead>
<tbody id="media-type-table">

</tbody>
</table>

</section>

</body>
</html>
9 changes: 9 additions & 0 deletions specifications/vc-jwt.json
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,9 @@
{
"name": "application/vc+ld+json+jwt",
"summary": "Securing Verifiable Credentials using JOSE and COSE",
"specification": "https://www.w3.org/TR/vc-jose-cose/",
"category": "media-type",
"maintainerEmail": "[email protected]",
Copy link

Choose a reason for hiding this comment

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

Can we add a "tranformationDirectionality" field to capture the uni/bidirectional nature of the media type transformation?

Copy link
Member Author

Choose a reason for hiding this comment

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

I was thinking that people would note that in the description, though, you're right -- if specifying the directionality is a requirement for VC-associated media types, then perhaps it should be a field.

I'd prefer if we got to consensus on exactly what these "transformation rules" need to do/say about directionality before adding that field to the registration requirements.

Copy link
Contributor

Choose a reason for hiding this comment

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

Let us not add another property, let us use the convention of commenting on this in the description.

The spec that is referenced should do the work.

Copy link
Contributor

Choose a reason for hiding this comment

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

The less we say about "transformation rules" the better.

The important part is that the output conform to application/vc+ld+json... how you get there is the business of the spec that is registered here. The VCWG's business is in ensuring that the output matches the expected media type.

Also, as I have said elsewhere, there can be more than 1 mapping... this is not our change to make 3 rings for the elves.

I also don't want the working group dragged into "reviewing mappings"... that is the entire point of the day 3 resolution, to shift that burden to the implementer, and give them a clear way to tell if they did a good job (does the output of your mapping look like application/vc+ld+json).

Copy link
Contributor

Choose a reason for hiding this comment

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

This PR is so stale it no longer reflects the working group documents, I have suggested changes to correct it.

"maintainerName": "W3C Verifiable Credentials Working Group",
"maintainerWebsite": "https://www.w3.org/groups/wg/vc"
}
1 change: 1 addition & 0 deletions tooling/specification-entry.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -30,6 +30,7 @@ properties:
- credentialStatus
- credentialSchema
- evidence
- media-type
- proof
- refreshService
- termsOfUse
Expand Down