update
authorGuus Schreiber <guus.schreiber@vu.nl>
Sun, 15 Dec 2013 22:02:27 +0100
changeset 1574 26ca1781e730
parent 1573 b36bcb51eb06
child 1576 4c3c1cde7b29
update
rdf-new/Overview.html
--- a/rdf-new/Overview.html	Sun Dec 15 21:58:27 2013 +0100
+++ b/rdf-new/Overview.html	Sun Dec 15 22:02:27 2013 +0100
@@ -8,7 +8,7 @@
     
     <style type="text/css">
       figure { text-align: center; }
-      img.graph { width: 80%; }
+      img.graph { width: 95%; }
       table td, table th { border: 1px solid #ddd; padding: 0.2em 0.5em; }
     </style>
   <style>/*****************************************************************
@@ -183,7 +183,7 @@
   <hr />
 </div>
 
-<div class="head" role="contentinfo" id="respecHeader">
+
   <section id="abstract" class="introductory" property="dcterms:abstract" datatype="" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter"><h2 aria-level="1" role="heading" id="h2_abstract">Abstract</h2>
 
     <p>The Resource Description Framework (RDF) is a language for
@@ -202,12 +202,14 @@
           http://www.w3.org/TR/.</em>
         </p>
         
-  The RDF Working Group  expects this document to become a Working
-  Group Note.
+  <p>The RDF Working Group  expects this document to become a Working
+  Group Note.</p>
 
         <p>
           This document was published by the <a href="http://www.w3.org/2011/rdf-wg/">RDF Working Group</a> as a First Public Working Draft.
           
+            This document is intended to become a <abbr title="World Wide Web Consortium">W3C</abbr> Recommendation.
+          
           
             If you wish to make comments regarding this document, please send them to 
             <a href="mailto:[email protected]">[email protected]</a> 
@@ -237,8 +239,6 @@
             Policy</a>.
           
           
-            The group does not expect this document to become a <abbr title="World Wide Web Consortium">W3C</abbr> Recommendation.
-          
           
             
               <abbr title="World Wide Web Consortium">W3C</abbr> maintains a <a rel="disclosure" href="http://www.w3.org/2004/01/pp-impl/46168/status">public list of any patent
@@ -262,7 +262,6 @@
 
 
 
-</div>
 
 <section id="section-introduction" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter">
 	
@@ -314,187 +313,163 @@
 
 <section id="section-abstract-syntax" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter">
 	
-		
+
 <!--OddPage-->
 <h2 aria-level="1" role="heading" id="h2_section-abstract-syntax"><span class="secno">2. </span>Abstract Syntax</h2>
-		
-		<section id="identifiers" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter">
-			
-			<h3 aria-level="2" role="heading" id="h3_identifiers"><span class="secno">2.1 </span>Identifiers</h3>
-			
-			<p>Identifiers in RDF 1.1 are now IRIs.  The following table summarizes specific differences.</p>
-			
-			<table class="simple">
-				<caption>Identifiers in RDF 1.0 and 1.1.</caption>
-				<tbody><tr>
-					<th></th>
-					<th>RDF 1.0</th>
-					<th>RDF 1.1</th>
-				</tr>
-				<tr>
-					<td>
-						Identifiers
-					</td>
-					<td>
-						RDF URI References
-					</td>
-					<td>
-						IRIs
-					</td>
-				</tr>
-				<tr>
-					<td>
-						Additional characters
-					</td>
-					<td>
-						&quot;&lt;&quot;, &quot;&gt;&quot;,
-						&quot;{&quot;, &quot;}&quot;, &quot;|&quot;, &quot;\&quot;, &quot;^&quot;,
-						&quot;`&quot;, ‘&quot;’ (double quote), and &quot; &quot; (space)
-					</td>
-					<td>
-						None; percent-encoding must be used as described in section 2.1 of [<cite><a class="bibref" href="#bib-RFC3986">RFC3986</a></cite>].
-					</td>
-				</tr>
-				<tr>
-					<td>
-						Fragment identifiers
-					</td>
-					<td>
-						Fragment identifiers interpreted in accordance with RDF/XML representation.
-					</td>
-					<td>
-						Full IRIs, including possible fragment identifiers, denote a resource.
-					</td>
-				</tr>
-				<tr>
-					<td>
-						Blank nodes
-					</td>
-					<td>
-						RDF 1.0 makes no reference to any internal structure of blank nodes. Given two
-						blank nodes, it is possible to determine whether or not they are the same.
-					</td>
-					<td>
-						Blank node identifiers are local identifiers that are used in some concrete
-						RDF syntaxes or RDF store implementations. They are always locally scoped to
-						the file or RDF store, and are not persistent or portable identifiers for
-						blank nodes. See the section in Concepts and Abstract Syntax regarding
-						Skolemization if blank nodes must be shared between implementations.
-					</td>
-				</tr>
-			</tbody></table>
-		
-		</section>
-		
-		<section id="literals" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter">
-			
-			<h3 aria-level="2" role="heading" id="h3_literals"><span class="secno">2.2 </span>Literals</h3>
-			
-			<p>The following table summarizes differences in the handling of literals.</p>
+
+<section id="identifiers" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter">
+	
+<h3 aria-level="2" role="heading" id="h3_identifiers"><span class="secno">2.1 </span>Identifiers</h3>
+	
+<p>Identifiers in RDF 1.1 are now IRIs.  The following table
+summarizes specific differences.</p> 
+	
+<table class="simple">
+  <caption>Identifiers in RDF 1.0 and 1.1.</caption>
+  <tbody><tr>
+        <th></th>
+	<th>RDF 1.0</th>
+	<th>RDF 1.1</th>
+  </tr>
+  <tr>
+	<td>Identifiers</td>
+	<td>RDF URI References</td>
+	<td>IRIs</td>
+  </tr>
+  <tr>
+	<td>Additional characters</td>
+	<td>
+	&quot;&lt;&quot;, &quot;&gt;&quot;,
+	&quot;{&quot;, &quot;}&quot;, &quot;|&quot;, &quot;\&quot;, &quot;^&quot;,
+	&quot;`&quot;, ‘&quot;’ (double quote), and &quot; &quot; (space)
+	</td>
+	<td>None; percent-encoding must be used as described in
+        section 2.1 of [<cite><a class="bibref" href="#bib-RFC3986">RFC3986</a></cite>]. </td>
+  </tr>
+  <tr>
+	<td>Fragment identifiers</td>
+	<td>Fragment identifiers interpreted in accordance with RDF/XML representation.
+	</td>
+	<td>Full IRIs, including possible fragment identifiers, denote a resource.
+	</td>
+  </tr>
+  <tr>
+	<td>Blank nodes</td>
+	<td>
+	RDF 1.0 makes no reference to any internal structure of blank nodes. Given two
+	blank nodes, it is possible to determine whether or not they are the same.
+	</td>
+	<td>
+	Blank node identifiers are local identifiers that are used in
+  some concrete RDF syntaxes or RDF store implementations. They are
+  always locally scoped to the file or RDF store, and are not
+  persistent or portable identifiers for blank nodes. See the section
+  in Concepts and Abstract Syntax regarding Skolemization if blank
+  nodes must be shared between implementations. 
+	</td>
+  </tr>
+</tbody></table>
+
+</section>
+
+<section id="literals" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter">
+	
+<h3 aria-level="2" role="heading" id="h3_literals"><span class="secno">2.2 </span>Literals</h3>
+	
+<p>The following table summarizes differences in the handling of literals.</p>
+
+<table class="simple">
+  <caption>Literals in RDF 1.0 and 1.1.</caption>
+  <tbody><tr>
+        <th></th>
+	<th>RDF 1.0</th>
+	<th>RDF 1.1</th>
+  </tr>
+  <tr>
+	<td>Language tags</td>
+	<td>Literals with a language tag did not have a datatype URI.</td>
+	<td>Literals with language tags now have the datatype IRI
+        <code>rdf:langString</code>. </td>
+  </tr>
+  <tr>
+	<td rowspan="2">Simple literals</td>
+	<td>Simple literals could appear directly, e.g. &quot;a literal&quot;.</td>
+	<td>All literals have datatypes; serializations or other
+        implementations might choose to support syntax for simple literals,
+        but only as synonyms for <code>xsd:string</code> literals.</td>
+  </tr>
+  <tr>
+	<td>Control codes in the #x0-#x1F range were permitted.</td>
+	<td>The <code>xsd:string</code> datatype does not permit the
+        #x0 character, and implementations might not permit control codes in
+        the #x1-#x1F range.  A literal with type <code>xsd:string</code>
+        containing the #x0 character is ill-typed. </td>
+  </tr>
+  <tr>
+	<td>Language tags</td>
+	<td>Permitted language tags that adhered to the generic
+        tag/subtag syntax of language tags, but were not well-formed
+        according to [<cite><a class="bibref" href="#bib-BCP47">BCP47</a></cite>]. </td>
+	<td>Language tags must be well-formed according to [<cite><a class="bibref" href="#bib-BCP47">BCP47</a></cite>].</td>
+  </tr>
+</tbody></table>
+	
+<p>Planned updates to DOM version 4 [<cite><a class="bibref" href="#bib-DOM4">DOM4</a></cite>] are not complete as of
+this writing.  The Working	Group decided to
+follow the changes to the DOM in order to support the
+new datatype <code>rdf:HTML</code>. 
+The unfinished status of DOM version 4 is why both
+<code>rdf:HTML</code> and <code>rdf:XMLLiteral</code> are
+non-normative in RDF 1.1 Concepts.  RDF 1.1 Concepts and Abstract
+Syntax clarifies functionality deemed to be
+useful for those including fragments of XML and HTML content in RDF
+serialization formats.</p>
 		
-			<table class="simple">
-				<caption>Literals in RDF 1.0 and 1.1.</caption>
-				<tbody><tr>
-					<th></th>
-					<th>RDF 1.0</th>
-					<th>RDF 1.1</th>
-				</tr>
-				<tr>
-					<td>
-						Language tags
-					</td>
-					<td>
-						Literals with a language tag did not have a datatype URI.
-					</td>
-					<td>
-						Literals with language tags now have the datatype IRI <code>rdf:langString</code>.
-					</td>
-				</tr>
-				<tr>
-					<td rowspan="2">
-						Simple literals
-					</td>
-					<td>
-						Simple literals could appear directly, e.g. &quot;a literal&quot;.
-					</td>
-					<td>
-						All literals have datatypes; serializations or other implementations
-						might choose to support syntax for simple literals, but only as synonyms
-						for <code>xsd:string</code> literals.
-					</td>
-				</tr>
-				<tr>
-					<td>
-						Control codes in the #x0-#x1F range were permitted.
-					</td>
-					<td>
-						The <code>xsd:string</code> datatype does not permit the #x0 character, and implementations
-						might not permit control codes in the #x1-#x1F range.  A literal with type
-						<code>xsd:string</code> containing the #x0 character is ill-typed.
-					</td>
-				</tr>
-				<tr>
-					<td>
-						Language tags
-					</td>
-					<td>
-						Permitted language tags that adhered to the generic tag/subtag syntax
-						of language tags, but were not well-formed according to [<cite><a class="bibref" href="#bib-BCP47">BCP47</a></cite>].
-					</td>
-					<td>
-						Language tags must be well-formed according to [<cite><a class="bibref" href="#bib-BCP47">BCP47</a></cite>].
-					</td>
-				</tr>
-			</tbody></table>
-			
-			<p>Planned updates to DOM version 4 [<cite><a class="bibref" href="#bib-DOM4">DOM4</a></cite>] are not complete as of this writing.  The Working
-				Group decided to follow the changes to the DOM in order to support the new datatype <code>rdf:HTML</code>.
-				The unfinished status of DOM version 4 is why both <code>rdf:HTML</code> and <code>rdf:XMLLiteral</code> are non-normative
-				in RDF 1.1 Concepts.  RDF 1.1 Concepts and Abstract Syntax clarifies functionality deemed to be
-				useful for those including fragments of XML and HTML content in RDF serialization formats.</p>
-				
-		</section>
-			
-		<section id="datasets" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter">
+</section>
+	
+<section id="datasets" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter">
 
-			<h3 aria-level="2" role="heading" id="h3_datasets"><span class="secno">2.3 </span>Datasets</h3>
-			
-			<p>RDF 1.1 introduces the concept of RDF Datasets.  An RDF Dataset is a collection of RDF
-				Graphs.  The semantics of RDF Datasets
-				are minimally specified as of RDF
-				1.1. The Working Group published a
-				draft Note discussing issues related
-				to semantics of datasets [<cite><a class="bibref" href="#bib-RDF11-DATASETS">RDF11-DATASETS</a></cite>].</p>
-				
-			<p>RDF Graphs may be named using an IRI or a blank node.  RDF Graphs that are so named are
-				called named graphs.</p>
-				
-			<p>RDF 1.1 includes three new serialization formats capable of representing multiple graphs.</p>
-			
-		</section>
-
-		<section id="datatypes" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter">
+<h3 aria-level="2" role="heading" id="h3_datasets"><span class="secno">2.3 </span>Datasets</h3>
 	
-		<h3 aria-level="2" role="heading" id="h3_datatypes"><span class="secno">2.4 </span>Datatypes</h3>
-	
-			<p>A table of RDF-compatible XSD datatypes has been added to RDF 1.1 Concepts and
-				Abstract Syntax.  Any XSD datatypes not represented in this table are incompatible
-				with RDF.  The following XSD 1.1 datatypes were added to the list of
-				RDF-compatible datatypes:</p>
+<p>RDF 1.1 introduces the concept of RDF Datasets.  An RDF Dataset is a collection of RDF
+Graphs.  The semantics of RDF Datasets
+are minimally specified as of RDF
+1.1. The Working Group published a
+draft Note discussing issues related
+to semantics of datasets [<cite><a class="bibref" href="#bib-RDF11-DATASETS">RDF11-DATASETS</a></cite>].</p>
+		
+<p>RDF Graphs may be named using an IRI or a blank node.  RDF Graphs that are so named are
+called named graphs.</p>
+		
+<p>RDF 1.1 includes three new serialization formats capable of
+representing multiple graphs.</p> 
 	
-			<ul>
-				<li><code>xsd:duration</code></li>
-				<li><code>xsd:dayTimeDuration</code></li>
-				<li><code>xsd:yearMonthDuration</code></li>
-				<li><code>xsd:dateTimeStamp</code></li>
-			</ul>
-		
-			<p>Support for <code>rdf:XMLLiteral</code> support is now optional.  Technically, support for
-				any individual datatype is optional and therefore may not be present in a given
-				implementation.  RDF-conformant specifications may require specific datatype maps.</p>
-		
-		</section>
-		
+</section>
+
+<section id="datatypes" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter">
+	
+<h3 aria-level="2" role="heading" id="h3_datatypes"><span class="secno">2.4 </span>Datatypes</h3>
+	
+<p>A table of RDF-compatible XSD datatypes has been added to RDF 1.1 Concepts and
+Abstract Syntax.  Any XSD datatypes not represented in this table are incompatible
+with RDF.  The following XSD 1.1 datatypes were added to the list of
+RDF-compatible datatypes:</p>
+	
+<ul>
+  <li><code>xsd:duration</code></li>
+  <li><code>xsd:dayTimeDuration</code></li>
+  <li><code>xsd:yearMonthDuration</code></li>
+  <li><code>xsd:dateTimeStamp</code></li>
+</ul>
+
+<p>Support for <code>rdf:XMLLiteral</code> support is now
+optional.  Technically, support for 
+any individual datatype is optional and therefore may not be present in a given
+implementation.  RDF-conformant specifications may require specific
+datatype maps.</p> 
+
+</section>
+
 </section>
 
 <section id="section-serializations" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter">
@@ -502,7 +477,7 @@
 
 <!--OddPage-->
 <h2 aria-level="1" role="heading" id="h2_section-serializations"><span class="secno">3. </span>New Serialization Formats</h2>
-		
+
 <p>RDF 1.1 introduces a number of new serialization formats. RDF 1.1 Concepts and
 Abstract Syntax makes it clear that RDF/XML is no longer the only recommended serialization
 format; RDF itself should be considered to be the data model (the
@@ -512,7 +487,7 @@
   <img src="serialization-formats.png" class="graph" />
   <figcaption>Fig. <span class="figno">1</span> <span class="fig-title">RDF 1.0 and 1.1 serialization formats</span></figcaption>
 </figure>
-		
+
 </section>
 
 <section id="section-semantics" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter">
@@ -527,7 +502,7 @@
 <p>Datatype entailment formally refers to a set of 'recognized' datatypes,
 replacing datatype maps in RDF 1.0 Semantics, but this does not have any
 effect on implementation.</p>
-		
+
 <p>Datatype entailment formally refers to a set of 'recognized' datatype IRIs.
 The RDF 1.0 Semantics used the concept of a datatype map: in the new semantic
 description, this is the mapping from recognized IRIs to the datatypes they