--- /dev/null Thu Jan 01 00:00:00 1970 +0000
+++ b/trig/index.html Sat Oct 15 11:00:59 2011 -0700
@@ -0,0 +1,259 @@
+<!DOCTYPE html>
+<html xmlns="http://www.w3.org/1999/xhtml">
+ <head>
+ <title>TriG</title>
+ <meta http-equiv='Content-Type' content='text/html;charset=utf-8'/>
+ <script src='https://ajax.googleapis.com/ajax/libs/jquery/1.6.2/jquery.min.js' class='remove'></script>
+ <script src='../ReSpec.js/js/respec.js' class='remove'></script>
+ <script class='remove'>
+ $.fn.renameElement = function (name) {
+ return this.each(function () {
+ var $newElement = $(this.ownerDocument.createElement(name));
+ for (var i = 0, n = this.attributes.length; i < n; i++) {
+ var attribute = this.attributes[i];
+ $newElement[0].setAttributeNS(attribute.namespaceURI, attribute.name, attribute.value);
+ }
+ $(this).contents().appendTo($newElement);
+ $(this).replaceWith($newElement);
+ });
+ };
+ preprocessTrig = { apply: function (ignore) {
+ $("script[type='application/trig']").removeAttr('type').renameElement('span');
+ $("script[type='text/plain']").removeAttr('type').renameElement('span');
+ }
+ };
+ var respecConfig = {
+ // specification status (e.g. WD, LCWD, NOTE, etc.). If in doubt use ED.
+ specStatus: "ED",
+
+ // the specification's short name, as in http://www.w3.org/TR/short-name/
+ shortName: "TriG",
+
+ // if your specification has a subtitle that goes below the main
+ // formal title, define it here
+ subtitle : "Named Graph and RDF Dataset Language",
+
+ // if you wish the publication date to be other than today, set this
+ // publishDate: "2011-08-09",
+
+ // if the specification's copyright date is a range of years, specify
+ // the start date here:
+ copyrightStart: "2010",
+
+ // if there is a previously published draft, uncomment this and set its YYYY-MM-DD date
+ // and its maturity status
+ //previousPublishDate: "2011-08-09",
+ //previousMaturity: "FPWD",
+ //previousURI: "http://www.w3.org/TR/???",
+
+ // if there a publicly available Editor's Draft, this is the link
+ edDraftURI: "http://dvcs.w3.org/hg/rdf/raw-file/default/trig/index.html",
+
+ // if this is a LCWD, uncomment and set the end of its review period
+ // lcEnd: "2009-08-05",
+
+ // if you want to have extra CSS, append them to this list
+ // it is recommended that the respec.css stylesheet be kept
+ extraCSS: ["http://dev.w3.org/2009/dap/ReSpec.js/css/respec.css"],
+
+ // editors, add as many as you like
+ // only "name" is required
+ editors: [
+ { name: "Gavin Carothers", url: "http://gavin.carothers.name/",
+ company: "TopQuadrant, Inc", companyURL: "http://topquadrant.com/" },
+ ],
+
+ // authors, add as many as you like.
+ // This is optional, uncomment if you have authors as well as editors.
+ // only "name" is required. Same format as editors.
+
+ authors: [
+ { name: "Chris Bizer", url: "http://www.bizer.de",
+ company: "Freie Universität Berlin", companyURL: "http://www.fu-berlin.de/" },
+ { name: "Richard Cyganiak", url: "http://richard.cyganiak.de",
+ company: "Freie Universität Berlin", companyURL: "http://www.fu-berlin.de/" },
+ ],
+
+ // name of the WG
+ wg: "RDF Working Group",
+
+ // URI of the public WG page
+ wgURI: "http://www.w3.org/2011/rdf-wg/",
+
+ // name (with the @w3c.org) of the public mailing to which comments are due
+ wgPublicList: "public-rdf-comments",
+
+ // URI of the patent status for this WG, for Rec-track documents
+ // !!!! IMPORTANT !!!!
+ // This is important for Rec-track documents, do not copy a patent URI from a random
+ // document unless you know what you're doing. If in doubt ask your friendly neighbourhood
+ // Team Contact.
+ wgPatentURI: "http://www.w3.org/2004/01/pp-impl/46168/status",
+ doRDFa: true,
+ preProcess: [ preprocessTrig ]
+ };
+ </script>
+ </head>
+ <body>
+ <section id='abstract'>
+ <p>The Resource Description Framework
+ (<abbr title="Resource Description Framework">RDF</abbr>) is a
+ general-purpose language for representing information in the Web.</p>
+
+ <p>This document defines a textual syntax for RDF called Trig
+ that allows an RDF dataset to be completely written in a compact and
+ natural text form, with abbreviations for common usage patterns and
+ datatypes. TriG is an extension of the
+ <a href="http://www.w3.org/TR/Turtle">Turtle</a> format.
+ </p>
+ </section>
+
+ <section id="sec-intro">
+ <h2>Introduction</h2>
+ <p>This document defines TriG a concrete syntax for RDF as defined in the
+ <a href="../rdf-concepts/index.html">RDF Concepts and Abstract Syntax</a>
+ ([[!RDF-CONCEPTS]]) W3C Recommendation. TriG is an extension of
+ <a href="http://www.w3.org/TR/Turtle">Turtle</a> ([[!TURTLE]]), extended
+ to support representing a complete RDF Dataset.
+ </section>
+
+ <section id="sec-trig-intro" class="informative">
+ <h2>An Introduction to TriG</h2>
+ <p>The
+ <a href="#sec-syntax">TriG Syntax</a> and <a href="#sec-grammar">TriG
+ Grammar</a> sections formally define the language.
+ </p>
+
+ <p>A TriG document allows writing down an RDF Dataset in a compact
+ textual form. It consists of a sequence of directives, graph statements
+ which contain triple-generating statements and optional blank lines.
+ Comments may be given after a <code>#</code> that is not part of another
+ lexical token and continue to the end of the line.</p>
+ <p>
+
+ <p>Graph statements are a pair of an IRI and a group of triple statements
+ surrounded by <code>{}</code>. The IRI of the graph statement may not be
+ used in another graph statement, but may reoccur as part of any triple
+ statement. Optionally one graph statement may not not be labeled with
+ an IRI. Such a graph statement corresponds to the Default Graph of an
+ RDF Dataset.</p>
+
+ <section id="sec-graph-statements">
+ <h3>Graph Statements</h3>
+ <p class="issue"> Examples should not refer to TriX vocabularies.<p>
+ </p>
+ <p>A RDF Dataset may contain only named graphs.</p>
+
+ <pre class="example">
+ <script type="application/trig"># This document encodes three graphs.
+
+@prefix rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> .
+@prefix xsd: <http://www.w3.org/2001/XMLSchema#> .
+@prefix swp: <http://www.w3.org/2004/03/trix/swp-1/> .
+@prefix dc: <http://purl.org/dc/elements/1.1/> .
+@prefix ex: <http://www.example.org/vocabulary#> .
+@prefix : <http://www.example.org/exampleDocument#> .
+
+:G1 { :Monica ex:name "Monica Murphy" .
+ :Monica ex:homepage <http://www.monicamurphy.org> .
+ :Monica ex:email <mailto:monica@monicamurphy.org> .
+ :Monica ex:hasSkill ex:Management }
+
+:G2 { :Monica rdf:type ex:Person .
+ :Monica ex:hasSkill ex:Programming }
+
+:G3 { :G1 swp:assertedBy _:w1 .
+ _:w1 swp:authority :Chris .
+ _:w1 dc:date "2003-10-02"^^xsd:date .
+ :G2 swp:quotedBy _:w2 .
+ :G3 swp:assertedBy _:w2 .
+ _:w2 dc:date "2003-09-03"^^xsd:date .
+ _:w2 swp:authority :Chris .
+ :Chris rdf:type ex:Person .
+ :Chris ex:email <mailto:chris@bizer.de> }
+ </script>
+ </pre>
+ <p>A RDF Dataset may contain only single graph.</p>
+ <pre class="example">
+ <script type="application/trig"># This document encodes one graph.
+@prefix ex: <http://www.example.org/vocabulary#> .
+@prefix : <http://www.example.org/exampleDocument#> .
+
+:G1 { :Monica a ex:Person ;
+ ex:name "Monica Murphy" ;
+ ex:homepage <http://www.monicamurphy.org> ;
+ ex:email <mailto:monica@monicamurphy.org> ;
+ ex:hasSkill ex:Management ,
+ ex:Programming . } .
+ </script>
+ </pre>
+ <p>A RDF Dataset may contain a default graph, and named graphs.</p>
+ <pre class="example">
+ <script type="application/trig"># This document contains a default graph and two named graphs.
+
+@prefix rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> .
+@prefix dc: <http://purl.org/dc/elements/1.1/> .
+@prefix foaf: <http://xmlns.com/foaf/0.1/> .
+
+# default graph
+ {
+ <http://example.org/bob> dc:publisher "Bob" .
+ <http://example.org/alice> dc:publisher "Alice" .
+ }
+
+<http://example.org/bob>
+ {
+ _:a foaf:name "Bob" .
+ _:a foaf:mbox <mailto:bob@oldcorp.example.org> .
+ }
+
+<http://example.org/alice>
+ {
+ _:a foaf:name "Alice" .
+ _:a foaf:mbox <mailto:alice@work.example.org> .
+ } </script>
+ </pre>
+ </section>
+ <section>
+ <h3>Other Terms</h3>
+ <p>All other terms and directives come from Turtle.</p>
+ </section>
+ </section>
+
+ <section id="sec-syntax">
+ <h2>Syntax</h2>
+
+ </section>
+ <section id="sec-grammar">
+ <h2>TriG Grammar</h2>
+ <p>Defer to Turtle</p>
+ <section id="grammar-ebnf">
+ <h3>Grammar</h3>
+ <p>The <abbr title="Extended Backus–Naur Form">EBNF</abbr> used here is defined in XML 1.0 (Third Edition) [[!EBNF-NOTATION]]. </p>
+ <pre>
+<span data-include="trig.bnf">
+</span>
+ </pre>
+ </p>
+
+ </section>
+ </section>
+ <section id="sec-mime" class="informative">
+ <h2>Media Type and Content Encoding</h2>
+
+ <p>The media type of TriG is <code>application/trig</code>.
+ The content encoding of Turtle content is always UTF-8.
+ See <a href="#sec-mediaReg">Internet Media
+ Type, File Extension and Macintosh File Type</a> for the media type
+ registration form.
+ </p>
+ </section>
+
+ <section id="sec-mediaReg" class="appendix">
+ <h2>Internet Media Type, File Extension and Macintosh File Type</h2>
+ <p class="issue">
+ TODO
+ </p>
+ </section>
+ </body>
+</html>
\ No newline at end of file