added references to RDF/XML and Turtle RDF serialisations
authorJeniT
Wed, 21 Dec 2011 16:43:38 +0000
changeset 68c6c5c47accc2
parent 67 915fd629432f
child 69 41c5fce1c6b9
added references to RDF/XML and Turtle RDF serialisations
html-data-guide/index.html
     1.1 --- a/html-data-guide/index.html	Wed Dec 21 16:36:21 2011 +0000
     1.2 +++ b/html-data-guide/index.html	Wed Dec 21 16:43:38 2011 +0000
     1.3 @@ -717,7 +717,7 @@
     1.4          You will find it easier to consume and combine data published using a single <a>format</a> (syntax and vocabulary). To decide which to consume, you should first look at what formats your target publishers are currently using. It may be that these contain sufficient information for your application.
     1.5        </p>
     1.6        <p>
     1.7 -        If the publishers whom you are targeting are already publishing using multiple formats, you may want to consume from all those formats (see <a href="#consuming-multiple-formats" class="sectionRef"></a>) in order to maximise the data that you can collect while minimising the impact on the publishers who are providing that information. If you are consuming microdata and storing the results as RDF, you should follow a <a href=https://dvcs.w3.org/hg/htmldata/raw-file/default/microdata-rdf/index.html">standard mapping</a>.
     1.8 +        If the publishers whom you are targeting are already publishing using multiple formats, you may want to consume from all those formats (see <a href="#consuming-multiple-formats" class="sectionRef"></a>) in order to maximise the data that you can collect while minimising the impact on the publishers who are providing that information. If you are consuming microdata and storing the results as RDF, you should follow a <a href="https://dvcs.w3.org/hg/htmldata/raw-file/default/microdata-rdf/index.html">standard mapping</a>.
     1.9        </p>
    1.10        <p>
    1.11          If current <a title="format">formats</a> do not encode the information you need to the detail you need it for your application, publishers will be more likely to publish extra data for you to consume if you:
    1.12 @@ -767,26 +767,28 @@
    1.13            <section>
    1.14              <h5>Microdata/Microformats-2 Data Model</h5>
    1.15              <p>
    1.16 -              Microdata and microformats-2 can be mapped to the same <a href="http://dev.w3.org/html5/md/Overview.html#json" class="external text" title="http://dev.w3.org/html5/md/Overview.html#json" rel="nofollow">basic (JSON) data model</a>. Processing JSON into native programming structures, in Javascript and other languages, is usually very easy. Vocabularies are usually described in specification prose rather than a formal language.
    1.17 +              Microdata and microformats-2 can be mapped to the same <a href="http://dev.w3.org/html5/md/Overview.html#json" rel="nofollow">basic (JSON) data model</a>. Processing JSON into native programming structures, in Javascript and other languages, is usually very easy. Vocabularies are usually described in specification prose rather than a formal language.
    1.18              </p>
    1.19              <ul>
    1.20 -              <li><a href="http://dev.w3.org/html5/md/Overview.html#microdata-dom-api" class="external text" title="http://dev.w3.org/html5/md/Overview.html#microdata-dom-api" rel="nofollow">microdata DOM API</a> &mdash; part of microdata specification (W3C Last Call Working Draft)</li>
    1.21 -              <li><a href="http://tools.ietf.org/html/draft-zyp-json-schema-03" class="external text" title="http://tools.ietf.org/html/draft-zyp-json-schema-03" rel="nofollow">JSON Schema</a> &mdash; schema language for JSON (IETF Internet Draft)</li>
    1.22 +              <li><a href="http://dev.w3.org/html5/md/Overview.html#microdata-dom-api">microdata DOM API</a> &mdash; part of microdata specification (W3C Last Call Working Draft)</li>
    1.23 +              <li><a href="http://tools.ietf.org/html/draft-zyp-json-schema-03">JSON Schema</a> &mdash; schema language for JSON (IETF Internet Draft)</li>
    1.24              </ul>
    1.25            </section>
    1.26            
    1.27            <section>
    1.28              <h5>RDF Data Model</h5>
    1.29              <p>
    1.30 -              RDFa processors extract an RDF data model and processors can also generate <a href="https://dvcs.w3.org/hg/htmldata/raw-file/default/microdata-rdf/index.html">RDF from microdata</a>. There are a number of standards for formally expressing RDF <a title="vocabulary">vocabularies</a> and querying RDF, and drafts in progress for DOM-based manipulation of RDFa content.
    1.31 +              RDFa processors extract an RDF data model and processors can also generate <a href="https://dvcs.w3.org/hg/htmldata/raw-file/default/microdata-rdf/index.html">RDF from microdata</a>. There are a number of standards for alternative serialisations of RDF graphs that target different toolchains, formally expressing RDF <a title="vocabulary">vocabularies</a> and querying RDF, and drafts in progress for DOM-based manipulation of RDFa content.
    1.32              </p>
    1.33              <ul>
    1.34 -              <li><a href="http://www.w3.org/TR/rdfa-api/" class="external text" title="http://www.w3.org/TR/rdfa-api/" rel="nofollow">RDFa API</a> &mdash; W3C Working Draft</li>
    1.35 -              <li> <a href="http://json-ld.org/spec/latest/" class="external text" title="http://json-ld.org/spec/latest/" rel="nofollow">JSON-LD</a> &mdash; JSON representation of RDF (Unofficial Draft)</li>
    1.36 -              <li><a href="http://www.w3.org/TR/rdf-sparql-query/" class="external text" title="http://www.w3.org/TR/rdf-sparql-query/" rel="nofollow">SPARQL</a> &mdash; query language for RDF (W3C Recommendation)</li>
    1.37 -              <li><a href="http://www.w3.org/TR/sparql11-overview/" class="external text" title="http://www.w3.org/TR/sparql11-overview/" rel="nofollow">SPARQL 1.1</a> &mdash; W3C Working Draft</li>
    1.38 -              <li><a href="http://www.w3.org/TR/rdf-mt/" class="external text" title="http://www.w3.org/TR/rdf-mt/" rel="nofollow">RDFS</a> &mdash; vocabulary description language for RDF (W3C Recommendation)</li>
    1.39 -              <li><a href="http://www.w3.org/TR/owl-primer/" class="external text" title="http://www.w3.org/TR/owl-primer/" rel="nofollow">OWL</a> &mdash; ontology language for RDF (W3C Recommendation)</li>
    1.40 +              <li><a href="http://www.w3.org/TR/REC-rdf-syntax/">RDF/XML</a> &mdash; XML-based serialisation of RDF (W3C Recommendation)</li>
    1.41 +              <li><a href="http://www.w3.org/TR/turtle/">Turtle</a> &mdash; text-based serialisation of RDF (W3C Working Draft)</li>
    1.42 +              <li> <a href="http://json-ld.org/spec/latest/">JSON-LD</a> &mdash; JSON-based serialisation of RDF (Unofficial Draft)</li>
    1.43 +              <li><a href="http://www.w3.org/TR/rdf-mt/">RDFS</a> &mdash; vocabulary description language for RDF (W3C Recommendation)</li>
    1.44 +              <li><a href="http://www.w3.org/TR/owl-primer/">OWL</a> &mdash; ontology language for RDF (W3C Recommendation)</li>
    1.45 +              <li><a href="http://www.w3.org/TR/rdf-sparql-query/">SPARQL</a> &mdash; query language for RDF (W3C Recommendation)</li>
    1.46 +              <li><a href="http://www.w3.org/TR/sparql11-overview/">SPARQL 1.1</a> &mdash; W3C Working Draft</li>
    1.47 +              <li><a href="http://www.w3.org/TR/rdfa-api/">RDFa API</a> &mdash; W3C Working Draft</li>
    1.48              </ul>
    1.49            </section>
    1.50          </section>