Re: [media-types] Notice for a potential media type registration: application/td+json
"Paul Libbrecht" <paul@hoplahup.net> Mon, 17 June 2019 06:37 UTC
Return-Path: <paul@hoplahup.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 A360112000E for <media-types@ietfa.amsl.com>; Sun, 16 Jun 2019 23:37:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.889
X-Spam-Level:
X-Spam-Status: No, score=-1.889 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, T_SPF_PERMERROR=0.01] 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 95x8J-7NT-xe for <media-types@ietfa.amsl.com>; Sun, 16 Jun 2019 23:37:42 -0700 (PDT)
Received: from pechora6.dc.icann.org (pechora6.icann.org [IPv6:2620:0:2830:201::1:72]) (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 73CC8120122 for <media-types@ietf.org>; Sun, 16 Jun 2019 23:37:41 -0700 (PDT)
Received: from 18.mo1.mail-out.ovh.net (18.mo1.mail-out.ovh.net [46.105.35.72]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by pechora6.dc.icann.org (Postfix) with ESMTPS id BF59D1E014F for <media-types@iana.org>; Mon, 17 Jun 2019 06:37:40 +0000 (UTC)
Received: from player735.ha.ovh.net (unknown [10.109.159.132]) by mo1.mail-out.ovh.net (Postfix) with ESMTP id 1B50517D7EC for <media-types@iana.org>; Mon, 17 Jun 2019 08:37:18 +0200 (CEST)
Received: from hoplahup.net (pD9526438.dip0.t-ipconnect.de [217.82.100.56]) (Authenticated sender: paul@hoplahup.net) by player735.ha.ovh.net (Postfix) with ESMTPSA id 72B4E6EA2239; Mon, 17 Jun 2019 06:37:15 +0000 (UTC)
From: Paul Libbrecht <paul@hoplahup.net>
To: Matthias Kovatsch <w3c@kovatsch.net>
Cc: media-types@iana.org, plh@w3.org, team-wot@w3.org
Date: Mon, 17 Jun 2019 08:37:14 +0200
X-Mailer: MailMate (1.12.5r5635)
Message-ID: <487D1B91-4BA1-4B59-9DAD-831BC1355E51@hoplahup.net>
In-Reply-To: <500fc6386f694fb18c55c6c2ebee7845@MBX100D.cloud4partner.com>
References: <bef5f77d59484b78a5cdc4caab167ee2@MBX100D.cloud4partner.com> <D0576ABF-05E5-455F-AC01-D99F0B8F1304@hoplahup.net> <500fc6386f694fb18c55c6c2ebee7845@MBX100D.cloud4partner.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="=_MailMate_D2BC52E7-1DDF-4036-B738-C92F09DF00F5_="
Content-Transfer-Encoding: 8bit
Embedded-HTML: [{"HTML":[2870, 1887], "plain":[1415, 1261], "uuid":"3017616C-683C-49E5-BB06-45F68331D808"}]
X-Ovh-Tracer-Id: 3827496736987482117
X-VR-SPAMSTATE: OK
X-VR-SPAMSCORE: 0
X-Greylist: Sender passed SPF test, not delayed by milter-greylist-4.6.2 (pechora6.dc.icann.org [192.0.46.72]); Mon, 17 Jun 2019 06:37:40 +0000 (UTC)
X-VR-SPAMCAUSE: gggruggvucftvghtrhhoucdtuddrgeduuddrudeiiedguddtiecutefuodetggdotefrodftvfcurfhrohhfihhlvgemucfqggfjpdevjffgvefmvefgnecuuegrihhlohhuthemucehtddtnecu
Archived-At: <https://mailarchive.ietf.org/arch/msg/media-types/Our2wMQ36h3WZztN7LYR0wIG3JY>
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: Mon, 17 Jun 2019 06:37:46 -0000
Dear Matthias, you’re basically asking for precision about my assertion: > type-specificity is likely to give the best user-experience Here is my interpretation and I am happy to hear about others’ point of view: Type-specificity allows services to be specific (so, a user knows what to read and write because the UI is able to express it); lack of specificity gives freedom to users but this freedom is bound to a broader interpretation range. As an example: text/html or text/json is only presented as text to people who understand it and is known to be sometimes quite painful to read. Similarly, using a generic editor for an OWL-RDF-encoded ontology works but requires the editors to be properly understood (I’ve never met newbie users to be confortable with Protégé for example). So while I am happy to support the possibility of editing given by the text and json-ld nature; I still think that a specific type is the only way to make tools able to offer relevant services. Note that the clipboard type is the most specific information you can use for a tool to be chosen as relevant or not; only an adjusted clipboard type can make it more specialised. Finally, because there is sub-typing (alas only on macOS), slightly more generic services might still be applicable (e.g. json-ld browser or json structured display). thanks. Paul On 15 Jun 2019, at 12:22, Matthias Kovatsch wrote: > 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 > _______________________________________________ > media-types mailing list > media-types@ietf.org > https://www.ietf.org/mailman/listinfo/media-types
- [media-types] Notice for a potential media type r… Matthias Kovatsch
- Re: [media-types] Notice for a potential media ty… Mark Baker
- Re: [media-types] Notice for a potential media ty… Matthias Kovatsch
- Re: [media-types] Notice for a potential media ty… Paul Libbrecht
- Re: [media-types] Notice for a potential media ty… Matthias Kovatsch
- Re: [media-types] Notice for a potential media ty… Paul Libbrecht
- Re: [media-types] Notice for a potential media ty… Matthias Kovatsch