- From: Nathan <nathan@webr3.org>
- Date: Wed, 10 Nov 2010 00:16:13 +0000
- To: Henri Sivonen <hsivonen@iki.fi>
- CC: Larry Masinter <masinter@adobe.com>, "julian.reschke@gmx.de" <julian.reschke@gmx.de>, "www-tag@w3.org WG" <www-tag@w3.org>, Alexey Melnikov <alexey.melnikov@isode.com>
Henri Sivonen wrote: > Another case of deployment happening ahead of registration not to mention the various rss types, and the types for all variations of RDF other than rdf+xml, and the media type for things like opensearch [1]. The question was asked, recently, how one would go about deploying a new mediatype, and which type to use whilst being a future web standard, but no reply was given [2,3], similarly after many years, the other RDF serializations like N3 and Turtle remain unregistered, and likewise re opensearch. To illustrate the effect this has, currently to figure out what the true media type is of some returned RDF, one needs to check for the following: application/rdf+xml, application/xml, text/xml -> hopefully rdf+xml text/turtle, application/x-turtle, application/turtle, text/rdf+n3, text/n3, application/n3: -> n3 or turtle text/rdf, text/text, text/plain, text/html, "" -> could be anything and that's only to negotiate between rdf/xml, n3 and turtle. Best, Nathan [1] http://www.opensearch.org/Specifications/OpenSearch/1.1 (application/opensearchdescription+xml - This type is pending IANA registration. - (for a very long time!) [2] http://www.ietf.org/mail-archive/web/ietf-types/current/msg01103.html [3] http://www.ietf.org/mail-archive/web/ietf-types/current/msg01102.html
Received on Wednesday, 10 November 2010 00:17:08 UTC