Recommending a canonical syntax?

[GoogleCodeExporter]

The Guide currently has this to say about the question of choosing a syntax for 
a voiD file (in 4.1, will be 5.2 after restructuring):

--- start quote ---
When deploying a voiD file one has basically three options:

Deploy it using Turtle RDF syntax [Turtle] in a file called void.ttl and make 
it accessible by assign an URI. Pro: easily readable by humans. Con: current 
parser support not overly well; higher costs of setup when accessing.

Deploy it using RDF/XML syntax [RDF/XML] in a file called void.rdf and make it 
accessible by assign an URI. Pro: wide parser support. Con: awkward syntax.

Deploy it using XHTML+RDFa syntax [RDFa] in the homepage of the dataset. Pro: 
can be directly embedded into the web page that describes the dataset hence 
does not require the publisher to maintain a separate voiD file. Con: weak 
current parser support (incl. SPARQL consumption).

Note: We have not decided on the canonical deployment format, yet. For the 
casual user, Turtle may seem to be the best option currently, but implementers 
are free to choose their deployment format as fit with their infrastructure. We 
explicitly solicit feedback on this issue!
--- end quote ---

It's almost 2011 and I think we have to do better than this non-statement!

Original issue reported on code.google.com by richard....@gmail.com on 8 Dec 2010 at 12:41

[GoogleCodeExporter]

Proposed replacement text for the words quoted above:

Popular options for publishing a voiD description alongside a dataset include 
the following:

1. A Turtle file void.ttl in the root directory of the site, with a local hash 
URI for the dataset, yielding a dataset URI such as 
http://example.com/void.ttl#MyDataset

2. Using the root URI of the site, such as http://example.com/, as the dataset 
URI, and serving both HTML and an RDF format via content negotiation from that 
URI

3. Embedding the voiD description as HTML+RDFa markup into the homepage of the 
dataset, with a local hash URI for the dataset, yielding a dataset URI such as 
http://example.com/#MyDataset

Original comment by richard....@gmail.com on 8 Dec 2010 at 7:34

[GoogleCodeExporter]

I just changed Section 6.2 in r163 along those lines. Hope it's ok with 
everyone; let me know if not.

Original comment by richard....@gmail.com on 8 Dec 2010 at 8:24

• Changed state: Started

[GoogleCodeExporter]

Looks good to me. Great job, R!

Original comment by Michael.Hausenblas on 9 Dec 2010 at 10:32

[GoogleCodeExporter]

Looks good to me too!

Original comment by jun.zhao...@googlemail.com on 9 Dec 2010 at 10:45

[GoogleCodeExporter]

Closed as per today's teleconference

Original comment by richard....@gmail.com on 14 Dec 2010 at 11:57

• Changed state: Fixed