Re: [media-types] More questions for multiple suffixes (Re: WG: IETF 112 agenda)

Manu Sporny <msporny@digitalbazaar.com> Mon, 08 November 2021 14:00 UTC

Return-Path: <msporny@digitalbazaar.com>
X-Original-To: media-types@ietfa.amsl.com
Delivered-To: media-types@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D0C693A0CB0 for <media-types@ietfa.amsl.com>; Mon, 8 Nov 2021 06:00:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.229
X-Spam-Level:
X-Spam-Status: No, score=-5.229 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, NICE_REPLY_A=-3.33, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id afOK8P4SgCtH for <media-types@ietfa.amsl.com>; Mon, 8 Nov 2021 06:00:06 -0800 (PST)
Received: from mail.digitalbazaar.com (mail.digitalbazaar.com [96.89.14.193]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8DE863A0AA0 for <media-types@ietf.org>; Mon, 8 Nov 2021 06:00:06 -0800 (PST)
Received: from [73.152.135.186] (helo=[10.4.10.95]) by mail.digitalbazaar.com with esmtpsa (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.89) (envelope-from <msporny@digitalbazaar.com>) id 1mk5Bp-00042F-3Q for media-types@ietf.org; Mon, 08 Nov 2021 09:00:03 -0500
To: media-types@ietf.org
References: <c4ae17e0-aa20-33fa-7931-23ea78a9a3b4@alvestrand.no> <b3be73ee-92c0-da23-e398-65d5d6d88293@alvestrand.no> <4ebc9cf0-12c4-0d98-67b3-6891c46c5b5e@digitalbazaar.com> <1fdafb9c-32ef-c563-86a2-d2a00c2b63a3@alvestrand.no> <193d2c3b-c3e0-dcb2-b990-0bb8ae981486@digitalbazaar.com> <59E39DE3-E17F-4D73-81A6-D3991533A857@mnot.net>
From: Manu Sporny <msporny@digitalbazaar.com>
Message-ID: <ce8f4935-24e5-b4f8-5369-0f2507bf873c@digitalbazaar.com>
Date: Mon, 8 Nov 2021 09:00:00 -0500
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.14.0
MIME-Version: 1.0
In-Reply-To: <59E39DE3-E17F-4D73-81A6-D3991533A857@mnot.net>
Content-Type: text/plain; charset=utf-8
Content-Language: en-GB
Content-Transfer-Encoding: 7bit
X-SA-Exim-Connect-IP: 73.152.135.186
X-SA-Exim-Mail-From: msporny@digitalbazaar.com
X-SA-Exim-Version: 4.2.1 (built Tue, 02 Aug 2016 21:08:31 +0000)
X-SA-Exim-Scanned: Yes (on mail.digitalbazaar.com)
Archived-At: <https://mailarchive.ietf.org/arch/msg/media-types/HgqMJs1GANjf8FAQS1ZhgstojIg>
Subject: Re: [media-types] More questions for multiple suffixes (Re: WG: IETF 112 agenda)
X-BeenThere: media-types@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "IANA mailing list for reviewing Media Type \(MIME Type, Content Type\) registration requests." <media-types.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/media-types>, <mailto:media-types-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/media-types/>
List-Post: <mailto:media-types@ietf.org>
List-Help: <mailto:media-types-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/media-types>, <mailto:media-types-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 08 Nov 2021 14:00:17 -0000

On 11/7/21 10:09 PM, Mark Nottingham wrote:
> Have you considered just registering '+ldjson'?

Yes, we did think of registering "+jsonld" back in 2013 and, IIRC, were
instructed by IANA folks to just do "ld+json" since it was a JSON syntax with
added semantics.

This was further reinforced in JSON-LD 1.1, where they took up the question
again, I think engaging w/ the registry maintainer (I wasn't a part of that
discussion, so I don't know the details), considering if "+jsonld" should be
registered... and deciding that it would cause too much chaos to register both
"+ld+json" and "+jsonld" -- possibly breaking implementations out in the field.

Fast forward 6+ years and we have other media types that use "ld+json" to
encode themselves, and people wanting to use the media type to decide how to
process the documents and thus things like "vc+ld+json" and "did+ld+json" were
born... but when we tried to register them, the experts said "Umm, we're not
sure how to interpret that extra '+'."

> FWIW, I think Harald has hit upon many of the central questions, and we 
> should focus on them in the time we have.

I'm fine w/ taking the conversation in whatever direction folks want to take it.

> Another is that 6838 describes the use case for suffixes as 'well-known 
> structuring syntaxes' -- whereas linked data is a data model, not a syntax.
> While there's some fuzziness in this area, it might be good to talk about
> whether linked data is a 'structuring syntax' or something else.

It's an abstract data model that is formally described in:
https://www.w3.org/TR/json-ld11/#data-model

It's not a structuring syntax.

Some have wondered why it's not "ld+vc+json"... and the answer there seemed to
be "because the Verifiable Credential isn't encoded in JSON... it's encoded in
JSON-LD"... the structure needs to go from most specific to least specific...
noting that the earlier parts of the media type describe data model-y things
and the latter parts of the media type describe syntax-y things.

It's a reasonable mental model, if not a bit fuzzy when it comes to components
in the middle.

-- manu

-- 
Manu Sporny - https://www.linkedin.com/in/manusporny/
Founder/CEO - Digital Bazaar, Inc.
News: Digital Bazaar Announces New Case Studies (2021)
https://www.digitalbazaar.com/