Re: Naive (short) question about JSON-LD parsing

Someone else mentioned a "runs against" analysis that makes me think the following makes more sense from a natural extensibility (aka layered model) perspective:
application/ld+credential+json

This allows for variations like:
application/credential+json (no JSON-LD/RDF extensions used)
application/structured+credential+json (example of an alternative JSON-based serialization format)

Depends on if you truly have a World Wide point-of-view or something more parochial (‘relating to an ecclesiastical district’, from parochia (see parish)).


Get Outlook for Android<https://aka.ms/AAb9ysg>
________________________________
From: Bob Wyman <bob@wyman.us>
Sent: Tuesday, February 14, 2023 4:29:48 AM
To: Michael Herman (Trusted Digital Web) <mwherman@parallelspace.net>
Cc: public-credentials (public-credentials@w3.org) <public-credentials@w3.org>
Subject: Re: Naive (short) question about JSON-LD parsing

Michael,
Given https://datatracker.ietf.org/doc/html/draft-ietf-mediaman-suffixes, it seems to me that:
application/credential+ld+json
would be more "obvious" than
application/ld-credential+json

What am I missing?

bob wyman


On Mon, Feb 13, 2023 at 2:33 PM Michael Herman (Trusted Digital Web) <mwherman@parallelspace.net<mailto:mwherman@parallelspace.net>> wrote:

Thank you Orie, Daniel, Dave, and Manu for your quick responses – and that everyone had the same answer 😊



RE: - https://www.iana.org/assignments/media-types/application/ld+json


RE: Type name: application

RE: Subtype name: ld+json



Using the above as a pattern, isn’t the most obvious Media Type for a JSON-LD Verifiable Credential (encoded as JSON) something like:



RE: Type name: application

RE: Subtype name: ld-credential+json



That is, the Subtype name correlates with a particular object model (e.g. JSON-LD VC DM) with the suffix correlating with the parseable “file type” (e.g, +json).



Michael

CAD 2 cents – even though we don’t have pennies any more


Get Outlook for Android<https://aka.ms/AAb9ysg>
________________________________
From: Dave Longley <dlongley@digitalbazaar.com<mailto:dlongley@digitalbazaar.com>>
Sent: Monday, February 13, 2023 12:08:37 PM
To: Orie Steele <orie@transmute.industries>
Cc: Michael Herman (Trusted Digital Web) <mwherman@parallelspace.net<mailto:mwherman@parallelspace.net>>; public-credentials (public-credentials@w3.org<mailto:public-credentials@w3.org>) <public-credentials@w3.org<mailto:public-credentials@w3.org>>
Subject: Re: Naive (short) question about JSON-LD parsing

Short answer: Yes, all JSON-LD is JSON and thus parsable by any "plain old" JSON parser.

Also (inline below)...

On Mon, Feb 13, 2023 at 12:10 PM Orie Steele <orie@transmute.industries> wrote:
See also:

https://datatracker.ietf.org/doc/html/draft-w3cdidwg-media-types-with-multiple-suffixes#section-2.1


^ Note the draft for multiple suffixes appears not adopted by an IETF WG and is also expired... Happy to assist in correcting that.

That's not the most up to date draft, which I believe is here: https://www.ietf.org/archive/id/draft-ietf-mediaman-suffixes-03.html


--

Dave Longley
CTO
Digital Bazaar, Inc.