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

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