--- a/trig/index.html Sat Jun 15 12:18:41 2013 -0700
+++ b/trig/index.html Sat Jun 15 12:31:25 2013 -0700
@@ -142,11 +142,10 @@
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 be
- used in another graph statement which implies merging the tripes generated
- by each graph statement, and may reoccur as part of any triple statement.
- Optionally one graph statement may not not be labeled with an IRI. Such a
+ <p>Graph statements are a pair of an IRI or blank node label and a group of triple statements
+ surrounded by <code>{}</code>. The IRI or blank node label of the graph statement may be used in another graph statement which implies taking the union of the tripes generated
+ by each graph statement. A IRI or blank node label used as a graph label may also reoccur as part of any triple statement.
+ Optionally a graph statement may not not be labeled with an IRI. Such a
graph statement corresponds to the Default Graph of an RDF Dataset.</p>
<p>
The construction of an RDF Dataset from a TriG document is defined in <a href="#sec-grammar" class="sectionRef">TriG Grammar</a> and <a href="#sec-parsing" class="sectionRef">Parsing</a>.
@@ -155,9 +154,9 @@
<section id="sec-graph-statements">
<h3>Graph Statements</h3>
- <p>A graph statement pairs an IRI with a RDF Graph. The triple statements that make up the graph are enclosed in <code>{}</code>.</p>
+ <p>A graph statement pairs an IRI or blank node with a RDF graph. The triple statements that make up the graph are enclosed in <code>{}</code>.</p>
- <p>In a TriG document a graph IRI MAY be used to label more then one graph. The IRI of a graph statement may be omitted. In this case the graph is considered the default graph of the RDF Dataset.</p>
+ <p>In a TriG document a graph IRI or blank node MAY be used to label more then one graph. The graph name of a graph statement may be omitted. In this case the graph is considered the default graph of the RDF Dataset.</p>
<p>A RDF Dataset may contain only a single graph.</p>
<pre class="example">
@@ -202,7 +201,7 @@
<p class="issue">
A provenance example
</p>
- <p class="issue">A verisions example</p>
+ <p class="issue">A versions example</p>
<p class="issue">A web snapshot example</p>
</section>
<section id="other-terms">
@@ -271,7 +270,7 @@
<p>
The <code>@base</code> directive defines the Base IRI used to resolve relative IRIs per RFC3986 section 5.1.1, "Base URI Embedded in Content".
Section 5.1.2, "Base URI from the Encapsulating Entity" defines how the In-Scope Base IRI may come from an encapsulating document, such as a SOAP envelope with an xml:base directive or a mime multipart document with a Content-Location header.
- The "Retrieval URI" identified in 5.1.3, Base "URI from the Retrieval URI", is the URL from which a particular Turtle document was retrieved.
+ The "Retrieval URI" identified in 5.1.3, Base "URI from the Retrieval URI", is the URL from which a particular TriG document was retrieved.
If none of the above specifies the Base URI, the default Base URI (section 5.1.4, "Default Base URI") is used.
Each <code>@base</code> directive sets a new In-Scope Base URI, relative to the previous one.
</p>
@@ -443,7 +442,7 @@
<section id="sec-parsing">
<h2>Parsing</h2>
<p class="issue">
- Define a method of parsing that treats each graph statement as a Turtle document. Merge any graph statements that have the same label, or if they don't have a label merge to form the default graph.
+ Define a method of parsing that treats each graph statement as a Turtle document. Union any graph statements that have the same label, or if they don't have a label merge to form the default graph.
</p>
</section>
<section id="sec-differences" class="appendix informative">