Re: [media-types] Notice for a potential media type registration: application/td+json

Matthias Kovatsch <w3c@kovatsch.net> Sat, 15 June 2019 10:23 UTC

Return-Path: <w3c@kovatsch.net>
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 07048120020 for <media-types@ietfa.amsl.com>; Sat, 15 Jun 2019 03:23:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level:
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, SPF_FAIL=0.001] autolearn=no 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 6nMDXPQjdPX8 for <media-types@ietfa.amsl.com>; Sat, 15 Jun 2019 03:22:59 -0700 (PDT)
Received: from pechora1.lax.icann.org (pechora1.icann.org [192.0.33.71]) (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 A889E1200B1 for <media-types@ietf.org>; Sat, 15 Jun 2019 03:22:58 -0700 (PDT)
Received: from ma04-relay.lansolnet.com (ma04-relay.lansolnet.com [176.95.46.38]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by pechora1.lax.icann.org (Postfix) with ESMTPS id 7352D1E01F2 for <media-types@iana.org>; Sat, 15 Jun 2019 10:22:57 +0000 (UTC)
Received: from unknown ([192.168.8.236]) by ma04-relay.lansolnet.com; Sat, 15 Jun 2019 12:22:35 +0200
Received: from MBX100D.cloud4partner.com (192.168.8.236) by MBX100D.cloud4partner.com (192.168.8.236) with Microsoft SMTP Server (TLS) id 15.0.1156.6; Sat, 15 Jun 2019 12:22:35 +0200
Received: from MBX100D.cloud4partner.com ([fe80::1438:a47a:e7b7:aed8]) by MBX100D.cloud4partner.com ([fe80::1438:a47a:e7b7:aed8%18]) with mapi id 15.00.1156.000; Sat, 15 Jun 2019 12:22:35 +0200
From: Matthias Kovatsch <w3c@kovatsch.net>
To: Paul Libbrecht <paul@hoplahup.net>, "media-types@iana.org" <media-types@iana.org>
CC: "plh@w3.org" <plh@w3.org>, "team-wot@w3.org" <team-wot@w3.org>
Thread-Topic: [media-types] Notice for a potential media type registration: application/td+json
Thread-Index: AdUBjvDgPXIk9DLnTCumvM9fM/S++gfxfJSAAINMOuA=
Date: Sat, 15 Jun 2019 10:22:34 +0000
Message-ID: <500fc6386f694fb18c55c6c2ebee7845@MBX100D.cloud4partner.com>
References: <bef5f77d59484b78a5cdc4caab167ee2@MBX100D.cloud4partner.com> <D0576ABF-05E5-455F-AC01-D99F0B8F1304@hoplahup.net>
In-Reply-To: <D0576ABF-05E5-455F-AC01-D99F0B8F1304@hoplahup.net>
Accept-Language: en-US, de-DE
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [192.168.8.246]
Content-Type: multipart/alternative; boundary="_000_500fc6386f694fb18c55c6c2ebee7845MBX100Dcloud4partnercom_"
MIME-Version: 1.0
X-cloud-security-sender: w3c@kovatsch.net
X-cloud-security-recipient: media-types@iana.org
X-cloud-security-Virusscan: CLEAN
X-cloud-security-disclaimer: This E-Mail was scanned by E-Mailservice on ma04-relay.lansolnet.com with 2E819B8006D
X-cloud-security-connect: unknown[192.168.8.236], TLS=1, IP=192.168.8.236
X-cloud-security: scantime:.1490
Archived-At: <https://mailarchive.ietf.org/arch/msg/media-types/B5Cc7ADWjqXAsZ2J-bLyFgrUArI>
Subject: Re: [media-types] Notice for a potential media type registration: application/td+json
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: Sat, 15 Jun 2019 10:23:01 -0000

Dear Paul

Thank you very much for pointing us to the clipboard flavor names. I have been trying to figure out more from the IANA side, but they appear to be only managed by Microsoft and Apple, resp. Is there any IANA recommendation around it – as it is not even part of the registration form (https://www.iana.org/form/media-types). Can you or anyone else help on this?

I have also been thinking about the very specific “json-td” flavor name. One motivation has been that TD can be treated like JSON, for human “reasoning” and processing pipelines. At the moment, the most specific tools that we have are online editors that provide some syntax highlighting. Yet I think, no information would be lost when it is copied around as JSON. Technically, TDs are a specialization of JSON-LD, which in turn is a specialization of JSON, which again could be seen as a specialization of Unicode text.

Could someone explain, what for instance, the “public.json” flavor provides on top of “public.utf8-plain-text” when copy-pasting JSON documents? From this I could extrapolate what “json-td” could offer atop “json”. Are there any folks having arguments to have “json-ld” as a clipboard flavor name?

Thanks a lot,
Matthias