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

[Matthias Kovatsch <[e-mail]>]

Dear Paul

Unfortunately, there have not been any other voices to come to a better conclusion…

I have been thinking and I see your argument enabling tools to offer relevant services. What I am worried about is creating an incompatibility to valid alternative tool that work at the JSON or JSON-LD level; I assume the majority wouldn’t add such a specific identifier when they focus at a far more general level. However, there is no identifier for JSON-LD and, for some reason, not even JSON. The resulting level of interoperability across tools is then public.utf8-plain-text / CF_UNICODETEXT, which is indeed to coarse-grained to provide relevant services.

The new HTML 5.3 spec now includes these clipboard identifiers, which is pretty late considering the reach of HTML. Anyhow, it is an example for “adding it later”.

Hence, my conclusion for the moment would be to leave it out for the current version of the WoT TD spec. We should consult with the JSON-LD 1.1 Working Group if they think a JSON-LD clipboard flavor name/identifier would be useful (I think it would) and should be defined for the upcoming JSON-LD 1.1 spec. This then also entrails checking with the authors/editor of RFC 8259 if it wouldn’t make sense to define one for JSON. I hope that this then provides enough input to choose the right level. We have already been considering a 1.1 version of the TD format in the WoT WG charter discussion, which then would include the update for clipboard identifiers.

I hope we will get some more feedback until then also. Hearing from tool vendors would be great!

Best wishes,
Matthias