W3C home > Mailing lists > Public > public-rdf-wg@w3.org > May 2012

Re: Deprecate most "native" RDF serializations

From: Gavin Carothers <gavin@carothers.name>
Date: Fri, 4 May 2012 08:03:42 -0700
Message-ID: <CAPqY83w8+jKjqJA9JECofYmnMi89eF79_njpGovEDvsgG7_h5Q@mail.gmail.com>
To: Dan Brickley <danbri@danbri.org>
Cc: Manu Sporny <msporny@digitalbazaar.com>, RDF WG <public-rdf-wg@w3.org>
On Thu, May 3, 2012 at 10:49 PM, Dan Brickley <danbri@danbri.org> wrote:
> 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?

RDFa or Turtle in script tag with type="text/turtle" (same as
XHTML/HTML) would work.

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

Adobe describes XMP rather oddly including statements like "One
enabling technology is the Resource Description Framework (RDF) that
utilizes Adobe XMP". This was news to me ;)  Also XMP is defined in
terms of XML not RDF. For example:

A single XMP packet shall be serialized using a single rdf:RDF XML
element. The rdf:RDF element content
shall consist of only zero or more rdf:Description elements.

It is parseable as RDF/XML but not specified as such.

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

Nope! (Note, in the future one will need to make sure your tools are
UTF-8 safe). With N-Triples defined as subset of Turtle
http://dvcs.w3.org/hg/rdf/raw-file/default/rdf-turtle/index.html#sec-triples
I think we have "Turtle Lite".

>
> N3 - we can't deprecate something we never recommended.

No, but we can stop talking about it. For example the introduction to
Turtle no longer mentions it in the first sentence ;)

>
> +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 15:04:16 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 16:25:48 GMT