Re: Deprecate most "native" RDF serializations

On 4 May 2012, at 06:42, Manu Sporny <msporny@digitalbazaar.com> wrote:

> Please send a strong signal out to RDF authors deprecating the following
> "native" RDF serializations:
> 
> * RDF/XML
> * N-Triples
> * N3
> * TRiG
> * N-Quads
> * anything else that isn't TURTLE :)

What should rdf-in-svg use? Rdfa?

How about all those Adobe-XMP embeds in jpegs, pdfs etc? What does it mean to deprecate rdf-xml there?

Ntriples --- am i the only one who regularly filters rdf ntriples dumps by grepping ?

N3 - we can't deprecate something we never recommended

+1 for making the landscape less daunting, but I look more to primer + tools for that

Cheers,

Dan

> 
> That is, something that we can point people to and say: W3C says not to
> use that, don't use it for any future work, put a bullet in the
> serialization.
> 
> The only officially supported RDF serializations should be:
> 
> * TURTLE
> * TURTLE Lite
> 
> TURTLE Lite would effectively be a subset of TURTLE - N-Quads, or
> something that would be N-Quads-like (allowing for either "s p o" or "s
> p o c" statements).
> 
> Note that I left RDFa and JSON-LD out of this as I don't view them as
> "native" RDF serializations. RDFa can express RDF in other Host
> Languages, but can be transformed to other things like JSON-LD without
> passing through RDF. JSON-LD just happens to have a way to convert it to
> RDF and back loss-lessly, but that's a happy side effect of the
> serialization.
> 
> The goal would be to simplify the dizzying array of options authors have
> in front of them right now and send a clear message about what they
> should be using and not using.
> 
> -- manu
> 
> -- 
> Manu Sporny (skype: msporny, twitter: manusporny)
> President/CEO - Digital Bazaar, Inc.
> blog: PaySwarm Website for Developers Launched
> http://digitalbazaar.com/2012/02/22/new-payswarm-alpha/
>

Received on Friday, 4 May 2012 05:49:50 UTC