--- a/rdf-xml/Overview.html Fri Dec 20 13:28:51 2013 +0100
+++ b/rdf-xml/Overview.html Fri Dec 20 13:40:27 2013 +0100
@@ -7,7 +7,7 @@
<style type="text/css">
- figure { with: 76% }
+ figure { width: 76% ; text-align: center}
.figure { font-weight: bold; text-align: center; }
table.xsd-types td, table.xsd-types th { border: 1px solid #ddd; padding: 0.1em 0.5em; }
</style>
@@ -201,7 +201,7 @@
<a href="http://www.w3.org/"><img width="72" height="48" alt="W3C" src="https://www.w3.org/Icons/w3c_home" /></a>
</p>
- <h1 property="dcterms:title" id="title" class="title p-name"><abbr title="Resource Description Framework">RDF</abbr> 1.1 XML Syntax</h1>
+ <h1 property="dcterms:title" id="title" class="title p-name">RDF 1.1 XML Syntax</h1>
<h2 content="2014-01-08T23:00:00.000Z" datatype="xsd:dateTime" property="dcterms:issued" id="w3c-proposed-edited-recommendation-09-january-2014"><abbr title="World Wide Web Consortium">W3C</abbr> Proposed Edited Recommendation <time datetime="2014-01-09" class="dt-published">09 January 2014</time></h2>
<dl>
@@ -286,11 +286,11 @@
<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
- (<abbr title="Resource Description Framework">RDF</abbr>) is a
+ (RDF) is a
general-purpose language for representing information in the Web.</p>
<p>This document defines an XML
- syntax for <abbr title="Resource Description Framework">RDF</abbr> called <abbr title="Resource Description Framework">RDF</abbr>/XML in terms of
+ syntax for RDF called RDF/XML in terms of
Namespaces in XML, the XML Information Set
and XML Base.</p>
@@ -305,16 +305,16 @@
http://www.w3.org/TR/.</em>
</p>
- <p>This document is an edited version of the 2004 <abbr title="Resource Description Framework">RDF</abbr> XML Syntax
+ <p>This document is an edited version of the 2004 RDF XML Syntax
Specification Recommendation. The purpose of this revision is
to make this
- document available as part of the <abbr title="Resource Description Framework">RDF</abbr> 1.1 document set. Changes are
+ document available as part of the RDF 1.1 document set. Changes are
limited to revised references, terminology updates, and adaptations to
the introduction.
The technical content of the document is unchanged. Details of the changes
are listed in the <a href="#changes-rdf11">Changes</a> section.</p>
<p>
- This document was published by the <a href="http://www.w3.org/2011/rdf-wg/"><abbr title="Resource Description Framework">RDF</abbr> Working Group</a> as a Proposed Edited Recommendation.
+ This document was published by the <a href="http://www.w3.org/2011/rdf-wg/">RDF Working Group</a> as a Proposed Edited Recommendation.
This document is intended to become a <abbr title="World Wide Web Consortium">W3C</abbr> Recommendation.
@@ -366,7 +366,7 @@
-</section><section id="toc"><h2 class="introductory" aria-level="1" role="heading" id="h2_toc">Table of Contents</h2><ul class="toc" role="directory" id="respecContents"><li class="tocline"><a href="#section-Introduction" class="tocxref"><span class="secno">1. </span>Introduction</a></li><li class="tocline"><a href="#section-Syntax" class="tocxref"><span class="secno">2. </span>An XML Syntax for <abbr title="Resource Description Framework">RDF</abbr></a><ul class="toc"><li class="tocline"><a href="#section-Syntax-intro" class="tocxref"><span class="secno">2.1 </span>Introduction</a></li><li class="tocline"><a href="#section-Syntax-node-property-elements" class="tocxref"><span class="secno">2.2 </span>Node Elements and Property Elements</a></li><li class="tocline"><a href="#section-Syntax-multiple-property-elements" class="tocxref"><span class="secno">2.3 </span>Multiple Property Elements</a></li><li class="tocline"><a href="#section-Syntax-empty-property-elements" class="tocxref"><span class="secno">2.4 </span>Empty Property Elements</a></li><li class="tocline"><a href="#section-Syntax-property-attributes" class="tocxref"><span class="secno">2.5 </span>Property Attributes</a></li><li class="tocline"><a href="#section-Syntax-complete-document" class="tocxref"><span class="secno">2.6 </span>Completing the Document: Document Element and XML Declaration</a></li><li class="tocline"><a href="#section-Syntax-languages" class="tocxref"><span class="secno">2.7 </span>Languages: <code>xml:lang</code></a></li><li class="tocline"><a href="#section-Syntax-XML-literals" class="tocxref"><span class="secno">2.8 </span>XML Literals: <code>rdf:parseType="Literal"</code></a></li><li class="tocline"><a href="#section-Syntax-datatyped-literals" class="tocxref"><span class="secno">2.9 </span>Typed Literals: <code>rdf:datatype</code></a></li><li class="tocline"><a href="#section-Syntax-blank-nodes" class="tocxref"><span class="secno">2.10 </span>Identifying Blank Nodes: <code>rdf:nodeID</code></a></li><li class="tocline"><a href="#section-Syntax-parsetype-resource" class="tocxref"><span class="secno">2.11 </span>Omitting Blank Nodes: <code>rdf:parseType="Resource"</code></a></li><li class="tocline"><a href="#section-Syntax-property-attributes-on-property-element" class="tocxref"><span class="secno">2.12 </span>Omitting Nodes: Property Attributes on an empty Property Element</a></li><li class="tocline"><a href="#section-Syntax-typed-nodes" class="tocxref"><span class="secno">2.13 </span>Typed Node Elements</a></li><li class="tocline"><a href="#section-Syntax-ID-xml-base" class="tocxref"><span class="secno">2.14 </span>Abbreviating URIs: <code>rdf:ID</code> and <code>xml:base</code></a></li><li class="tocline"><a href="#section-Syntax-list-elements" class="tocxref"><span class="secno">2.15 </span>Container Membership Property Elements: <code>rdf:li</code> and <code>rdf:_</code><em>n</em></a></li><li class="tocline"><a href="#section-Syntax-parsetype-Collection" class="tocxref"><span class="secno">2.16 </span>Collections: <code>rdf:parseType="Collection"</code></a></li><li class="tocline"><a href="#section-Syntax-reifying" class="tocxref"><span class="secno">2.17 </span>Reifying Statements: <code>rdf:ID</code></a></li></ul></li><li class="tocline"><a href="#section-Terminology" class="tocxref"><span class="secno">3. </span>Terminology</a></li><li class="tocline"><a href="#section-MIME-Type" class="tocxref"><span class="secno">4. </span><abbr title="Resource Description Framework">RDF</abbr> MIME Type, File Extension and Macintosh File Type</a></li><li class="tocline"><a href="#section-Global" class="tocxref"><span class="secno">5. </span>Global Issues</a><ul class="toc"><li class="tocline"><a href="#section-Namespace" class="tocxref"><span class="secno">5.1 </span>The <abbr title="Resource Description Framework">RDF</abbr> Namespace and Vocabulary</a></li><li class="tocline"><a href="#section-Identifiers" class="tocxref"><span class="secno">5.2 </span>Identifiers</a></li><li class="tocline"><a href="#section-baseURIs" class="tocxref"><span class="secno">5.3 </span>Resolving IRIs</a></li><li class="tocline"><a href="#section-constraints" class="tocxref"><span class="secno">5.4 </span>Constraints</a></li><li class="tocline"><a href="#section-conformance" class="tocxref"><span class="secno">5.5 </span>Conformance</a></li></ul></li><li class="tocline"><a href="#section-Data-Model" class="tocxref"><span class="secno">6. </span>Syntax Data Model</a><ul class="toc"><li class="tocline"><a href="#section-Nodes" class="tocxref"><span class="secno">6.1 </span>Events</a><ul class="toc"><li class="tocline"><a href="#section-root-node" class="tocxref"><span class="secno">6.1.1 </span>Root Event</a></li><li class="tocline"><a href="#section-element-node" class="tocxref"><span class="secno">6.1.2 </span>Element Event</a></li><li class="tocline"><a href="#section-end-element-node" class="tocxref"><span class="secno">6.1.3 </span>End Element Event</a></li><li class="tocline"><a href="#section-attribute-node" class="tocxref"><span class="secno">6.1.4 </span>Attribute Event</a></li><li class="tocline"><a href="#section-text-node" class="tocxref"><span class="secno">6.1.5 </span>Text Event</a></li><li class="tocline"><a href="#section-identifier-node" class="tocxref"><span class="secno">6.1.6 </span>IRI Event</a></li><li class="tocline"><a href="#section-blank-nodeid-event" class="tocxref"><span class="secno">6.1.7 </span>Blank Node Identifier Event</a></li><li class="tocline"><a href="#section-literal-node" class="tocxref"><span class="secno">6.1.8 </span>Plain Literal Event</a></li><li class="tocline"><a href="#section-typed-literal-node" class="tocxref"><span class="secno">6.1.9 </span>Typed Literal Event</a></li></ul></li><li class="tocline"><a href="#section-Infoset-Mapping" class="tocxref"><span class="secno">6.2 </span>Information Set Mapping</a></li><li class="tocline"><a href="#section-Infoset-Grammar-Notation" class="tocxref"><span class="secno">6.3 </span>Grammar Notation</a><ul class="toc"><li class="tocline"><a href="#section-Infoset-Grammar-General" class="tocxref"><span class="secno">6.3.1 </span>Grammar General Notation</a></li><li class="tocline"><a href="#section-Infoset-Grammar-Matching" class="tocxref"><span class="secno">6.3.2 </span>Grammar Event Matching Notation</a></li><li class="tocline"><a href="#section-Infoset-Grammar-Action" class="tocxref"><span class="secno">6.3.3 </span>Grammar Action Notation</a></li></ul></li></ul></li><li class="tocline"><a href="#section-Infoset-Grammar" class="tocxref"><span class="secno">7. </span><abbr title="Resource Description Framework">RDF</abbr>/XML Grammar</a><ul class="toc"><li class="tocline"><a href="#section-grammar-summary" class="tocxref"><span class="secno">7.1 </span>Grammar summary</a></li><li class="tocline"><a href="#section-grammar-productions" class="tocxref"><span class="secno">7.2 </span>Grammar Productions</a><ul class="toc"><li class="tocline"><a href="#start" class="tocxref"><span class="secno">7.2.1 </span>Grammar start</a></li><li class="tocline"><a href="#coreSyntaxTerms" class="tocxref"><span class="secno">7.2.2 </span>Production coreSyntaxTerms</a></li><li class="tocline"><a href="#syntaxTerms" class="tocxref"><span class="secno">7.2.3 </span>Production syntaxTerms</a></li><li class="tocline"><a href="#oldTerms" class="tocxref"><span class="secno">7.2.4 </span>Production oldTerms</a></li><li class="tocline"><a href="#nodeElementURIs" class="tocxref"><span class="secno">7.2.5 </span>Production nodeElementURIs</a></li><li class="tocline"><a href="#propertyElementURIs" class="tocxref"><span class="secno">7.2.6 </span>Production propertyElementURIs</a></li><li class="tocline"><a href="#propertyAttributeURIs" class="tocxref"><span class="secno">7.2.7 </span>Production propertyAttributeURIs</a></li><li class="tocline"><a href="#doc" class="tocxref"><span class="secno">7.2.8 </span>Production doc</a></li><li class="tocline"><a href="#RDF" class="tocxref"><span class="secno">7.2.9 </span>Production <abbr title="Resource Description Framework">RDF</abbr></a></li><li class="tocline"><a href="#nodeElementList" class="tocxref"><span class="secno">7.2.10 </span>Production nodeElementList</a></li><li class="tocline"><a href="#nodeElement" class="tocxref"><span class="secno">7.2.11 </span>Production nodeElement</a></li><li class="tocline"><a href="#ws" class="tocxref"><span class="secno">7.2.12 </span>Production ws</a></li><li class="tocline"><a href="#propertyEltList" class="tocxref"><span class="secno">7.2.13 </span>Production propertyEltList</a></li><li class="tocline"><a href="#propertyElt" class="tocxref"><span class="secno">7.2.14 </span>Production propertyElt</a></li><li class="tocline"><a href="#resourcePropertyElt" class="tocxref"><span class="secno">7.2.15 </span>Production resourcePropertyElt</a></li><li class="tocline"><a href="#literalPropertyElt" class="tocxref"><span class="secno">7.2.16 </span>Production literalPropertyElt</a></li><li class="tocline"><a href="#parseTypeLiteralPropertyElt" class="tocxref"><span class="secno">7.2.17 </span>Production parseTypeLiteralPropertyElt</a></li><li class="tocline"><a href="#parseTypeResourcePropertyElt" class="tocxref"><span class="secno">7.2.18 </span>Production parseTypeResourcePropertyElt</a></li><li class="tocline"><a href="#parseTypeCollectionPropertyElt" class="tocxref"><span class="secno">7.2.19 </span>Production parseTypeCollectionPropertyElt</a></li><li class="tocline"><a href="#parseTypeOtherPropertyElt" class="tocxref"><span class="secno">7.2.20 </span>Production parseTypeOtherPropertyElt</a></li><li class="tocline"><a href="#emptyPropertyElt" class="tocxref"><span class="secno">7.2.21 </span>Production emptyPropertyElt</a></li><li class="tocline"><a href="#idAttr" class="tocxref"><span class="secno">7.2.22 </span>Production idAttr</a></li><li class="tocline"><a href="#nodeIdAttr" class="tocxref"><span class="secno">7.2.23 </span>Production nodeIdAttr</a></li><li class="tocline"><a href="#aboutAttr" class="tocxref"><span class="secno">7.2.24 </span>Production aboutAttr</a></li><li class="tocline"><a href="#propertyAttr" class="tocxref"><span class="secno">7.2.25 </span>Production propertyAttr</a></li><li class="tocline"><a href="#resourceAttr" class="tocxref"><span class="secno">7.2.26 </span>Production resourceAttr</a></li><li class="tocline"><a href="#datatypeAttr" class="tocxref"><span class="secno">7.2.27 </span>Production datatypeAttr</a></li><li class="tocline"><a href="#parseLiteral" class="tocxref"><span class="secno">7.2.28 </span>Production parseLiteral</a></li><li class="tocline"><a href="#parseResource" class="tocxref"><span class="secno">7.2.29 </span>Production parseResource</a></li><li class="tocline"><a href="#parseCollection" class="tocxref"><span class="secno">7.2.30 </span>Production parseCollection</a></li><li class="tocline"><a href="#parseOther" class="tocxref"><span class="secno">7.2.31 </span>Production parseOther</a></li><li class="tocline"><a href="#URI-reference" class="tocxref"><span class="secno">7.2.32 </span>Production IRI</a></li><li class="tocline"><a href="#literal" class="tocxref"><span class="secno">7.2.33 </span>Production literal</a></li><li class="tocline"><a href="#rdf-id" class="tocxref"><span class="secno">7.2.34 </span>Production rdf-id</a></li></ul></li><li class="tocline"><a href="#section-Reification" class="tocxref"><span class="secno">7.3 </span>Reification Rules</a></li><li class="tocline"><a href="#section-List-Expand" class="tocxref"><span class="secno">7.4 </span>List Expansion Rules</a></li></ul></li><li class="tocline"><a href="#section-Serialising" class="tocxref"><span class="secno">8. </span>Serializing an <abbr title="Resource Description Framework">RDF</abbr> Graph to <abbr title="Resource Description Framework">RDF</abbr>/XML</a></li><li class="tocline"><a href="#section-rdf-in-SVG" class="tocxref"><span class="secno">9. </span>Using <abbr title="Resource Description Framework">RDF</abbr>/XML with SVG</a></li><li class="tocline"><a href="#section-Acknowledgments" class="tocxref"><span class="secno">A. </span>Acknowledgments</a></li><li class="tocline"><a href="#section-Schemas" class="tocxref"><span class="secno">B. </span>Syntax Schemas</a><ul class="toc"><li class="tocline"><a href="#section-RELAXNG-Schema" class="tocxref"><span class="secno">B.1 </span>RELAX NG Compact Schema</a></li></ul></li><li class="tocline"><a href="#section-changes" class="tocxref"><span class="secno">C. </span>Changes</a><ul class="toc"><li class="tocline"><a href="#changes-rdf11" class="tocxref"><span class="secno">C.1 </span>Changes since 2004 Recommendation</a></li><li class="tocline"><a href="#changes-2004" class="tocxref"><span class="secno">C.2 </span>Revisions since Draft 10 October 2003</a><ul class="toc"><li class="tocline"><a href="#section-Changes-non-editorial" class="tocxref"><span class="secno">C.2.1 </span>Non-Editorial Revisions</a></li><li class="tocline"><a href="#section-Changes-editorial" class="tocxref"><span class="secno">C.2.2 </span>Editorial Revisions</a></li><li class="tocline"><a href="#section-Changes-none" class="tocxref"><span class="secno">C.2.3 </span>Issues requiring no document revisions</a></li></ul></li></ul></li><li class="tocline"><a href="#references" class="tocxref"><span class="secno">D. </span>References</a><ul class="toc"><li class="tocline"><a href="#normative-references" class="tocxref"><span class="secno">D.1 </span>Normative references</a></li><li class="tocline"><a href="#informative-references" class="tocxref"><span class="secno">D.2 </span>Informative references</a></li></ul></li></ul></section>
+</section><section id="toc"><h2 class="introductory" aria-level="1" role="heading" id="h2_toc">Table of Contents</h2><ul class="toc" role="directory" id="respecContents"><li class="tocline"><a href="#section-Introduction" class="tocxref"><span class="secno">1. </span>Introduction</a></li><li class="tocline"><a href="#section-Syntax" class="tocxref"><span class="secno">2. </span>An XML Syntax for RDF</a><ul class="toc"><li class="tocline"><a href="#section-Syntax-intro" class="tocxref"><span class="secno">2.1 </span>Introduction</a></li><li class="tocline"><a href="#section-Syntax-node-property-elements" class="tocxref"><span class="secno">2.2 </span>Node Elements and Property Elements</a></li><li class="tocline"><a href="#section-Syntax-multiple-property-elements" class="tocxref"><span class="secno">2.3 </span>Multiple Property Elements</a></li><li class="tocline"><a href="#section-Syntax-empty-property-elements" class="tocxref"><span class="secno">2.4 </span>Empty Property Elements</a></li><li class="tocline"><a href="#section-Syntax-property-attributes" class="tocxref"><span class="secno">2.5 </span>Property Attributes</a></li><li class="tocline"><a href="#section-Syntax-complete-document" class="tocxref"><span class="secno">2.6 </span>Completing the Document: Document Element and XML Declaration</a></li><li class="tocline"><a href="#section-Syntax-languages" class="tocxref"><span class="secno">2.7 </span>Languages: <code>xml:lang</code></a></li><li class="tocline"><a href="#section-Syntax-XML-literals" class="tocxref"><span class="secno">2.8 </span>XML Literals: <code>rdf:parseType="Literal"</code></a></li><li class="tocline"><a href="#section-Syntax-datatyped-literals" class="tocxref"><span class="secno">2.9 </span>Typed Literals: <code>rdf:datatype</code></a></li><li class="tocline"><a href="#section-Syntax-blank-nodes" class="tocxref"><span class="secno">2.10 </span>Identifying Blank Nodes: <code>rdf:nodeID</code></a></li><li class="tocline"><a href="#section-Syntax-parsetype-resource" class="tocxref"><span class="secno">2.11 </span>Omitting Blank Nodes: <code>rdf:parseType="Resource"</code></a></li><li class="tocline"><a href="#section-Syntax-property-attributes-on-property-element" class="tocxref"><span class="secno">2.12 </span>Omitting Nodes: Property Attributes on an empty Property Element</a></li><li class="tocline"><a href="#section-Syntax-typed-nodes" class="tocxref"><span class="secno">2.13 </span>Typed Node Elements</a></li><li class="tocline"><a href="#section-Syntax-ID-xml-base" class="tocxref"><span class="secno">2.14 </span>Abbreviating URIs: <code>rdf:ID</code> and <code>xml:base</code></a></li><li class="tocline"><a href="#section-Syntax-list-elements" class="tocxref"><span class="secno">2.15 </span>Container Membership Property Elements: <code>rdf:li</code> and <code>rdf:_</code><em>n</em></a></li><li class="tocline"><a href="#section-Syntax-parsetype-Collection" class="tocxref"><span class="secno">2.16 </span>Collections: <code>rdf:parseType="Collection"</code></a></li><li class="tocline"><a href="#section-Syntax-reifying" class="tocxref"><span class="secno">2.17 </span>Reifying Statements: <code>rdf:ID</code></a></li></ul></li><li class="tocline"><a href="#section-Terminology" class="tocxref"><span class="secno">3. </span>Terminology</a></li><li class="tocline"><a href="#section-MIME-Type" class="tocxref"><span class="secno">4. </span>RDF MIME Type, File Extension and Macintosh File Type</a></li><li class="tocline"><a href="#section-Global" class="tocxref"><span class="secno">5. </span>Global Issues</a><ul class="toc"><li class="tocline"><a href="#section-Namespace" class="tocxref"><span class="secno">5.1 </span>The RDF Namespace and Vocabulary</a></li><li class="tocline"><a href="#section-Identifiers" class="tocxref"><span class="secno">5.2 </span>Identifiers</a></li><li class="tocline"><a href="#section-baseURIs" class="tocxref"><span class="secno">5.3 </span>Resolving IRIs</a></li><li class="tocline"><a href="#section-constraints" class="tocxref"><span class="secno">5.4 </span>Constraints</a></li><li class="tocline"><a href="#section-conformance" class="tocxref"><span class="secno">5.5 </span>Conformance</a></li></ul></li><li class="tocline"><a href="#section-Data-Model" class="tocxref"><span class="secno">6. </span>Syntax Data Model</a><ul class="toc"><li class="tocline"><a href="#section-Nodes" class="tocxref"><span class="secno">6.1 </span>Events</a><ul class="toc"><li class="tocline"><a href="#section-root-node" class="tocxref"><span class="secno">6.1.1 </span>Root Event</a></li><li class="tocline"><a href="#section-element-node" class="tocxref"><span class="secno">6.1.2 </span>Element Event</a></li><li class="tocline"><a href="#section-end-element-node" class="tocxref"><span class="secno">6.1.3 </span>End Element Event</a></li><li class="tocline"><a href="#section-attribute-node" class="tocxref"><span class="secno">6.1.4 </span>Attribute Event</a></li><li class="tocline"><a href="#section-text-node" class="tocxref"><span class="secno">6.1.5 </span>Text Event</a></li><li class="tocline"><a href="#section-identifier-node" class="tocxref"><span class="secno">6.1.6 </span>IRI Event</a></li><li class="tocline"><a href="#section-blank-nodeid-event" class="tocxref"><span class="secno">6.1.7 </span>Blank Node Identifier Event</a></li><li class="tocline"><a href="#section-literal-node" class="tocxref"><span class="secno">6.1.8 </span>Plain Literal Event</a></li><li class="tocline"><a href="#section-typed-literal-node" class="tocxref"><span class="secno">6.1.9 </span>Typed Literal Event</a></li></ul></li><li class="tocline"><a href="#section-Infoset-Mapping" class="tocxref"><span class="secno">6.2 </span>Information Set Mapping</a></li><li class="tocline"><a href="#section-Infoset-Grammar-Notation" class="tocxref"><span class="secno">6.3 </span>Grammar Notation</a><ul class="toc"><li class="tocline"><a href="#section-Infoset-Grammar-General" class="tocxref"><span class="secno">6.3.1 </span>Grammar General Notation</a></li><li class="tocline"><a href="#section-Infoset-Grammar-Matching" class="tocxref"><span class="secno">6.3.2 </span>Grammar Event Matching Notation</a></li><li class="tocline"><a href="#section-Infoset-Grammar-Action" class="tocxref"><span class="secno">6.3.3 </span>Grammar Action Notation</a></li></ul></li></ul></li><li class="tocline"><a href="#section-Infoset-Grammar" class="tocxref"><span class="secno">7. </span>RDF/XML Grammar</a><ul class="toc"><li class="tocline"><a href="#section-grammar-summary" class="tocxref"><span class="secno">7.1 </span>Grammar summary</a></li><li class="tocline"><a href="#section-grammar-productions" class="tocxref"><span class="secno">7.2 </span>Grammar Productions</a><ul class="toc"><li class="tocline"><a href="#start" class="tocxref"><span class="secno">7.2.1 </span>Grammar start</a></li><li class="tocline"><a href="#coreSyntaxTerms" class="tocxref"><span class="secno">7.2.2 </span>Production coreSyntaxTerms</a></li><li class="tocline"><a href="#syntaxTerms" class="tocxref"><span class="secno">7.2.3 </span>Production syntaxTerms</a></li><li class="tocline"><a href="#oldTerms" class="tocxref"><span class="secno">7.2.4 </span>Production oldTerms</a></li><li class="tocline"><a href="#nodeElementURIs" class="tocxref"><span class="secno">7.2.5 </span>Production nodeElementURIs</a></li><li class="tocline"><a href="#propertyElementURIs" class="tocxref"><span class="secno">7.2.6 </span>Production propertyElementURIs</a></li><li class="tocline"><a href="#propertyAttributeURIs" class="tocxref"><span class="secno">7.2.7 </span>Production propertyAttributeURIs</a></li><li class="tocline"><a href="#doc" class="tocxref"><span class="secno">7.2.8 </span>Production doc</a></li><li class="tocline"><a href="#RDF" class="tocxref"><span class="secno">7.2.9 </span>Production RDF</a></li><li class="tocline"><a href="#nodeElementList" class="tocxref"><span class="secno">7.2.10 </span>Production nodeElementList</a></li><li class="tocline"><a href="#nodeElement" class="tocxref"><span class="secno">7.2.11 </span>Production nodeElement</a></li><li class="tocline"><a href="#ws" class="tocxref"><span class="secno">7.2.12 </span>Production ws</a></li><li class="tocline"><a href="#propertyEltList" class="tocxref"><span class="secno">7.2.13 </span>Production propertyEltList</a></li><li class="tocline"><a href="#propertyElt" class="tocxref"><span class="secno">7.2.14 </span>Production propertyElt</a></li><li class="tocline"><a href="#resourcePropertyElt" class="tocxref"><span class="secno">7.2.15 </span>Production resourcePropertyElt</a></li><li class="tocline"><a href="#literalPropertyElt" class="tocxref"><span class="secno">7.2.16 </span>Production literalPropertyElt</a></li><li class="tocline"><a href="#parseTypeLiteralPropertyElt" class="tocxref"><span class="secno">7.2.17 </span>Production parseTypeLiteralPropertyElt</a></li><li class="tocline"><a href="#parseTypeResourcePropertyElt" class="tocxref"><span class="secno">7.2.18 </span>Production parseTypeResourcePropertyElt</a></li><li class="tocline"><a href="#parseTypeCollectionPropertyElt" class="tocxref"><span class="secno">7.2.19 </span>Production parseTypeCollectionPropertyElt</a></li><li class="tocline"><a href="#parseTypeOtherPropertyElt" class="tocxref"><span class="secno">7.2.20 </span>Production parseTypeOtherPropertyElt</a></li><li class="tocline"><a href="#emptyPropertyElt" class="tocxref"><span class="secno">7.2.21 </span>Production emptyPropertyElt</a></li><li class="tocline"><a href="#idAttr" class="tocxref"><span class="secno">7.2.22 </span>Production idAttr</a></li><li class="tocline"><a href="#nodeIdAttr" class="tocxref"><span class="secno">7.2.23 </span>Production nodeIdAttr</a></li><li class="tocline"><a href="#aboutAttr" class="tocxref"><span class="secno">7.2.24 </span>Production aboutAttr</a></li><li class="tocline"><a href="#propertyAttr" class="tocxref"><span class="secno">7.2.25 </span>Production propertyAttr</a></li><li class="tocline"><a href="#resourceAttr" class="tocxref"><span class="secno">7.2.26 </span>Production resourceAttr</a></li><li class="tocline"><a href="#datatypeAttr" class="tocxref"><span class="secno">7.2.27 </span>Production datatypeAttr</a></li><li class="tocline"><a href="#parseLiteral" class="tocxref"><span class="secno">7.2.28 </span>Production parseLiteral</a></li><li class="tocline"><a href="#parseResource" class="tocxref"><span class="secno">7.2.29 </span>Production parseResource</a></li><li class="tocline"><a href="#parseCollection" class="tocxref"><span class="secno">7.2.30 </span>Production parseCollection</a></li><li class="tocline"><a href="#parseOther" class="tocxref"><span class="secno">7.2.31 </span>Production parseOther</a></li><li class="tocline"><a href="#URI-reference" class="tocxref"><span class="secno">7.2.32 </span>Production IRI</a></li><li class="tocline"><a href="#literal" class="tocxref"><span class="secno">7.2.33 </span>Production literal</a></li><li class="tocline"><a href="#rdf-id" class="tocxref"><span class="secno">7.2.34 </span>Production rdf-id</a></li></ul></li><li class="tocline"><a href="#section-Reification" class="tocxref"><span class="secno">7.3 </span>Reification Rules</a></li><li class="tocline"><a href="#section-List-Expand" class="tocxref"><span class="secno">7.4 </span>List Expansion Rules</a></li></ul></li><li class="tocline"><a href="#section-Serialising" class="tocxref"><span class="secno">8. </span>Serializing an RDF Graph to RDF/XML</a></li><li class="tocline"><a href="#section-rdf-in-SVG" class="tocxref"><span class="secno">9. </span>Using RDF/XML with SVG</a></li><li class="tocline"><a href="#section-Acknowledgments" class="tocxref"><span class="secno">A. </span>Acknowledgments</a></li><li class="tocline"><a href="#changes-rdf11" class="tocxref"><span class="secno">B. </span>Changes to 2004 Recommendation</a></li><li class="tocline"><a href="#section-Schemas" class="tocxref"><span class="secno">C. </span>Syntax Schemas</a><ul class="toc"><li class="tocline"><a href="#section-RELAXNG-Schema" class="tocxref"><span class="secno">C.1 </span>RELAX NG Compact Schema</a></li></ul></li><li class="tocline"><a href="#references" class="tocxref"><span class="secno">D. </span>References</a><ul class="toc"><li class="tocline"><a href="#normative-references" class="tocxref"><span class="secno">D.1 </span>Normative references</a></li><li class="tocline"><a href="#informative-references" class="tocxref"><span class="secno">D.2 </span>Informative references</a></li></ul></li></ul></section>
@@ -376,37 +376,37 @@
<h2 aria-level="1" role="heading" id="h2_section-Introduction"><span class="secno">1. </span>Introduction</h2>
<p>This document defines the
- XML [<cite><a class="bibref" href="#bib-XML10">XML10</a></cite>] syntax for <abbr title="Resource Description Framework">RDF</abbr> graphs. </p>
+ XML [<cite><a class="bibref" href="#bib-XML10">XML10</a></cite>] syntax for RDF graphs. </p>
- <p>This document revises the original <abbr title="Resource Description Framework">RDF</abbr>/XML grammar [<cite><a class="bibref" href="#bib-RDFMS">RDFMS</a></cite>]
+ <p>This document revises the original RDF/XML grammar [<cite><a class="bibref" href="#bib-RDFMS">RDFMS</a></cite>]
in terms of XML Information Set [<cite><a class="bibref" href="#bib-XML-INFOSET">XML-INFOSET</a></cite>] information items which moves
away from the rather low-level details of XML, such as particular
forms of empty elements. This allows the grammar to be more
- precisely recorded and the mapping from the XML syntax to the <abbr title="Resource Description Framework">RDF</abbr>
- Graph more clearly shown. The mapping to the <abbr title="Resource Description Framework">RDF</abbr> graph is done by
+ precisely recorded and the mapping from the XML syntax to the RDF
+ Graph more clearly shown. The mapping to the RDF graph is done by
emitting statements in the N-Triples [<cite><a class="bibref" href="#bib-N-TRIPLES">N-TRIPLES</a></cite>] format. </p>
- <p>This document is part of the suite of <abbr title="Resource Description Framework">RDF</abbr> 1.1
+ <p>This document is part of the suite of RDF 1.1
documents. Other documents in this suite are: </p>
<ul>
- <li>A document describing the basic concepts underlying <abbr title="Resource Description Framework">RDF</abbr>, as
- well as abstract syntax ("<abbr title="Resource Description Framework">RDF</abbr> Concepts and Abstract Syntax")
+ <li>A document describing the basic concepts underlying RDF, as
+ well as abstract syntax ("RDF Concepts and Abstract Syntax")
[<cite><a class="bibref" href="#bib-RDF11-CONCEPTS">RDF11-CONCEPTS</a></cite>]</li>
<li>A document describing the formal model-theoretic semantics
- of <abbr title="Resource Description Framework">RDF</abbr> ("<abbr title="Resource Description Framework">RDF</abbr> Semantics") [<cite><a class="bibref" href="#bib-RDF11-MT">RDF11-MT</a></cite>]</li>
- <li>Specifications of concrete syntaxes for <abbr title="Resource Description Framework">RDF</abbr>:
+ of RDF ("RDF Semantics") [<cite><a class="bibref" href="#bib-RDF11-MT">RDF11-MT</a></cite>]</li>
+ <li>Specifications of concrete syntaxes for RDF:
<ul>
<li>Turtle [<cite><a class="bibref" href="#bib-TURTLE">TURTLE</a></cite>] and TriG [<cite><a class="bibref" href="#bib-TRIG">TRIG</a></cite>]</li>
<li>JSON-LD [<cite><a class="bibref" href="#bib-JSON-LD">JSON-LD</a></cite>] (JSON based)</li>
<li>RDFa [<cite><a class="bibref" href="#bib-RDFA-PRIMER">RDFA-PRIMER</a></cite>] (for HTML embedding)</li>
<li>N-Triples and N-Quads (line-based exchange formats)</li>
</ul></li>
- <li>A document describing <abbr title="Resource Description Framework">RDF</abbr> Schema [<cite><a class="bibref" href="#bib-RDF-SCHEMA">RDF-SCHEMA</a></cite>], which
- provides a data-modeling vocabulary for <abbr title="Resource Description Framework">RDF</abbr> data. </li>
+ <li>A document describing RDF Schema [<cite><a class="bibref" href="#bib-RDF11-SCHEMA">RDF11-SCHEMA</a></cite>], which
+ provides a data-modeling vocabulary for RDF data. </li>
</ul>
- <p>For a longer introduction to the <abbr title="Resource Description Framework">RDF</abbr>/XML syntax with a historical
- perspective, see "<abbr title="Resource Description Framework">RDF</abbr>: Understanding the Striped <abbr title="Resource Description Framework">RDF</abbr>/XML
+ <p>For a longer introduction to the RDF/XML syntax with a historical
+ perspective, see "RDF: Understanding the Striped RDF/XML
Syntax" [<cite><a class="bibref" href="#bib-STRIPEDRDF">STRIPEDRDF</a></cite>].</p>
</section>
@@ -420,13 +420,13 @@
<!--OddPage-->
-<h2 aria-level="1" role="heading" id="h2_section-Syntax"><span class="secno">2. </span>An XML Syntax for <abbr title="Resource Description Framework">RDF</abbr></h2>
- <p>This section introduces the <abbr title="Resource Description Framework">RDF</abbr>/XML syntax, describes how it
- encodes <abbr title="Resource Description Framework">RDF</abbr> graphs and explains this with examples. If there is any
+<h2 aria-level="1" role="heading" id="h2_section-Syntax"><span class="secno">2. </span>An XML Syntax for RDF</h2>
+ <p>This section introduces the RDF/XML syntax, describes how it
+ encodes RDF graphs and explains this with examples. If there is any
conflict between this informal description and the formal description
of the syntax and grammar in sections
<a href="#section-Data-Model">6 Syntax Data Model</a> and
- <a href="#section-Infoset-Grammar">7 <abbr title="Resource Description Framework">RDF</abbr>/XML Grammar</a>, the
+ <a href="#section-Infoset-Grammar">7 RDF/XML Grammar</a>, the
latter two sections take precedence.
</p>
@@ -436,15 +436,15 @@
<section id="section-Syntax-intro" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter">
<h3 aria-level="2" role="heading" id="h3_section-Syntax-intro"><span class="secno">2.1 </span>Introduction</h3>
- <p>The <abbr title="Resource Description Framework">RDF</abbr> Concepts and Abstract Syntax document [<cite><a class="bibref" href="#bib-RDF11-CONCEPTS">RDF11-CONCEPTS</a></cite>]
- defines the <abbr title="Resource Description Framework">RDF</abbr> Graph data model and the
- <abbr title="Resource Description Framework">RDF</abbr> Graph abstract syntax.
- Along with the <abbr title="Resource Description Framework">RDF</abbr> Semantics [<cite><a class="bibref" href="#bib-RDF11-MT">RDF11-MT</a></cite>]
+ <p>The RDF Concepts and Abstract Syntax document [<cite><a class="bibref" href="#bib-RDF11-CONCEPTS">RDF11-CONCEPTS</a></cite>]
+ defines the RDF Graph data model and the
+ RDF Graph abstract syntax.
+ Along with the RDF Semantics [<cite><a class="bibref" href="#bib-RDF11-MT">RDF11-MT</a></cite>]
this provides an abstract syntax with a formal semantics for it.
- The <abbr title="Resource Description Framework">RDF</abbr> graph has <em>nodes</em>
+ The RDF graph has <em>nodes</em>
and labeled directed <em>arcs</em>
that link pairs of nodes and this is represented as a set of
- <abbr title="Resource Description Framework">RDF</abbr> triples
+ RDF triples
where each triple contains a
<em>subject node</em>, <em>predicate</em> and <em>object node</em>.
Nodes are IRIs, literals, or blank nodes.
@@ -459,7 +459,7 @@
<p>In order to encode the graph in XML, the nodes and predicates have to be
represented in XML terms — element names, attribute names, element contents
and attribute values.
- <abbr title="Resource Description Framework">RDF</abbr>/XML uses XML
+ RDF/XML uses XML
<a href="http://www.w3.org/TR/1999/REC-xml-names-19990114/#NT-QName">QNames</a>
as defined in Namespaces in XML [<cite><a class="bibref" href="#bib-XML-NAMES">XML-NAMES</a></cite>] to represent IRIs.
All QNames have a <a href="http://www.w3.org/TR/1999/REC-xml-names-19990114/#dt-NSName">namespace
@@ -480,24 +480,24 @@
of all predicates and some nodes.
IRIs identifying
subject and object nodes can also be stored as XML attribute values.
- <abbr title="Resource Description Framework">RDF</abbr> literals
+ RDF literals
which can only be object nodes,
become either XML element text content or XML attribute values.</p>
<p>A graph can be considered a collection of paths of the form node,
predicate arc, node, predicate arc, node, predicate arc, ... node
- which cover the entire graph. In <abbr title="Resource Description Framework">RDF</abbr>/XML these turn into sequences of
+ which cover the entire graph. In RDF/XML these turn into sequences of
elements inside elements which alternate between elements for nodes
and predicate arcs. This has been called a series of node/arc
stripes. The node at the start of the sequence turns into the
outermost element, the next predicate arc turns into a child element,
- and so on. The stripes generally start at the top of an <abbr title="Resource Description Framework">RDF</abbr>/XML
+ and so on. The stripes generally start at the top of an RDF/XML
document and always begin with nodes.
</p>
- <p>Several <abbr title="Resource Description Framework">RDF</abbr>/XML examples are given in the following sections
- building up to complete <abbr title="Resource Description Framework">RDF</abbr>/XML documents. <a href="#example7">Example 7</a>
- is the first complete <abbr title="Resource Description Framework">RDF</abbr>/XML document.</p>
+ <p>Several RDF/XML examples are given in the following sections
+ building up to complete RDF/XML documents. <a href="#example7">Example 7</a>
+ is the first complete RDF/XML document.</p>
</section>
@@ -513,7 +513,7 @@
<figcaption>Fig. <span class="figno">1</span> <span class="fig-title">Graph for RDF/XML Example (SVG version)</span></figcaption>
</figure>
- <p>An <abbr title="Resource Description Framework">RDF</abbr> graph is given in <a href="#figure1" class="fig-ref">Figure 1</a>
+ <p>An RDF graph is given in <a href="#figure1" class="fig-ref">Figure 1</a>
where the nodes are represented as ovals and contain their
IRIs where they have them, all the predicate arcs are labeled with
IRIs and string literals nodes have been written in rectangles.</p>
@@ -525,7 +525,7 @@
<figure id="figure2">
<img alt="One Path Through the Graph" src="figure2.png" />
- <figcaption>Fig. <span class="figno">2</span> <span class="fig-title">One Path Through the Graph (SVG version)</span></figcaption>
+ <figcaption>Fig. <span class="figno">2</span> <span class="fig-title">One Path Through the Graph (SVG version)</span></figcaption>
</figure>
<p>The left hand side of the <a href="#figure2" class="fig-ref">Figure 2</a>
@@ -541,7 +541,7 @@
<li>Node with IRI <code>http://purl.org/net/dajobe/</code></li>
</ol>
- <p>In <abbr title="Resource Description Framework">RDF</abbr>/XML, the sequence of 5 nodes and predicate arcs on
+ <p>In RDF/XML, the sequence of 5 nodes and predicate arcs on
the left hand side of <a href="#figure2" class="fig-ref">Figure 2</a> corresponds to
the usage of five XML elements of two types, for the graph nodes and
predicate arcs. These are conventionally called <em>node elements</em> and
@@ -571,7 +571,7 @@
IRIs
(and others that are not) and this can be added
- to the <abbr title="Resource Description Framework">RDF</abbr>/XML using the <code>rdf:about</code> attribute on node
+ to the RDF/XML using the <code>rdf:about</code> attribute on node
elements to give the result in <a href="#example2">Example 2</a>:</p>
<div class="example"><div class="example-title"><span>Example 2</span></div><pre id="example2" class="example"><strong>Node Elements with IRIs added</strong>
@@ -588,7 +588,7 @@
</rdf:Description></pre></div>
<p>Adding the other two paths through the <a href="#figure1" class="fig-ref">Figure 1</a>
- graph to the <abbr title="Resource Description Framework">RDF</abbr>/XML in
+ graph to the RDF/XML in
<a href="#example2">Example 2</a>
gives the result in <a href="#example3">Example 3</a>
(this example fails to show that the blank node is
@@ -617,7 +617,7 @@
</rdf:Description>
<rdf:Description rdf:about="http://www.w3.org/TR/rdf-syntax-grammar">
- <dc:title>RDF/XML Syntax Specification (Revised)</dc:title>
+ <dc:title>RDF 1.1 XML Syntax</dc:title>
</rdf:Description></pre></div>
</section>
@@ -630,7 +630,7 @@
<p>There are several abbreviations that can be used to make common
uses easier to write down. In particular, it is common that a
- subject node in the <abbr title="Resource Description Framework">RDF</abbr> graph has multiple outgoing predicate arcs. <abbr title="Resource Description Framework">RDF</abbr>/XML
+ subject node in the RDF graph has multiple outgoing predicate arcs. RDF/XML
provides an abbreviation for the corresponding syntax when a node
element about a resource has multiple property elements. This can be
abbreviated by using multiple child property elements inside the node
@@ -659,7 +659,7 @@
<ex:fullName>Dave Beckett</ex:fullName>
</rdf:Description>
</ex:editor>
- <dc:title>RDF/XML Syntax Specification (Revised)</dc:title>
+ <dc:title>RDF 1.1 XML Syntax</dc:title>
</rdf:Description></pre></div>
</section>
@@ -670,8 +670,8 @@
<section id="section-Syntax-empty-property-elements" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter">
<h3 aria-level="2" role="heading" id="h3_section-Syntax-empty-property-elements"><span class="secno">2.4 </span>Empty Property Elements</h3>
- <p>When a predicate arc in an <abbr title="Resource Description Framework">RDF</abbr> graph points to an object node which has no
- further predicate arcs, which appears in <abbr title="Resource Description Framework">RDF</abbr>/XML as an empty node element
+ <p>When a predicate arc in an RDF graph points to an object node which has no
+ further predicate arcs, which appears in RDF/XML as an empty node element
<code><rdf:Description rdf:about="..."></code>
<code></rdf:Description></code>
(or <code><rdf:Description rdf:about="..." /></code>)
@@ -696,7 +696,7 @@
<ex:fullName>Dave Beckett</ex:fullName>
</rdf:Description>
</ex:editor>
- <dc:title>RDF/XML Syntax Specification (Revised)</dc:title>
+ <dc:title>RDF 1.1 XML Syntax</dc:title>
</rdf:Description></pre></div>
</section>
@@ -733,7 +733,7 @@
<div class="example"><div class="example-title"><span>Example 6</span></div><pre id="example6" class="example"><strong>Replacing property elements with string literal content into property attributes</strong>
<rdf:Description rdf:about="http://www.w3.org/TR/rdf-syntax-grammar"
- dc:title="RDF/XML Syntax Specification (Revised)">
+ dc:title="RDF 1.1 XML Syntax">
<ex:editor>
<rdf:Description ex:fullName="Dave Beckett">
<ex:homePage rdf:resource="http://purl.org/net/dajobe/"/>
@@ -749,24 +749,24 @@
<section id="section-Syntax-complete-document" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter">
<h3 aria-level="2" role="heading" id="h3_section-Syntax-complete-document"><span class="secno">2.6 </span>Completing the Document: Document Element and XML Declaration</h3>
- <p>To create a complete <abbr title="Resource Description Framework">RDF</abbr>/XML document, the serialization of the
- graph into XML is usually contained inside an <code>rdf:<abbr title="Resource Description Framework">RDF</abbr></code>
+ <p>To create a complete RDF/XML document, the serialization of the
+ graph into XML is usually contained inside an <code>rdf:RDF</code>
XML element which becomes the top-level XML document element.
- Conventionally the <code>rdf:<abbr title="Resource Description Framework">RDF</abbr></code> element is also used to
+ Conventionally the <code>rdf:RDF</code> element is also used to
declare the XML namespaces that are used, although that is not
required. When there is only one top-level node element inside
- <code>rdf:<abbr title="Resource Description Framework">RDF</abbr></code>, the <code>rdf:<abbr title="Resource Description Framework">RDF</abbr></code> can be omitted
+ <code>rdf:RDF</code>, the <code>rdf:RDF</code> can be omitted
although any XML namespaces must still be declared.</p>
<p>The XML specification also permits an XML declaration at
the top of the document with the XML version and possibly the XML
content encoding. This is optional but recommended.</p>
- <p>Completing the <abbr title="Resource Description Framework">RDF</abbr>/XML could be done for any of the correct
+ <p>Completing the RDF/XML could be done for any of the correct
complete graph examples from
<a href="#example4">Example 4</a> onwards but taking the smallest
<a href="#example6">Example 6</a> and adding the final components,
- gives a complete <abbr title="Resource Description Framework">RDF</abbr>/XML representation of the original
+ gives a complete RDF/XML representation of the original
<a href="#figure1" class="fig-ref">Figure 1</a> graph
in <a href="#example7">Example 7</a>:</p>
@@ -779,7 +779,7 @@
xmlns:ex="http://example.org/stuff/1.0/">
<rdf:Description rdf:about="http://www.w3.org/TR/rdf-syntax-grammar"
- dc:title="RDF/XML Syntax Specification (Revised)">
+ dc:title="RDF1.1 XML Syntax">
<ex:editor>
<rdf:Description ex:fullName="Dave Beckett">
<ex:homePage rdf:resource="http://purl.org/net/dajobe/" />
@@ -789,9 +789,9 @@
</rdf:RDF></pre></div>
- <p>It is possible to omit <code>rdf:<abbr title="Resource Description Framework">RDF</abbr></code> in
+ <p>It is possible to omit <code>rdf:RDF</code> in
<a href="#example7">Example 7</a> above since there is only one
- <code>rdf:Description</code> inside <code>rdf:<abbr title="Resource Description Framework">RDF</abbr></code> but this
+ <code>rdf:Description</code> inside <code>rdf:RDF</code> but this
is not shown here.</p>
</section>
@@ -801,7 +801,7 @@
<section id="section-Syntax-languages" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter">
<h3 aria-level="2" role="heading" id="h3_section-Syntax-languages"><span class="secno">2.7 </span>Languages: <code>xml:lang</code></h3>
- <p><abbr title="Resource Description Framework">RDF</abbr>/XML permits the use of the <code>xml:lang</code> attribute as defined by
+ <p>RDF/XML permits the use of the <code>xml:lang</code> attribute as defined by
<a href="http://www.w3.org/TR/REC-xml#sec-lang-tag">2.12 Language Identification</a>
of XML 1.0 [<cite><a class="bibref" href="#bib-XML10">XML10</a></cite>]
to allow the identification of content language.
@@ -815,7 +815,7 @@
property attribute values. The <code>xml:lang=""</code> form
indicates the absence of a language identifier.</p>
- <p>Some examples of marking content languages for <abbr title="Resource Description Framework">RDF</abbr> properties are shown in
+ <p>Some examples of marking content languages for RDF properties are shown in
<a href="#example8">Example 8</a>:</p>
<div class="example"><div class="example-title"><span>Example 8</span></div><pre id="example8" class="example"><strong>Complete example of <code>xml:lang</code>
@@ -826,9 +826,9 @@
xmlns:dc="http://purl.org/dc/elements/1.1/">
<rdf:Description rdf:about="http://www.w3.org/TR/rdf-syntax-grammar">
- <dc:title>RDF/XML Syntax Specification (Revised)</dc:title>
- <dc:title xml:lang="en">RDF/XML Syntax Specification (Revised)</dc:title>
- <dc:title xml:lang="en-US">RDF/XML Syntax Specification (Revised)</dc:title>
+ <dc:title>RDF 1.1 XML Syntax</dc:title>
+ <dc:title xml:lang="en">RDF 1.1 XML Syntax</dc:title>
+ <dc:title xml:lang="en-US">RDF 1.1 XML Syntax</dc:title>
</rdf:Description>
<rdf:Description rdf:about="http://example.org/buecher/baum" xml:lang="de">
@@ -847,9 +847,9 @@
<section id="section-Syntax-XML-literals" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter">
<h3 aria-level="2" role="heading" id="h3_section-Syntax-XML-literals"><span class="secno">2.8 </span>XML Literals: <code>rdf:parseType="Literal"</code></h3>
- <p><abbr title="Resource Description Framework">RDF</abbr> allows XML literals [RDF11-CONCEPTS]
+ <p>RDF allows XML literals [RDF11-CONCEPTS]
to be given as the object node of a predicate.
- These are written in <abbr title="Resource Description Framework">RDF</abbr>/XML as content of a property element (not
+ These are written in RDF/XML as content of a property element (not
a property attribute) and indicated using the
<code>rdf:parseType="Literal"</code> attribute on the containing
property element.
@@ -857,12 +857,11 @@
<p>An example of writing an XML literal is given in
<a href="#example9">Example 9</a> where
- there is a single <abbr title="Resource Description Framework">RDF</abbr> triple with the subject node
+ there is a single RDF triple with the subject node
IRI
<code>http://example.org/item01</code>, the predicate
IRI
<code>http://example.org/stuff/1.0/prop</code> (from
-
<code>ex:prop</code>) and the object node with XML literal
content beginning <code>a:Box</code>.
</p>
@@ -874,11 +873,12 @@
<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
xmlns:ex="http://example.org/stuff/1.0/">
- <rdf:Description rdf:about="http://example.org/item01">
- <ex:prop rdf:parseType="Literal"
- xmlns:a="http://example.org/a#"><a:Box required="true">
- <a:widget size="10" />
- <a:grommit id="23" /></a:Box>
+ <rdf:Description rdf:about="http://example.org/item01">
+ <ex:prop rdf:parseType="Literal" xmlns:a="http://example.org/a#">
+ <a:Box required="true">
+ <a:widget size="10" />
+ <a:grommit id="23" />
+ </a:Box>
</ex:prop>
</rdf:Description>
@@ -892,10 +892,10 @@
<section id="section-Syntax-datatyped-literals" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter">
<h3 aria-level="2" role="heading" id="h3_section-Syntax-datatyped-literals"><span class="secno">2.9 </span>Typed Literals: <code>rdf:datatype</code></h3>
- <p><abbr title="Resource Description Framework">RDF</abbr> allows typed literals
+ <p>RDF allows typed literals
to be given as the object node of a predicate. Typed literals consist of a literal
string and a datatype
- IRI. These are written in <abbr title="Resource Description Framework">RDF</abbr>/XML using
+ IRI. These are written in RDF/XML using
the same syntax for literal string nodes in the property element form
(not property attribute) but with an additional
<code>rdf:datatype="</code><em>datatypeURI</em><code>"</code>
@@ -903,10 +903,10 @@
IRI can be used in the attribute.
</p>
- <p>An example of an <abbr title="Resource Description Framework">RDF</abbr> typed
+ <p>An example of an RDF typed
literal
is given in <a href="#example10">Example 10</a> where
- there is a single <abbr title="Resource Description Framework">RDF</abbr> triple with the subject node
+ there is a single RDF triple with the subject node
IRI
<code>http://example.org/item01</code>, the predicate
IRI
@@ -939,13 +939,13 @@
<section id="section-Syntax-blank-nodes" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter">
<h3 aria-level="2" role="heading" id="h3_section-Syntax-blank-nodes"><span class="secno">2.10 </span>Identifying Blank Nodes: <code>rdf:nodeID</code></h3>
- <p>Blank nodes in the <abbr title="Resource Description Framework">RDF</abbr> graph are distinct but have no
+ <p>Blank nodes in the RDF graph are distinct but have no
IRI identifier.
It is sometimes required that the same graph blank node is referred to in the
- <abbr title="Resource Description Framework">RDF</abbr>/XML in multiple places, such as at the subject and object
- of several <abbr title="Resource Description Framework">RDF</abbr> triples. In this case, a blank node identifier
+ RDF/XML in multiple places, such as at the subject and object
+ of several RDF triples. In this case, a blank node identifier
can be given to the blank node for identifying it
- in the document. Blank node identifiers in <abbr title="Resource Description Framework">RDF</abbr>/XML are scoped to the
+ in the document. Blank node identifiers in RDF/XML are scoped to the
containing XML Information Set
<a href="http://www.w3.org/TR/xml-infoset/#infoitem.document">document information item</a>.
A blank node identifier is used
@@ -954,7 +954,7 @@
or on a property element to replace
<code>rdf:resource="</code><em>IRI</em><code>"</code>
- with <code>rdf:nodeID="</code><em><a href="http://www.w3.org/TR/2004/REC-rdf-concepts-20040210/#dfn-blank-node-id">blank node identifier</a></em><code>"</code>
+ with <code>rdf:nodeID="</code><em>blank node identifier</em><code>"</code>
in both cases.</p>
<p>Taking <a href="#example7">Example 7</a> and explicitly giving
@@ -973,7 +973,7 @@
xmlns:ex="http://example.org/stuff/1.0/">
<rdf:Description rdf:about="http://www.w3.org/TR/rdf-syntax-grammar"
- dc:title="RDF/XML Syntax Specification (Revised)">
+ dc:title="RDF 1.1 XML Syntax">
<ex:editor rdf:nodeID="abc"/>
</rdf:Description>
@@ -991,7 +991,7 @@
<section id="section-Syntax-parsetype-resource" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter">
<h3 aria-level="2" role="heading" id="h3_section-Syntax-parsetype-resource"><span class="secno">2.11 </span>Omitting Blank Nodes: <code>rdf:parseType="Resource"</code></h3>
- <p>Blank nodes (not IRI nodes) in <abbr title="Resource Description Framework">RDF</abbr> graphs can be written
+ <p>Blank nodes (not IRI nodes) in RDF graphs can be written
in a form that allows the
<code><rdf:Description></code>
<code></rdf:Description></code> pair to be omitted.
@@ -1018,7 +1018,7 @@
xmlns:dc="http://purl.org/dc/elements/1.1/"
xmlns:ex="http://example.org/stuff/1.0/">
<rdf:Description rdf:about="http://www.w3.org/TR/rdf-syntax-grammar"
- dc:title="RDF/XML Syntax Specification (Revised)">
+ dc:title="RDF 1.1 XML Syntax">
<ex:editor rdf:parseType="Resource">
<ex:fullName>Dave Beckett</ex:fullName>
<ex:homePage rdf:resource="http://purl.org/net/dajobe/"/>
@@ -1068,7 +1068,7 @@
xmlns:ex="http://example.org/stuff/1.0/">
<rdf:Description rdf:about="http://www.w3.org/TR/rdf-syntax-grammar"
- dc:title="RDF/XML Syntax Specification (Revised)">
+ dc:title="RDF 1.1 XML Syntax">
<ex:editor ex:fullName="Dave Beckett" />
<!-- Note the ex:homePage property has been ignored for this example -->
</rdf:Description>
@@ -1083,10 +1083,10 @@
<section id="section-Syntax-typed-nodes" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter">
<h3 aria-level="2" role="heading" id="h3_section-Syntax-typed-nodes"><span class="secno">2.13 </span>Typed Node Elements</h3>
- <p>It is common for <abbr title="Resource Description Framework">RDF</abbr> graphs to have <code>rdf:type</code> predicates
+ <p>It is common for RDF graphs to have <code>rdf:type</code> predicates
from subject nodes. These are conventionally called <em>typed
nodes</em> in the graph, or <em>typed node elements</em> in the
- <abbr title="Resource Description Framework">RDF</abbr>/XML. <abbr title="Resource Description Framework">RDF</abbr>/XML allows this triple to be expressed more concisely.
+ RDF/XML. RDF/XML allows this triple to be expressed more concisely.
by replacing the <code>rdf:Description</code> node element name with
the namespaced-element corresponding to the
@@ -1096,14 +1096,14 @@
property elements or property attributes.
</p>
- <p>The typed node elements are commonly used in <abbr title="Resource Description Framework">RDF</abbr>/XML with the built-in
- classes in the <a href="#section-Namespace"><abbr title="Resource Description Framework">RDF</abbr> vocabulary</a>:
+ <p>The typed node elements are commonly used in RDF/XML with the built-in
+ classes in the <a href="#section-Namespace">RDF vocabulary</a>:
<code>rdf:Seq</code>, <code>rdf:Bag</code>, <code>rdf:Alt</code>,
<code>rdf:Statement</code>, <code>rdf:Property</code> and
<code>rdf:List</code>.</p>
- <p>For example, the <abbr title="Resource Description Framework">RDF</abbr>/XML in <a href="#example14">Example 14</a>
+ <p>For example, the RDF/XML in <a href="#example14">Example 14</a>
could be written as shown in <a href="#example15">Example 15</a>.</p>
<div class="example"><div class="example-title"><span>Example 14</span></div><pre id="example14" class="example"><strong>Complete example with <code>rdf:type</code>
@@ -1142,11 +1142,11 @@
<section id="section-Syntax-ID-xml-base" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter">
<h3 aria-level="2" role="heading" id="h3_section-Syntax-ID-xml-base"><span class="secno">2.14 </span>Abbreviating URIs: <code>rdf:ID</code> and <code>xml:base</code></h3>
- <p><abbr title="Resource Description Framework">RDF</abbr>/XML allows further abbreviating IRIs in XML attributes in two
+ <p>RDF/XML allows further abbreviating IRIs in XML attributes in two
ways. The XML Infoset provides a base URI attribute <code>xml:base</code>
that sets the base URI for resolving relative IRIs, otherwise
the base URI is that of the document. The base URI applies to
- all <abbr title="Resource Description Framework">RDF</abbr>/XML attributes that deal with IRIs which are <code>rdf:about</code>,
+ all RDF/XML attributes that deal with IRIs which are <code>rdf:about</code>,
<code>rdf:resource</code>, <code>rdf:ID</code>
and <code>rdf:datatype</code>.</p>
@@ -1162,7 +1162,7 @@
related terms relative to the same IRI.</p>
<p>Both forms require a base URI to be known, either from an in-scope
- <code>xml:base</code> or from the URI of the <abbr title="Resource Description Framework">RDF</abbr>/XML document.</p>
+ <code>xml:base</code> or from the URI of the RDF/XML document.</p>
<p><a href="#example16">Example 16</a> shows abbreviating the node
IRI of <code>http://example.org/here/#snack</code> using an
@@ -1197,7 +1197,7 @@
<section id="section-Syntax-list-elements" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter">
<h3 aria-level="2" role="heading" id="h3_section-Syntax-list-elements"><span class="secno">2.15 </span>Container Membership Property Elements: <code>rdf:li</code> and <code>rdf:_</code><em>n</em></h3>
- <p><abbr title="Resource Description Framework">RDF</abbr> has a set of container membership properties
+ <p>RDF has a set of container membership properties
and corresponding property elements that are mostly used with
instances of the
<code>rdf:Seq</code>, <code>rdf:Bag</code> and <code>rdf:Alt</code>
@@ -1212,7 +1212,7 @@
The mapping to the container membership properties is
always done in the order that the <code>rdf:li</code> special
property elements appear in XML — the document order is significant.
- The equivalent <abbr title="Resource Description Framework">RDF</abbr>/XML to <a href="#example17">Example 17</a> written
+ The equivalent RDF/XML to <a href="#example17">Example 17</a> written
in this form is shown in <a href="#example18">Example 18</a>.
</p>
@@ -1252,7 +1252,7 @@
<section id="section-Syntax-parsetype-Collection" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter">
<h3 aria-level="2" role="heading" id="h3_section-Syntax-parsetype-Collection"><span class="secno">2.16 </span>Collections: <code>rdf:parseType="Collection"</code></h3>
- <p><abbr title="Resource Description Framework">RDF</abbr>/XML allows an <code>rdf:parseType="Collection"</code>
+ <p>RDF/XML allows an <code>rdf:parseType="Collection"</code>
attribute on a property element to let it contain multiple node
elements. These contained node elements give the set of subject
@@ -1308,7 +1308,7 @@
<code>rdf:ID="triple"</code>, that would be equivalent to the IRI
formed from relative IRI <code>#triple</code> against the base URI.
Each (<code>rdf:ID</code> attribute value, base URI)
- pair has to be unique in an <abbr title="Resource Description Framework">RDF</abbr>/XML document,
+ pair has to be unique in an RDF/XML document,
see <a href="#constraint-id">constraint-id</a>.
</p>
@@ -1365,9 +1365,9 @@
<section id="section-MIME-Type" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter">
<!--OddPage-->
-<h2 aria-level="1" role="heading" id="h2_section-MIME-Type"><span class="secno">4. </span><abbr title="Resource Description Framework">RDF</abbr> MIME Type, File Extension and Macintosh File Type</h2>
-
- <p>The Internet media type / MIME type for <abbr title="Resource Description Framework">RDF</abbr>/XML is
+<h2 aria-level="1" role="heading" id="h2_section-MIME-Type"><span class="secno">4. </span>RDF MIME Type, File Extension and Macintosh File Type</h2>
+
+ <p>The Internet media type / MIME type for RDF/XML is
<code>application/rdf+xml</code> —
RFC 3023 [<cite><a class="bibref" href="#bib-RFC3023">RFC3023</a></cite>], section 8.18.
</p>
@@ -1377,10 +1377,10 @@
IANA MIME Media Types [<cite><a class="bibref" href="#bib-IANA-MEDIA-TYPES">IANA-MEDIA-TYPES</a></cite>]
</p></div>
- <p>It is recommended that <abbr title="Resource Description Framework">RDF</abbr>/XML files have the extension
+ <p>It is recommended that RDF/XML files have the extension
<code>".rdf"</code> (all lowercase) on all platforms.</p>
- <p>It is recommended that <abbr title="Resource Description Framework">RDF</abbr>/XML files stored on Macintosh HFS file
+ <p>It is recommended that RDF/XML files stored on Macintosh HFS file
systems be given a file type of <code>"rdf "</code>
(all lowercase, with a space character as the fourth letter).</p>
</section>
@@ -1400,44 +1400,20 @@
<section id="section-Namespace" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter">
- <h3 aria-level="2" role="heading" id="h3_section-Namespace"><span class="secno">5.1 </span>The <abbr title="Resource Description Framework">RDF</abbr> Namespace and Vocabulary</h3>
-
- <div class="note"><div class="note-title" aria-level="3" role="heading" id="h_note_2"><span>Note</span></div><p class=""><strong>(Informative): </strong>
- The names <code>aboutEach</code> and <code>aboutEachPrefix</code> were removed
- from the language and the <abbr title="Resource Description Framework">RDF</abbr> vocabulary by the <abbr title="Resource Description Framework">RDF</abbr> Core Working Group.
- See the resolution of issues
- <a href="http://www.w3.org/2000/03/rdf-tracking/#rdfms-abouteach">rdfms-abouteach</a> and
- <a href="http://www.w3.org/2000/03/rdf-tracking/#rdfms-abouteachprefix">rdfms-abouteachprefix</a>
- for further information.
- </p></div>
-
- <div class="note"><div class="note-title" aria-level="3" role="heading" id="h_note_3"><span>Note</span></div><p class=""><strong>(Informative): </strong>
- The names <code>List</code>, <code>first</code>,
- <code>rest</code> and <code>nil</code> were added for issue
-
- <a href="http://www.w3.org/2000/03/rdf-tracking/#rdfms-seq-representation">rdfms-seq-representation</a>.
- The names <code>XMLLiteral</code> and <code>datatype</code> were added
- to support <abbr title="Resource Description Framework">RDF</abbr> datatyping.
- The name <code>nodeID</code> was added
- for issue
- <a href="http://www.w3.org/2000/03/rdf-tracking/#rdfms-syntax-incomplete">rdfms-syntax-incomplete</a>.
- See the
- <a href="http://www.w3.org/2000/03/rdf-tracking/"><abbr title="Resource Description Framework">RDF</abbr> Core Issues List</a>
- for further information.
- </p></div>
-
- <p>The <dfn id="rdf-ns-uri"><abbr title="Resource Description Framework">RDF</abbr> namespace IRI</dfn> (or namespace name) is
+ <h3 aria-level="2" role="heading" id="h3_section-Namespace"><span class="secno">5.1 </span>The RDF Namespace and Vocabulary</h3>
+
+ <p>The <dfn id="rdf-ns-uri">RDF namespace IRI</dfn> (or namespace name) is
<code>http://www.w3.org/1999/02/22-rdf-syntax-ns#</code>
and is typically used in XML with the prefix <code>rdf</code>
although other prefix strings may be used.
- The <dfn id="rdf-vocabulary"><abbr title="Resource Description Framework">RDF</abbr> Vocabulary</dfn>
+ The <dfn id="rdf-vocabulary">RDF Vocabulary</dfn>
is identified by this namespace name and consists of the following names only:</p>
<dl>
<dt>Syntax names — not concepts</dt>
<dd>
<p>
- <code><abbr title="Resource Description Framework">RDF</abbr> Description ID about parseType resource li nodeID datatype</code>
+ <code>RDF Description ID about parseType resource li nodeID datatype</code>
</p>
</dd>
@@ -1468,16 +1444,16 @@
<p>Any other names are not defined and <em class="rfc2119" title="SHOULD">SHOULD</em> generate a warning when
encountered, but should otherwise behave normally.</p>
- <p>Within <abbr title="Resource Description Framework">RDF</abbr>/XML documents it is not permitted to use XML namespaces
+ <p>Within RDF/XML documents it is not permitted to use XML namespaces
whose namespace name is the
- <a class="termref" href="#rdf-ns-uri"><span class="arrow">·</span><abbr title="Resource Description Framework">RDF</abbr> namespace IRI<span class="arrow">·</span></a>
+ <a class="termref" href="#rdf-ns-uri"><span class="arrow">·</span>RDF namespace IRI<span class="arrow">·</span></a>
concatenated with additional characters.</p>
<p>Throughout this document the terminology <code>rdf:</code><em>name</em>
- will be used to indicate <em>name</em> is from the <abbr title="Resource Description Framework">RDF</abbr> vocabulary
+ will be used to indicate <em>name</em> is from the RDF vocabulary
and it has a IRI of the concatenation of the
- <a class="termref" href="#rdf-ns-uri"><span class="arrow">·</span><abbr title="Resource Description Framework">RDF</abbr> namespace IRI<span class="arrow">·</span></a> and <em>name</em>.
+ <a class="termref" href="#rdf-ns-uri"><span class="arrow">·</span>RDF namespace IRI<span class="arrow">·</span></a> and <em>name</em>.
For example, <code>rdf:type</code> has the IRI
<code>http://www.w3.org/1999/02/22-rdf-syntax-ns#type</code></p>
</section>
@@ -1489,8 +1465,8 @@
<section id="section-Identifiers" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter">
<h3 aria-level="2" role="heading" id="h3_section-Identifiers"><span class="secno">5.2 </span>Identifiers</h3>
- <p>The <abbr title="Resource Description Framework">RDF</abbr> Concepts document [<cite><a class="bibref" href="#bib-RDF11-CONCEPTS">RDF11-CONCEPTS</a></cite>]
- defines the three types of <abbr title="Resource Description Framework">RDF</abbr> data that can act as node
+ <p>The RDF Concepts document [<cite><a class="bibref" href="#bib-RDF11-CONCEPTS">RDF11-CONCEPTS</a></cite>]
+ defines the three types of RDF data that can act as node
and/or predicate:</p>
<dl>
@@ -1512,7 +1488,7 @@
<li>transformed from <code>rdf:ID</code> attribute values.</li>
</ul>
- <p>Within <abbr title="Resource Description Framework">RDF</abbr>/XML, XML QNames are transformed into
+ <p>Within RDF/XML, XML QNames are transformed into
IRIs
by appending the XML local name to the namespace name (IRI).
For example, if the XML namespace prefix <code>foo</code> has
@@ -1548,14 +1524,14 @@
<p>Blank nodes can act as subject node and as object node.</p>
<p><a href="http://www.w3.org/TR/rdf11-concepts/#section-blank-nodes">Blank nodes</a>
- have distinct identity in the <abbr title="Resource Description Framework">RDF</abbr> graph.
- When the graph is written in a syntax such as <abbr title="Resource Description Framework">RDF</abbr>/XML, these
+ have distinct identity in the RDF graph.
+ When the graph is written in a syntax such as RDF/XML, these
blank nodes may need graph-local identifiers and a syntax
in order to preserve this distinction. These local identifiers are called
blank node identifiers
- and are used in <abbr title="Resource Description Framework">RDF</abbr>/XML as values of the <code>rdf:nodeID</code> attribute
+ and are used in RDF/XML as values of the <code>rdf:nodeID</code> attribute
with the syntax given in <a href="#nodeIdAttr">Production nodeIdAttr</a>.
- Blank node identifiers in <abbr title="Resource Description Framework">RDF</abbr>/XML are scoped to the XML Information Set
+ Blank node identifiers in RDF/XML are scoped to the XML Information Set
<a href="http://www.w3.org/TR/xml-infoset/#infoitem.document">document information item</a>.</p>
<p>If no blank node identifier is given explicitly as an
@@ -1571,7 +1547,7 @@
values and ensure no generated blank node identifiers ever used that
prefix. Another would be to map all <code>rdf:nodeID</code> attribute
values to new generated blank node identifiers and perform that mapping
- on all such values in the <abbr title="Resource Description Framework">RDF</abbr>/XML document.</p>
+ on all such values in the RDF/XML document.</p>
</dd>
</dl>
@@ -1584,7 +1560,7 @@
<section id="section-baseURIs" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter">
<h3 aria-level="2" role="heading" id="h3_section-baseURIs"><span class="secno">5.3 </span>Resolving IRIs</h3>
- <p><abbr title="Resource Description Framework">RDF</abbr>/XML supports
+ <p>RDF/XML supports
XML Base [<cite><a class="bibref" href="#bib-XMLBASE">XMLBASE</a></cite>]
which defines a
<a class="termref" href="#eventterm-element-base-uri"><span class="arrow">·</span>base-uri<span class="arrow">·</span></a>
@@ -1596,14 +1572,14 @@
These specifications do not specify an algorithm for resolving a
fragment identifier alone, such as <code>#foo</code>, or the empty
string <code>""</code> into an
- IRI. In <abbr title="Resource Description Framework">RDF</abbr>/XML, a fragment identifier
+ IRI. In RDF/XML, a fragment identifier
is transformed into an IRI
by appending the fragment identifier to the in-scope base URI. The
empty string is transformed
into an IRI by substituting the in-scope base URI.
</p>
- <div class="note"><div class="note-title" aria-level="3" role="heading" id="h_note_4"><span>Note</span></div><p class=""><strong>Test:</strong>
+ <div class="note"><div class="note-title" aria-level="3" role="heading" id="h_note_2"><span>Note</span></div><p class=""><strong>Test:</strong>
indicated by: <br />
<a href="http://www.w3.org/2000/10/rdf-tests/rdfcore/xmlbase/test001.rdf">test001.rdf</a> and
<a href="http://www.w3.org/2000/10/rdf-tests/rdfcore/xmlbase/test001.nt">test001.nt</a>
@@ -1627,19 +1603,19 @@
Uniform Resource Identifiers (URI) [<cite><a class="bibref" href="#bib-RFC3986">RFC3986</a></cite>].
</p>
- <div class="note"><div class="note-title" aria-level="3" role="heading" id="h_note_5"><span>Note</span></div><p class=""><strong>Test:</strong>
+ <div class="note"><div class="note-title" aria-level="3" role="heading" id="h_note_3"><span>Note</span></div><p class=""><strong>Test:</strong>
Indicated by
<a href="http://www.w3.org/2000/10/rdf-tests/rdfcore/xmlbase/test013.rdf">test013.rdf</a> and
<a href="http://www.w3.org/2000/10/rdf-tests/rdfcore/xmlbase/test013.nt">test013.nt</a>
</p></div>
- <div class="note"><div class="note-title" aria-level="3" role="heading" id="h_note_6"><span>Note</span></div><p class=""><strong>Implementation Note (Informative):</strong>
+ <div class="note"><div class="note-title" aria-level="3" role="heading" id="h_note_4"><span>Note</span></div><p class=""><strong>Implementation Note (Informative):</strong>
When using a hierarchical base
URI that has no path component (/), it must be added before using as a
base URI for resolving.
</p></div>
- <div class="note"><div class="note-title" aria-level="3" role="heading" id="h_note_7"><span>Note</span></div><p class=""><strong>Test:</strong>
+ <div class="note"><div class="note-title" aria-level="3" role="heading" id="h_note_5"><span>Note</span></div><p class=""><strong>Test:</strong>
Indicated by
<a href="http://www.w3.org/2000/10/rdf-tests/rdfcore/xmlbase/test011.rdf">test011.rdf</a> and
<a href="http://www.w3.org/2000/10/rdf-tests/rdfcore/xmlbase/test011.nt">test011.nt</a>
@@ -1660,13 +1636,13 @@
<a class="termref" href="#eventterm-attribute-string-value"><span class="arrow">·</span>string-value<span class="arrow">·</span></a>
accessor of the matched attribute and the
<a class="termref" href="#eventterm-element-base-uri"><span class="arrow">·</span>base-uri<span class="arrow">·</span></a>
- accessor of the matched attribute is unique within a single <abbr title="Resource Description Framework">RDF</abbr>/XML
+ accessor of the matched attribute is unique within a single RDF/XML
document.</p>
<p>The syntax of the names must match the
<a href="#rdf-id">rdf-id production</a>.</p>
- <div class="note"><div class="note-title" aria-level="3" role="heading" id="h_note_8"><span>Note</span></div><p class=""><strong>Test:</strong>
+ <div class="note"><div class="note-title" aria-level="3" role="heading" id="h_note_6"><span>Note</span></div><p class=""><strong>Test:</strong>
Indicated by
<a href="http://www.w3.org/2000/10/rdf-tests/rdfcore/xmlbase/test014.rdf">test014.rdf</a> and
<a href="http://www.w3.org/2000/10/rdf-tests/rdfcore/xmlbase/test014.nt">test014.nt</a>
@@ -1685,18 +1661,18 @@
<dl>
<dt>Definition:</dt>
- <dd>An <dfn id="dfn-rdf-document"><abbr title="Resource Description Framework">RDF</abbr> Document</dfn> is a serialization of an
- <a href="http://www.w3.org/TR/rdf-concepts/#dfn-rdf-graph"><abbr title="Resource Description Framework">RDF</abbr> Graph</a>
+ <dd>An <dfn id="dfn-rdf-document">RDF Document</dfn> is a serialization of an
+ <a href="http://www.w3.org/TR/rdf-concepts/#dfn-rdf-graph">RDF Graph</a>
into a concrete syntax.</dd>
<dt>Definition:<br /></dt>
- <dd>An <dfn id="dfn-rdf-xml-document"><abbr title="Resource Description Framework">RDF</abbr>/XML Document</dfn> is an
- <a class="termref" href="#dfn-rdf-document"><abbr title="Resource Description Framework">RDF</abbr> Document</a> written in the
- XML syntax for <abbr title="Resource Description Framework">RDF</abbr> as defined in this document.</dd>
+ <dd>An <dfn id="dfn-rdf-xml-document">RDF/XML Document</dfn> is an
+ <a class="termref" href="#dfn-rdf-document">RDF Document</a> written in the
+ XML syntax for RDF as defined in this document.</dd>
<dt>Conformance:<br /></dt>
- <dd>An <a class="termref" href="#dfn-rdf-xml-document"><abbr title="Resource Description Framework">RDF</abbr>/XML Document</a> is a
- <dfn id="dfn-conforming-document">conforming <abbr title="Resource Description Framework">RDF</abbr>/XML document</dfn>
+ <dd>An <a class="termref" href="#dfn-rdf-xml-document">RDF/XML Document</a> is a
+ <dfn id="dfn-conforming-document">conforming RDF/XML document</dfn>
if it adheres to the specification defined in this document.</dd>
</dl>
</section>
@@ -1715,7 +1691,7 @@
<h2 aria-level="1" role="heading" id="h2_section-Data-Model"><span class="secno">6. </span>Syntax Data Model</h2>
<div>
- <p>This document specifies the syntax of <abbr title="Resource Description Framework">RDF</abbr>/XML as a grammar on an
+ <p>This document specifies the syntax of RDF/XML as a grammar on an
alphabet of symbols. The symbols are called <em>events</em> in the
style of the XPATH
<a href="http://www.w3.org/TR/xpath#infoset">Information Set Mapping</a>.
@@ -1726,31 +1702,31 @@
of events produced by the [<cite><a class="bibref" href="#bib-SAX">SAX</a></cite>] XML API from
the same XML document. Sequences of events may be checked against
the grammar to determine whether they are or are not syntactically
- well-formed <abbr title="Resource Description Framework">RDF</abbr>/XML.</p>
+ well-formed RDF/XML.</p>
<p>The grammar productions may include actions which fire when the
production is recognized. Taken together these actions define a
- transformation from any syntactically well-formed <abbr title="Resource Description Framework">RDF</abbr>/XML sequence of
- events into an <abbr title="Resource Description Framework">RDF</abbr> graph represented in the N-Triples [<cite><a class="bibref" href="#bib-N-TRIPLES">N-TRIPLES</a></cite>]
+ transformation from any syntactically well-formed RDF/XML sequence of
+ events into an RDF graph represented in the N-Triples [<cite><a class="bibref" href="#bib-N-TRIPLES">N-TRIPLES</a></cite>]
language.</p>
<p>The model given here illustrates one way to create a representation of
- an <abbr title="Resource Description Framework">RDF</abbr> Graph
- from an <abbr title="Resource Description Framework">RDF</abbr>/XML document. It does not mandate any implementation
+ an RDF Graph
+ from an RDF/XML document. It does not mandate any implementation
method — any other method that results in a representation of the same
- <abbr title="Resource Description Framework">RDF</abbr> Graph may be used.</p>
+ RDF Graph may be used.</p>
<p>In particular:</p>
<ul>
<li>This specification permits any
- representation of an <abbr title="Resource Description Framework">RDF</abbr> graph;
+ representation of an RDF graph;
in particular, it does not require the use of N-Triples [<cite><a class="bibref" href="#bib-N-TRIPLES">N-TRIPLES</a></cite>].</li>
<li>This specification does not require the use of
[<cite><a class="bibref" href="#bib-XPATH">XPATH</a></cite>] or [<cite><a class="bibref" href="#bib-SAX">SAX</a></cite>]</li>
<li>This specification places no constraints on the order in which
- software transforming <abbr title="Resource Description Framework">RDF</abbr>/XML into a representation of a graph,
+ software transforming RDF/XML into a representation of a graph,
constructs the representation of the graph.</li>
- <li>Software transforming <abbr title="Resource Description Framework">RDF</abbr>/XML into a representation of a graph
+ <li>Software transforming RDF/XML into a representation of a graph
<em class="rfc2119" title="MAY">MAY</em> eliminate duplicate predicate arcs.</li>
</ul>
@@ -1762,14 +1738,14 @@
<p>The Infoset requires support for
XML Base [<cite><a class="bibref" href="#bib-XMLBASE">XMLBASE</a></cite>].
- <abbr title="Resource Description Framework">RDF</abbr>/XML uses the information item property [base URI], discussed in
+ RDF/XML uses the information item property [base URI], discussed in
<a href="#section-baseURIs">section 5.3</a>
</p>
<p>This specification requires an
XML Information Set [<cite><a class="bibref" href="#bib-XML-INFOSET">XML-INFOSET</a></cite>]
which supports at least the following information items and
- properties for <abbr title="Resource Description Framework">RDF</abbr>/XML:</p>
+ properties for RDF/XML:</p>
<dl>
<dt><a href="http://www.w3.org/TR/xml-infoset/#infoitem.document">document information item</a></dt>
@@ -1963,7 +1939,7 @@
<dt id="eventterm-element-subject">subject</dt>
<dd>Has no initial value. Takes a value that is an
<a href="#section-identifier-node">Identifier</a> event.
- This accessor is used on elements that deal with one node in the <abbr title="Resource Description Framework">RDF</abbr> graph,
+ This accessor is used on elements that deal with one node in the RDF graph,
this generally being the subject of a statement.</dd>
</dl>
@@ -2014,13 +1990,13 @@
<code>ID</code>, <code>about</code>, <code>resource</code>,
<code>parseType</code> or <code>type</code>, set to a string
value of the concatenation of the
- <a class="termref" href="#rdf-ns-uri"><span class="arrow">·</span><abbr title="Resource Description Framework">RDF</abbr> namespace IRI<span class="arrow">·</span></a>
+ <a class="termref" href="#rdf-ns-uri"><span class="arrow">·</span>RDF namespace IRI<span class="arrow">·</span></a>
and the value of the <a class="termref" href="#eventterm-attribute-local-name"><span class="arrow">·</span>local-name<span class="arrow">·</span></a> accessor. Other non-namespaced
<a class="termref" href="#eventterm-attribute-local-name"><span class="arrow">·</span>local-name<span class="arrow">·</span></a> accessor values are
forbidden.</p>
<p>The support for a limited set of non-namespaced names is
- <em class="rfc2119" title="REQUIRED">REQUIRED</em> and intended to allow <abbr title="Resource Description Framework">RDF</abbr>/XML documents specified in
+ <em class="rfc2119" title="REQUIRED">REQUIRED</em> and intended to allow RDF/XML documents specified in
[<cite><a class="bibref" href="#bib-RDFMS">RDFMS</a></cite>] to remain valid; new documents
<em class="rfc2119" title="SHOULD NOT">SHOULD NOT</em> use these unqualified attributes and applications <em class="rfc2119" title="MAY">MAY</em>
choose to warn when the unqualified form is seen in a document.</p>
@@ -2101,7 +2077,7 @@
<a class="termref" href="#eventterm-identifier-identifier"><span class="arrow">·</span>identifier<span class="arrow">·</span></a> accessor.
</p>
- <p>For further information on identifiers in the <abbr title="Resource Description Framework">RDF</abbr> graph, see
+ <p>For further information on identifiers in the RDF graph, see
<a href="#section-Identifiers">section 5.2</a>.</p>
</section>
@@ -2125,8 +2101,8 @@
<dd>The value is a function of the value of the
<a class="termref" href="#eventterm-blanknodeid-identifier"><span class="arrow">·</span>identifier<span class="arrow">·</span></a> accessor.
The value begins with "_:" and the entire value <em class="rfc2119" title="MUST">MUST</em> match the
- <a href="http://www.w3.org/TR/2004/REC-rdf-testcases-20040210/#ntriples">N-Triples</a>
- <a href="http://www.w3.org/TR/2004/REC-rdf-testcases-20040210/#nodeID">nodeID</a> production.
+ N-Triples
+ <a href="http://www.w3.org/TR/n-triples/#grammar-production-BLANK_NODE_LABEL">BLANK_NODE_LABELD</a> production.
The function <em class="rfc2119" title="MUST">MUST</em> preserve distinct blank node identity as
discussed in in section <a href="#section-Identifiers">5.2
Identifiers</a>.</dd>
@@ -2137,7 +2113,7 @@
<a class="termref" href="#eventterm-blanknodeid-identifier"><span class="arrow">·</span>identifier<span class="arrow">·</span></a> accessor.
</p>
- <p>For further information on identifiers in the <abbr title="Resource Description Framework">RDF</abbr> graph, see
+ <p>For further information on identifiers in the RDF graph, see
<a href="#section-Identifiers">section 5.2</a>.</p>
</section>
@@ -2148,7 +2124,7 @@
<section id="section-literal-node" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter">
<h4 aria-level="3" role="heading" id="h4_section-literal-node"><span class="secno">6.1.8 </span>Plain Literal Event</h4>
- <div class="note"><div class="note-title" aria-level="4" role="heading" id="h_note_9"><span>Note</span></div><p class=""><abbr title="Resource Description Framework">RDF</abbr>/XML plain literals are in <abbr title="Resource Description Framework">RDF</abbr> 1.1 treated as
+ <div class="note"><div class="note-title" aria-level="4" role="heading" id="h_note_7"><span>Note</span></div><p class="">RDF/XML plain literals are in RDF 1.1 treated as
syntactic sugar for a literal with datatype
<code>xsd:string</code> (in case no language tag is present)
or as a literal with datatype <code>rdf:langString</code> (in
@@ -2163,7 +2139,7 @@
<dd>Takes a string value.</dd>
<dt id="eventterm-literal-literal-language">literal-language</dt>
- <dd>Takes a string value used as a language tag in an <abbr title="Resource Description Framework">RDF</abbr> plain literal.</dd>
+ <dd>Takes a string value used as a language tag in an RDF plain literal.</dd>
<dt id="eventterm-literal-string-value">string-value</dt>
<dd><p>The value is calculated from the other accessors as follows.</p>
@@ -2181,7 +2157,7 @@
and the value of the
<a class="termref" href="#eventterm-literal-literal-language"><span class="arrow">·</span>literal-language<span class="arrow">·</span></a> accessor.</p>
- <p>The escaping of the <a class="termref" href="#eventterm-literal-literal-value"><span class="arrow">·</span>literal-value<span class="arrow">·</span></a> accessor value uses the <a href="http://www.w3.org/TR/2004/REC-rdf-testcases-20040210/#ntriples">N-Triples</a>
+ <p>The escaping of the <a class="termref" href="#eventterm-literal-literal-value"><span class="arrow">·</span>literal-value<span class="arrow">·</span></a> accessor value uses the N-Triples
escapes for strings as described in [<cite><a class="bibref" href="#bib-N-TRIPLES">N-TRIPLES</a></cite>]
for escaping certain characters such as ". </p>
</dd>
@@ -2191,7 +2167,7 @@
<a class="termref" href="#eventterm-literal-literal-value"><span class="arrow">·</span>literal-value<span class="arrow">·</span></a> and
<a class="termref" href="#eventterm-literal-literal-language"><span class="arrow">·</span>literal-language<span class="arrow">·</span></a> accessors.</p>
- <div class="note"><div class="note-title" aria-level="4" role="heading" id="h_note_10"><span>Note</span></div><p id="literal-comb-char-note1" class="">
+ <div class="note"><div class="note-title" aria-level="4" role="heading" id="h_note_8"><span>Note</span></div><p id="literal-comb-char-note1" class="">
<strong>Interoperability Note (Informative):</strong>
Literals beginning with a Unicode combining character are
allowed however they may cause interoperability problems.
@@ -2240,14 +2216,14 @@
<a class="termref" href="#eventterm-typedliteral-literal-value"><span class="arrow">·</span>literal-value<span class="arrow">·</span></a>
and <a class="termref" href="#eventterm-typedliteral-literal-datatype"><span class="arrow">·</span>literal-datatype<span class="arrow">·</span></a> accessors.</p>
- <div class="note"><div class="note-title" aria-level="4" role="heading" id="h_note_11"><span>Note</span></div><p class="" id="literal-comb-char-note2">
+ <div class="note"><div class="note-title" aria-level="4" role="heading" id="h_note_9"><span>Note</span></div><p class="" id="literal-comb-char-note2">
<strong>Interoperability Note (Informative):</strong>
Literals beginning with a Unicode combining character are
allowed however they may cause interoperability problems.
See [<cite><a class="bibref" href="#bib-CHARMOD">CHARMOD</a></cite>] for further information.
</p></div>
- <div class="note"><div class="note-title" aria-level="4" role="heading" id="h_note_12"><span>Note</span></div><p id="literal-white-space-normalization-note" class="">
+ <div class="note"><div class="note-title" aria-level="4" role="heading" id="h_note_10"><span>Note</span></div><p id="literal-white-space-normalization-note" class="">
<strong>Implementation Note (Informative): </strong>
In XML Schema (part 1) [<cite><a class="bibref" href="#bib-XMLSCHEMA-1">XMLSCHEMA-1</a></cite>],
<a href="http://www.w3.org/TR/2001/REC-xmlschema-1-20010502/#section-White-Space-Normalization-during-Validation">white
@@ -2292,7 +2268,7 @@
<p>The following notation is used to describe matching the sequence
of data model events as given in <a href="#section-Data-Model">Section 6</a>
and the actions to perform for the matches.
- The <abbr title="Resource Description Framework">RDF</abbr>/XML grammar is defined in terms of mapping from these matched
+ The RDF/XML grammar is defined in terms of mapping from these matched
data model events to triples, using notation of the form:</p>
<blockquote>
@@ -2483,7 +2459,7 @@
<tr>
<td>generated-blank-node-id()</td>
<td>A string value for a new distinct generated
- <a href="http://www.w3.org/TR/2004/REC-rdf-concepts-20040210/#dfn-blank-node-id">blank node identifier</a>
+ blank node identifier
as defined in <a href="#section-Identifiers">section 5.2 Identifiers</a>.
</td>
@@ -2522,7 +2498,7 @@
<section id="section-Infoset-Grammar" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter">
<!--OddPage-->
-<h2 aria-level="1" role="heading" id="h2_section-Infoset-Grammar"><span class="secno">7. </span><abbr title="Resource Description Framework">RDF</abbr>/XML Grammar</h2>
+<h2 aria-level="1" role="heading" id="h2_section-Infoset-Grammar"><span class="secno">7. </span>RDF/XML Grammar</h2>
@@ -2534,7 +2510,7 @@
<div class="productionOuter"><div class="productionInner">
<table>
<tbody><tr>
- <td><a href="#coreSyntaxTerms">7.2.2</a> <a href="#coreSyntaxTerms">coreSyntaxTerms</a></td> <td><code>rdf:<abbr title="Resource Description Framework">RDF</abbr></code> | <code>rdf:ID</code> | <code>rdf:about</code> | <code>rdf:parseType</code> | <code>rdf:resource</code> | <code>rdf:nodeID</code> | <code>rdf:datatype</code></td>
+ <td><a href="#coreSyntaxTerms">7.2.2</a> <a href="#coreSyntaxTerms">coreSyntaxTerms</a></td> <td><code>rdf:RDF</code> | <code>rdf:ID</code> | <code>rdf:about</code> | <code>rdf:parseType</code> | <code>rdf:resource</code> | <code>rdf:nodeID</code> | <code>rdf:datatype</code></td>
</tr>
<tr>
@@ -2557,12 +2533,12 @@
</tr>
<tr>
- <td><a href="#doc">7.2.8</a> <a href="#doc">doc</a></td> <td>root(<a href="#eventterm-root-document-element">document-element</a> == <a href="#RDF"><abbr title="Resource Description Framework">RDF</abbr></a>,
- <a href="#eventterm-root-children">children</a> == list(<a href="#RDF"><abbr title="Resource Description Framework">RDF</abbr></a>))</td>
+ <td><a href="#doc">7.2.8</a> <a href="#doc">doc</a></td> <td>root(<a href="#eventterm-root-document-element">document-element</a> == <a href="#RDF">RDF</a>,
+ <a href="#eventterm-root-children">children</a> == list(<a href="#RDF">RDF</a>))</td>
</tr>
<tr>
- <td><a href="#RDF">7.2.9</a> <a href="#RDF"><abbr title="Resource Description Framework">RDF</abbr></a></td> <td>start-element(<a href="#eventterm-element-URI">URI</a> == <code>rdf:<abbr title="Resource Description Framework">RDF</abbr></code>,
+ <td><a href="#RDF">7.2.9</a> <a href="#RDF">RDF</a></td> <td>start-element(<a href="#eventterm-element-URI">URI</a> == <code>rdf:RDF</code>,
<a href="#eventterm-element-attributes">attributes</a> == set())<br />
<a href="#nodeElementList">nodeElementList</a><br />
@@ -2738,22 +2714,22 @@
<section id="start" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter">
<h4 aria-level="3" role="heading" id="h4_start"><span class="secno">7.2.1 </span>Grammar start</h4>
- <p>If the <abbr title="Resource Description Framework">RDF</abbr>/XML is a standalone XML document
+ <p>If the RDF/XML is a standalone XML document
(identified by presentation as an
- application/rdf+xml <a href="#section-MIME-Type"><abbr title="Resource Description Framework">RDF</abbr> MIME type</a> object,
+ application/rdf+xml <a href="#section-MIME-Type">RDF MIME type</a> object,
or by some other means) then the grammar may start with
production <a href="#doc">doc</a> or
production <a href="#nodeElement">nodeElement</a>.</p>
- <p>If the content is known to be <abbr title="Resource Description Framework">RDF</abbr>/XML by context, such as when
- <abbr title="Resource Description Framework">RDF</abbr>/XML is embedded inside other XML content, then the grammar
+ <p>If the content is known to be RDF/XML by context, such as when
+ RDF/XML is embedded inside other XML content, then the grammar
can either start
at <a href="#section-element-node">Element Event</a>
- <a href="#RDF"><abbr title="Resource Description Framework">RDF</abbr></a>
+ <a href="#RDF">RDF</a>
(only when an element is legal at that point in the XML)
or at production <a href="#nodeElementList">nodeElementList</a>
(only when element content is legal, since this is a list of elements).
- For such embedded <abbr title="Resource Description Framework">RDF</abbr>/XML, the
+ For such embedded RDF/XML, the
<a class="termref" href="#eventterm-element-base-uri"><span class="arrow">·</span>base-uri<span class="arrow">·</span></a>
value on the outermost element must be initialized from the containing
XML since no
@@ -2769,13 +2745,13 @@
<h4 aria-level="3" role="heading" id="h4_coreSyntaxTerms"><span class="secno">7.2.2 </span>Production coreSyntaxTerms</h4>
<div class="productionOuter"><div class="productionInner"><p>
- <code>rdf:<abbr title="Resource Description Framework">RDF</abbr></code> | <code>rdf:ID</code> | <code>rdf:about</code> | <code>rdf:parseType</code> | <code>rdf:resource</code> | <code>rdf:nodeID</code> | <code>rdf:datatype</code>
+ <code>rdf:RDF</code> | <code>rdf:ID</code> | <code>rdf:about</code> | <code>rdf:parseType</code> | <code>rdf:resource</code> | <code>rdf:nodeID</code> | <code>rdf:datatype</code>
</p></div></div>
- <p>A subset of the syntax terms from the <abbr title="Resource Description Framework">RDF</abbr> vocabulary in
+ <p>A subset of the syntax terms from the RDF vocabulary in
<a href="#section-Namespace">section 5.1</a>
- which are used in <abbr title="Resource Description Framework">RDF</abbr>/XML.
+ which are used in RDF/XML.
</p>
</section>
@@ -2790,9 +2766,9 @@
</p></div></div>
- <p>All the syntax terms from the <abbr title="Resource Description Framework">RDF</abbr> vocabulary in
+ <p>All the syntax terms from the RDF vocabulary in
<a href="#section-Namespace">section 5.1</a>
- which are used in <abbr title="Resource Description Framework">RDF</abbr>/XML.
+ which are used in RDF/XML.
</p>
</section>
@@ -2807,7 +2783,7 @@
</p></div></div>
- <p>These are the names from the <a href="#section-Namespace"><abbr title="Resource Description Framework">RDF</abbr> vocabulary</a>
+ <p>These are the names from the <a href="#section-Namespace">RDF vocabulary</a>
that have been withdrawn from the language. See the resolutions of
Issue <a href="http://www.w3.org/2000/03/rdf-tracking/#rdfms-aboutEach-on-object">rdfms-aboutEach-on-object</a>,
Issue <a href="http://www.w3.org/2000/03/rdf-tracking/#rdfms-abouteachprefix">rdfms-abouteachprefix</a> and
@@ -2815,7 +2791,7 @@
for further information.
</p>
- <div class="note"><div class="note-title" aria-level="4" role="heading" id="h_note_13"><span>Note</span></div><p class=""><strong>Error Test:</strong>
+ <div class="note"><div class="note-title" aria-level="4" role="heading" id="h_note_11"><span>Note</span></div><p class=""><strong>Error Test:</strong>
Indicated by
<a href="http://www.w3.org/2000/10/rdf-tests/rdfcore/rdfms-abouteach/error001.rdf">error001.rdf</a> and
<a href="http://www.w3.org/2000/10/rdf-tests/rdfcore/rdfms-abouteach/error002.rdf">error002.rdf</a>
@@ -2871,9 +2847,9 @@
<h4 aria-level="3" role="heading" id="h4_doc"><span class="secno">7.2.8 </span>Production doc</h4>
<div class="productionOuter"><div class="productionInner"><p>
- root(<a href="#eventterm-root-document-element">document-element</a> == <a href="#RDF"><abbr title="Resource Description Framework">RDF</abbr></a>,<br />
-
- <a href="#eventterm-root-children">children</a> == list(<a href="#RDF"><abbr title="Resource Description Framework">RDF</abbr></a>))
+ root(<a href="#eventterm-root-document-element">document-element</a> == <a href="#RDF">RDF</a>,<br />
+
+ <a href="#eventterm-root-children">children</a> == list(<a href="#RDF">RDF</a>))
</p></div></div>
</section>
@@ -2881,10 +2857,10 @@
<!-- production RDF -->
<section id="RDF" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter">
- <h4 aria-level="3" role="heading" id="h4_RDF"><span class="secno">7.2.9 </span>Production <abbr title="Resource Description Framework">RDF</abbr></h4>
+ <h4 aria-level="3" role="heading" id="h4_RDF"><span class="secno">7.2.9 </span>Production RDF</h4>
<div class="productionOuter"><div class="productionInner"><p>
- start-element(<a href="#eventterm-element-URI">URI</a> == <code>rdf:<abbr title="Resource Description Framework">RDF</abbr></code>,<br />
+ start-element(<a href="#eventterm-element-URI">URI</a> == <code>rdf:RDF</code>,<br />
<a href="#eventterm-element-attributes">attributes</a> == set())<br />
<a href="#nodeElementList">nodeElementList</a><br />
@@ -3149,12 +3125,12 @@
<p>For element <em>e</em> and the literal <em>l</em>
that is the <code>rdf:parseType="Literal"</code> content.
<em>l</em> is not transformed by the syntax data model mapping into events
- (as noted in <a href="#section-Data-Model">6 Syntax Data Model</a>)
+ (as noted in section <a href="#section-Data-Model">6 Syntax Data Model</a>)
but remains an XML Infoset of XML Information items.</p>
<p><em>l</em> is transformed into the lexical form of an
- <a href="http://www.w3.org/TR/2004/REC-rdf-concepts-20040210/#dfn-rdf-XMLLiteral">XML literal</a>
- in the <abbr title="Resource Description Framework">RDF</abbr> graph <em>x</em> (a Unicode string)
+ <a href="http://www.w3.org/TR/rdf11-concepts/#dfn-rdf-xmlliteral">XML literal</a>
+ in the RDF graph <em>x</em> (a Unicode string)
by the following algorithm. This does not mandate any implementation
method — any other method that gives the same result may be used.</p>
@@ -3177,15 +3153,14 @@
of Unicode characters)</li>
-->
- <li>Use <em>l</em> to construct an an <a href="http://www.w3.org/TR/xpath-datamodel-30/#sequences">XPath
- sequence</a>.</li>
- <li>Apply <a href="http://www.w3.org/TR/xpath-functions-30/#func-serialize">http://www.w3.org/TR/xpath-functions-30/#func-serialize</a> to this sequence to give an xsd:string <em>x</em>.</li>
+ <li>Use <em>l</em> to construct an <a href="http://www.w3.org/TR/xpath-datamodel-30/#sequences">XPath
+ sequence</a> [<cite><a class="bibref" href="#bib-XPATH-DATAMODEL-30">XPATH-DATAMODEL-30</a></cite>].</li>
+ <li>Apply <a href="http://www.w3.org/TR/xpath-functions-30/#func-serialize">http://www.w3.org/TR/xpath-functions-30/#func-serialize</a> [<cite><a class="bibref" href="#bib-XPATH-FUNCTIONS-30">XPATH-FUNCTIONS-30</a></cite>]
+ to this sequence to give an xsd:string <em>x</em>.</li>
<li>The Unicode string <em>x</em> is used as the lexical form of <em>l</em></li>
- <li>This Unicode string
- <em>x</em> <em class="rfc2119" title="SHOULD">SHOULD</em> be in NFC Normal Form C [<cite><a class="bibref" href="#bib-NFC">NFC</a></cite>]</li>
+ <li>This Unicode string <em>x</em> <em class="rfc2119" title="SHOULD">SHOULD</em> be in NFC Normal Form C [<cite><a class="bibref" href="#bib-NFC">NFC</a></cite>]</li>
</ol>
-
<p>Then <em>o</em> := typed-literal(<a href="#eventterm-typedliteral-literal-value">literal-value</a> := <em>x</em>, <a href="#eventterm-typedliteral-literal-datatype">literal-datatype</a> := <code>http://www.w3.org/1999/02/22-rdf-syntax-ns#XMLLiteral</code> )
and the following statement is added to the graph:</p>
@@ -3194,7 +3169,7 @@
</p></div></div>
- <div class="note"><div class="note-title" aria-level="4" role="heading" id="h_note_14"><span>Note</span></div><p class=""><strong>Test:</strong>
+ <div class="note"><div class="note-title" aria-level="4" role="heading" id="h_note_12"><span>Note</span></div><p class=""><strong>Test:</strong>
Empty literal case indicated by
<a href="http://www.w3.org/2000/10/rdf-tests/rdfcore/rdfms-empty-property-elements/test009.rdf">test009.rdf</a>
and
@@ -3235,7 +3210,7 @@
</p></div></div>
- <div class="note"><div class="note-title" aria-level="4" role="heading" id="h_note_15"><span>Note</span></div><p class=""><strong>Test:</strong>
+ <div class="note"><div class="note-title" aria-level="4" role="heading" id="h_note_13"><span>Note</span></div><p class=""><strong>Test:</strong>
Indicated by
<a href="http://www.w3.org/2000/10/rdf-tests/rdfcore/rdfms-empty-property-elements/test004.rdf">test004.rdf</a>
and
@@ -3394,14 +3369,14 @@
using the reification rules in
<a href="#section-Reification">section 7.3</a>.</p>
- <div class="note"><div class="note-title" aria-level="4" role="heading" id="h_note_16"><span>Note</span></div><p class=""><strong>Test:</strong>
+ <div class="note"><div class="note-title" aria-level="4" role="heading" id="h_note_14"><span>Note</span></div><p class=""><strong>Test:</strong>
Indicated by
<a href="http://www.w3.org/2000/10/rdf-tests/rdfcore/rdfms-empty-property-elements/test002.rdf">test002.rdf</a>
and
<a href="http://www.w3.org/2000/10/rdf-tests/rdfcore/rdfms-empty-property-elements/test002.nt">test002.nt</a>
</p></div>
- <div class="note"><div class="note-title" aria-level="4" role="heading" id="h_note_17"><span>Note</span></div><p class=""><strong>Test:</strong>
+ <div class="note"><div class="note-title" aria-level="4" role="heading" id="h_note_15"><span>Note</span></div><p class=""><strong>Test:</strong>
Indicated by
<a href="http://www.w3.org/2000/10/rdf-tests/rdfcore/rdfms-empty-property-elements/test005.rdf">test005.rdf</a>
and
@@ -3460,14 +3435,14 @@
</ul>
- <div class="note"><div class="note-title" aria-level="4" role="heading" id="h_note_18"><span>Note</span></div><p class=""><strong>Test:</strong>
+ <div class="note"><div class="note-title" aria-level="4" role="heading" id="h_note_16"><span>Note</span></div><p class=""><strong>Test:</strong>
Indicated by
<a href="http://www.w3.org/2000/10/rdf-tests/rdfcore/rdfms-empty-property-elements/test013.rdf">test013.rdf</a>
and
<a href="http://www.w3.org/2000/10/rdf-tests/rdfcore/rdfms-empty-property-elements/test013.nt">test013.nt</a>
</p></div>
- <div class="note"><div class="note-title" aria-level="4" role="heading" id="h_note_19"><span>Note</span></div><p class=""><strong>Test:</strong>
+ <div class="note"><div class="note-title" aria-level="4" role="heading" id="h_note_17"><span>Note</span></div><p class=""><strong>Test:</strong>
Indicated by
<a href="http://www.w3.org/2000/10/rdf-tests/rdfcore/rdfms-empty-property-elements/test014.rdf">test014.rdf</a>
and
@@ -3730,13 +3705,10 @@
<section id="section-Serialising" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter">
<!--OddPage-->
-<h2 aria-level="1" role="heading" id="h2_section-Serialising"><span class="secno">8. </span>Serializing an <abbr title="Resource Description Framework">RDF</abbr> Graph to <abbr title="Resource Description Framework">RDF</abbr>/XML</h2>
-
- <p>There are some
- <a href="http://www.w3.org/TR/2004/REC-rdf-concepts-20040210/#dfn-rdf-graph"><abbr title="Resource Description Framework">RDF</abbr> Graphs</a>
- as defined in
- <a href="http://www.w3.org/TR/2004/REC-rdf-concepts-20040210/"><abbr title="Resource Description Framework">RDF</abbr> Concepts and Abstract Syntax</a>
- that cannot be serialized in <abbr title="Resource Description Framework">RDF</abbr>/XML. These are those that:</p>
+<h2 aria-level="1" role="heading" id="h2_section-Serialising"><span class="secno">8. </span>Serializing an RDF Graph to RDF/XML</h2>
+
+ <p>There are some RDF Graphs as defined in
+ [<cite><a class="bibref" href="#bib-RDF11-CONCEPTS">RDF11-CONCEPTS</a></cite>]that cannot be serialized in RDF/XML. These are those that:</p>
<dl>
<dt>Use property names that cannot be turned into XML namespace-qualified names.<br /></dt>
@@ -3744,15 +3716,14 @@
(<a href="http://www.w3.org/TR/REC-xml-names/#ns-qualnames">QName</a>)
has restrictions on the legal characters such that not all property URIs
can be expressed as these names.
- It is recommended that implementors of <abbr title="Resource Description Framework">RDF</abbr> serializers, in order to
+ It is recommended that implementors of RDF serializers, in order to
break a URI into a namespace name and a local name, split it after
the last XML non-<a href="http://www.w3.org/TR/REC-xml-names/#NT-NCName">NCName</a>
-
character, ensuring that the first character of the name is a
<a href="http://www.w3.org/TR/REC-xml#NT-Letter">Letter</a> or '_'.
If the URI ends in a
non-<a href="http://www.w3.org/TR/REC-xml-names/#NT-NCName">NCName</a>
- character then throw a "this graph cannot be serialized in <abbr title="Resource Description Framework">RDF</abbr>/XML"
+ character then throw a "this graph cannot be serialized in RDF/XML"
exception or error.
</dd>
@@ -3761,12 +3732,16 @@
<a href="#syntaxTerms">syntaxTerms</a> production.
</dd>
+ <dt>Use the <code>rdf:HTML</code> datatype</dt>
+ <dd>This datatype as introduced in RDF 1.1
+ [<cite><a class="bibref" href="#bib-RDF11-CONCEPTS">RDF11-CONCEPTS</a></cite>]. </dd>
+
</dl>
- <div class="note"><div class="note-title" aria-level="2" role="heading" id="h_note_20"><span>Note</span></div><p class=""><strong>Implementation Note (Informative):</strong>
- When an <abbr title="Resource Description Framework">RDF</abbr> graph is serialized to <abbr title="Resource Description Framework">RDF</abbr>/XML and has an XML Schema
+ <div class="note"><div class="note-title" aria-level="2" role="heading" id="h_note_18"><span>Note</span></div><p class=""><strong>Implementation Note (Informative):</strong>
+ When an RDF graph is serialized to RDF/XML and has an XML Schema
Datatype (XSD), it <em class="rfc2119" title="SHOULD">SHOULD</em> be written in a form that does not require
- whitespace processing. XSD support is NOT required by <abbr title="Resource Description Framework">RDF</abbr> or <abbr title="Resource Description Framework">RDF</abbr>/XML
+ whitespace processing. XSD support is NOT required by RDF or RDF/XML
so this is optional.
</p></div>
</section>
@@ -3778,9 +3753,9 @@
<section class="informative" id="section-rdf-in-SVG" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter">
<!--OddPage-->
-<h2 aria-level="1" role="heading" id="h2_section-rdf-in-SVG"><span class="secno">9. </span>Using <abbr title="Resource Description Framework">RDF</abbr>/XML with SVG</h2><p><em>This section is non-normative.</em></p>
-
- <p>There is a standardized approach for associating <abbr title="Resource Description Framework">RDF</abbr> compatible
+<h2 aria-level="1" role="heading" id="h2_section-rdf-in-SVG"><span class="secno">9. </span>Using RDF/XML with SVG</h2><p><em>This section is non-normative.</em></p>
+
+ <p>There is a standardized approach for associating RDF compatible
metadata with SVG — the metadata element which was explicitly
designed for this purpose as defined in
<a href="http://www.w3.org/TR/SVG/metadata.html">Section 21 Metadata</a>
@@ -3799,7 +3774,7 @@
</p>
<p>This document contains two example graphs in SVG with such
- embedded <abbr title="Resource Description Framework">RDF</abbr>/XML inside the metadata element:
+ embedded RDF/XML inside the metadata element:
<a href="http://www.w3.org/TR/rdf-syntax-grammar/figure1.svg">figure 1</a>
and
@@ -3815,24 +3790,23 @@
<!--OddPage-->
<h2 aria-level="1" role="heading" id="h2_section-Acknowledgments"><span class="secno">A. </span>Acknowledgments</h2><p><em>This section is non-normative.</em></p>
- <p>Gavin Carothers provided the <abbr title="Resource Description Framework">RDF</abbr> 1.1 update for the <a href="parseTypeLiteralPropertyElt">Production
- parseTypeLiteralPropertyElt</a>.</p>
+ <p>Gavin Carothers provided the RDF 1.1 update for the <a href="parseTypeLiteralPropertyElt">Production
+ parseTypeLiteralPropertyElt</a>. Ivan Herman provided valuable
+ comments and reworked Figs 1 and 2. </p>
<p>This specification is a product of extended deliberations by the
- <a href="http://www.w3.org/TR/2004/REC-rdf-concepts-20040210/#section-Acknowledgments">members
- of the RDFcore Working Group and the <abbr title="Resource Description Framework">RDF</abbr> and <abbr title="Resource Description Framework">RDF</abbr> Schema Working Group</a>.</p>
+ members of the RDFcore Working Group and the RDF and RDF Schema Working Group.</p>
<p>The following people provided valuable contributions to the document:</p>
<ul>
<li>Dan Brickley, <abbr title="World Wide Web Consortium">W3C</abbr>/ILRT</li>
-
<li>Jeremy Carroll, HP Labs, Bristol</li>
<li>Graham Klyne, Nine by Nine</li>
<li>Bijan Parsia, MIND Lab at University of Maryland at College Park</li>
</ul>
- <p>This document is a product of extended deliberations by the <abbr title="Resource Description Framework">RDF</abbr>
+ <p>This document is a product of extended deliberations by the RDF
Core working group, whose members have included: Art Barstow (<abbr title="World Wide Web Consortium">W3C</abbr>)
Dave Beckett (ILRT), Dan Brickley (<abbr title="World Wide Web Consortium">W3C</abbr>/ILRT), Dan Connolly (<abbr title="World Wide Web Consortium">W3C</abbr>),
Jeremy Carroll (Hewlett Packard), Ron Daniel (Interwoven Inc), Bill
@@ -3844,9 +3818,9 @@
(IHMC), Sergey Melnik (Stanford University), Martyn Horner (Profium
Ltd).</p>
- <p>This specification also draws upon an earlier <abbr title="Resource Description Framework">RDF</abbr> Model and Syntax
- document edited by Ora Lassilla and Ralph Swick, and <abbr title="Resource Description Framework">RDF</abbr> Schema
- edited by Dan Brickley and R. V. Guha. <abbr title="Resource Description Framework">RDF</abbr> and <abbr title="Resource Description Framework">RDF</abbr> Schema Working
+ <p>This specification also draws upon an earlier RDF Model and Syntax
+ document edited by Ora Lassilla and Ralph Swick, and RDF Schema
+ edited by Dan Brickley and R. V. Guha. RDF and RDF Schema Working
group members who contributed to this earlier work are:
Nick Arnett (Verity), Tim Berners-Lee (<abbr title="World Wide Web Consortium">W3C</abbr>), Tim Bray (Textuality),
Dan Brickley (ILRT / University of Bristol), Walter Chang (Adobe),
@@ -3872,6 +3846,56 @@
</p>
</section>
+ <section class="appendix informative" id="changes-rdf11" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter">
+
+<!--OddPage-->
+<h2 aria-level="1" role="heading" id="h2_changes-rdf11"><span class="secno">B. </span>Changes to 2004 Recommendation</h2><p><em>This section is non-normative.</em></p>
+
+ <p>The following changes were made for the Edited
+ Recommendation version of this document for RDF 1.1.:</p>
+ <ol>
+ <li>Conversion to ResPec.</li>
+ <li>RDF 2004 errata handling:
+ <ol>
+ <li>Replaced hard-coded reference to XML and Unicode versions
+ (<a href="http://www.w3.org/2011/rdf-wg/wiki/TF-RDF-XML#Change_2:_hard_coded_reference_to_XML_and_Unicode_versions">background info</a>)</li>
+ <li>Corrected the resolve action with the signature resolve(e, s)
+ (<a href="http://www.w3.org/2011/rdf-wg/wiki/TF-RDF-XML#Change_3:_signature_resolve.28e.2C_s.29">background info</a>)</li>
+ <li>Added parent accessor to element events
+ (<a href="http://www.w3.org/2011/rdf-wg/wiki/TF-RDF-XML#Change_4:_missing_parent_accessor">background info</a>)</li>
+ <li>Allow datatyped empty literals
+ (<a href="http://www.w3.org/2011/rdf-wg/wiki/TF-RDF-XML#Change_5:_datatyped_empty_literals">background info</a>)</li>
+ <li>Removed ID and datatype exclusion on literal property
+ (<a href="http://www.w3.org/2011/rdf-wg/wiki/TF-RDF-XML#Change_6:_ID_and_datatype_exclusion_on_literal_property">background info</a>)</li>
+ </ol></li>
+ <li>Adapted and shortened introduction to reflect RDF 1.1</li>
+ <li>Updated references to RDF 1.1 documents</li>
+ <li>Replaced "(RDF) URI reference" with "IRI"</li>
+ <li>Removed Section on embedding RDF/XML into HTML</li>
+ <li>Removed "Specification" from the title to bring it in
+ line with other RDF 1.1 document titles</li>
+ <li>Updated references to other documents</li>
+ <li>Changed links in Sec. 2 examples from relative URI to
+ absolute URI; same for RELAX schema in Appendix.</li>
+ <li>Added note to section on plain-literal event</li>
+ <li>Updated link to QName definition in XML-NAMES</li>
+ <li>Added diff with 2004 Recommendation</li>
+ <li>Adapted <a href="#parseTypeLiteralPropertyElt">Production
+ parseTypeLiteralPropertyElt</a> to cater for the non-normative
+ status of <code>rdf:XMLLiteral</code>.</li>
+ <li>Improved version of Figs. 1 and 2 (with same
+ content)</li>
+ <li>Removed old changes section</li>
+ <li>Informative notes at start of Sec. 5.1 removed, as these
+ have become irrelevant.</li>
+ <li>Added new datatype <code>rdf:HTML</code> to the list of things that
+ cannot be serialized in RDF/XML.</li>
+ <li>Replaced the link to 2004 N-Triples <code>nodeID</code> production to
+ the RDF 1.1 N-Triples <code>BLANK_NODE_LABEL</code>
+ production.</li>
+ </ol>
+
+ </section>
<!-- TWELVETH PART : Syntax Schemas -->
@@ -3879,9 +3903,9 @@
<section class="appendix informative" id="section-Schemas" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter">
<!--OddPage-->
-<h2 aria-level="1" role="heading" id="h2_section-Schemas"><span class="secno">B. </span>Syntax Schemas</h2><p><em>This section is non-normative.</em></p>
-
- <p>This appendix contains XML schemas for validating <abbr title="Resource Description Framework">RDF</abbr>/XML forms.
+<h2 aria-level="1" role="heading" id="h2_section-Schemas"><span class="secno">C. </span>Syntax Schemas</h2><p><em>This section is non-normative.</em></p>
+
+ <p>This appendix contains XML schemas for validating RDF/XML forms.
These are example schemas for information only and are not part of
this specification.</p>
@@ -3889,20 +3913,20 @@
<!-- Compact Schema -->
<section class="informative" id="section-RELAXNG-Schema" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter">
- <h3 aria-level="2" role="heading" id="h3_section-RELAXNG-Schema"><span class="secno">B.1 </span>RELAX NG Compact Schema</h3><p><em>This section is non-normative.</em></p>
+ <h3 aria-level="2" role="heading" id="h3_section-RELAXNG-Schema"><span class="secno">C.1 </span>RELAX NG Compact Schema</h3><p><em>This section is non-normative.</em></p>
<p>This is an <a href="http://www.w3.org/TR/2004/REC-rdf-syntax-grammar-20040210/rdfxml.rnc">example
schema in
RELAX NG Compact</a> (for ease of reading)
- for <abbr title="Resource Description Framework">RDF</abbr>/XML. Applications can also use the
+ for RDF/XML. Applications can also use the
<a href="http://www.w3.org/TR/2004/REC-rdf-syntax-grammar-20040210/rdfxml.rng">RELAX NG XML version</a>.
These formats are described in
RELAX NG [<cite><a class="bibref" href="#bib-RELAXNG">RELAXNG</a></cite>]
and RELAX NG Compact [<cite><a class="bibref" href="#bib-RELAXNG-COMPACT">RELAXNG-COMPACT</a></cite>].</p>
- <div class="note"><div class="note-title" aria-level="3" role="heading" id="h_note_21"><span>Note</span></div><p class="">
+ <div class="note"><div class="note-title" aria-level="3" role="heading" id="h_note_19"><span>Note</span></div><p class="">
The RNGC schema has been updated to attempt to match the grammar but
- this has not been checked or used to validate <abbr title="Resource Description Framework">RDF</abbr>/XML.
+ this has not been checked or used to validate RDF/XML.
</p></div>
<pre> #
@@ -4113,149 +4137,17 @@
</section>
-<!-- THIRTEENTH PART : Changes -->
-
- <section class="appendix informative" id="section-changes" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter">
-
-<!--OddPage-->
-<h2 aria-level="1" role="heading" id="h2_section-changes"><span class="secno">C. </span>Changes</h2><p><em>This section is non-normative.</em></p>
-
- <section id="changes-rdf11" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter">
- <h3 aria-level="2" role="heading" id="h3_changes-rdf11"><span class="secno">C.1 </span>Changes since 2004 Recommendation</h3>
-
- <p>The following changes were made for the Edited
- Recommendation version of this document for <abbr title="Resource Description Framework">RDF</abbr> 1.1.:</p>
- <ul>
- <li>Conversion to ResPec.</li>
- <li>Adapted and shortened introduction to reflect <abbr title="Resource Description Framework">RDF</abbr> 1.1</li>
- <li>Updated references to <abbr title="Resource Description Framework">RDF</abbr> 1.1 documents</li>
- <li>Replaced "(<abbr title="Resource Description Framework">RDF</abbr>) URI reference" with "IRI"</li>
- <li>Removed Section on embedding <abbr title="Resource Description Framework">RDF</abbr>/XML into HTML</li>
- <li>Removed "Specification" from the title to bring it in
- line with other <abbr title="Resource Description Framework">RDF</abbr> 1.1 document titles</li>
- <li>Updated references to other documents</li>
- <li>Changed links in Sec. 2 examples from relative URI to
- absolute URI; same for RELAX schema in Appendix.</li>
- <li>Corrected the resolve action with the signature resolve(e, s)</li>
- <li>Add parent accessor to element events</li>
- <li>Allow datatyped empty literals </li>
- <li>Removed ID and datatype exclusion on literal
- property</li>
- <li>Added note to section on plain-literal event</li>
- <li>Updated link to QName definition in XML-NAMES</li>
- <li>Added diff with 2004 Recommendation</li>
- <li>Adapted <a href="#parseTypeLiteralPropertyElt">Production
- parseTypeLiteralPropertyElt</a> to cater for non-normative
- status of <code>rdf:XMLLiteral</code>.</li>
- <h3 id="generatedID"></h3>
- </ul>
-
- </section>
-
- <section id="changes-2004" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter">
- <h3 aria-level="2" role="heading" id="h3_changes-2004"><span class="secno">C.2 </span>Revisions since Draft 10 October 2003</h3>
-
- <p>Changes since <a href="http://www.w3.org/TR/2003/WD-rdf-syntax-grammar-20031010/">10 October 2003</a> second last call working draft</p>
-
- <p>These are are divided into non-editorial and editorial. The
- non-editorial changes also list consquential editorial changes.
- Editorial changes are those which do not result in any change in the
- meaning of an <abbr title="Resource Description Framework">RDF</abbr> document or the behaviour of an <abbr title="Resource Description Framework">RDF</abbr>
- application.</p>
-
-
-<!-- Non-Editorial Revisions -->
-
- <section id="section-Changes-non-editorial" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter">
- <h4 aria-level="3" role="heading" id="h4_section-Changes-non-editorial"><span class="secno">C.2.1 </span>Non-Editorial Revisions</h4>
-
- <p>None</p>
- </section>
-
-
-<!-- Editorial Revisions -->
-
- <section id="section-Changes-editorial" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter">
- <h4 aria-level="3" role="heading" id="h4_section-Changes-editorial"><span class="secno">C.2.2 </span>Editorial Revisions</h4>
-
- <dl>
- <dt>German Translation</dt>
-
- <dd>
- Fix the German in <a href="#example8">Example 8</a>
- in section <a href="#section-Syntax-languages">2.7</a> after the
- <a href="http://lists.w3.org/Archives/Public/www-rdf-comments/2003OctDec/0215.html">comment
- by Benjamin Nowack
- </a>
- </dd>
-
- <dt>No property attributes on rdf:parseType="Resource"</dt>
- <dd>
- <a href="#section-Syntax-property-attributes">2.5</a>
-
- Update to reflect the syntax definition that property attributes cannot
- be used with <code>rdf:parseType="Resource"</code> as pointed out by
- <a href="http://lists.w3.org/Archives/Public/www-rdf-comments/2003OctDec/0074.html">comment by Sabadello 2003-10-30</a>
- </dd>
-
- <dt>URI Encoding</dt>
- <dd>
- <a href="#section-identifier-node">6.1.6</a>,
- <a href="#section-literal-node">6.1.8</a>,
- <a href="#section-typed-literal-node">6.1.9</a>
-
- after <a href="http://lists.w3.org/Archives/Public/w3c-rdfcore-wg/2003Nov/0006.html">proposal by Jeremy Carroll</a><br />
- <a href="#section-element-node">6.1.2</a>,
- <a href="#section-attribute-node">6.1.4</a>
- Added element/attribute URI-string-value accessors<br />
- <a href="#nodeElement">7.2.11</a>,
- <a href="#emptyPropertyElt">7.2.21</a>
- Added use of new uri event for the <code>rdf:type</code> cases<br />
-
- <a href="#nodeElement">7.2.11</a> (<e.URI> and <a.URI>),
- <a href="#resourcePropertyElt">7.2.15</a> (<e.URI>)
- <a href="#literalPropertyElt">7.2.16</a> (<e.URI>)
-
- <a href="#parseTypeLiteralPropertyElt">7.2.17</a> (<e.URI>)
- <a href="#parseTypeResourcePropertyElt">7.2.18</a> (<e.URI>)
- <a href="#parseTypeCollectionPropertyElt">7.2.19</a> (<e.URI> twice)
- <a href="#emptyPropertyElt">7.2.21</a> (<e.URI> twice, <a.URI> once)
- changed from X.URI to X.URI-string-value (anywhere "<"..">" appeared
- in the grammar action without a hardcoded URI)<br />
-
- <a href="#URI-reference">7.2.32</a>
- Replace action wording with "An <abbr title="Resource Description Framework">RDF</abbr> URI reference"<br />
- All changed as outlined in
- <a href="http://lists.w3.org/Archives/Public/www-rdf-comments/2003OctDec/0100.html">proposal 2003-10-06</a>
- after
- <a href="http://lists.w3.org/Archives/Public/www-rdf-comments/2003OctDec/0068.html">comment by Patel-Schneider 2003-10-29</a>
- </dd>
- </dl>
- </section>
-
-
-<!-- Issues requiring no document revisions -->
-
- <section id="section-Changes-none" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter">
- <h4 aria-level="3" role="heading" id="h4_section-Changes-none"><span class="secno">C.2.3 </span>Issues requiring no document revisions</h4>
-
- <p>None</p>
- </section>
- </section>
- </section>
-
-
<section class="appendix" id="references" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter">
<!--OddPage-->
<h2 aria-level="1" role="heading" id="h2_references"><span class="secno">D. </span>References</h2><section id="normative-references" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter"><h3 aria-level="2" role="heading" id="h3_normative-references"><span class="secno">D.1 </span>Normative references</h3><dl class="bibliography" about=""><dt id="bib-JSON-LD">[JSON-LD]</dt><dd rel="dcterms:requires">Manu Sporny, Gregg Kellogg, Markus Lanthaler, Editors. <cite><a href="http://www.w3.org/TR/2013/PR-json-ld-20131105/">JSON-LD 1.0</a>.</cite> 5 November 2013. W3C Proposed Recommendation. URL: <a href="http://www.w3.org/TR/2013/PR-json-ld-20131105/">http://www.w3.org/TR/2013/PR-json-ld-20131105/</a>. The latest edition is available at <a href="http://www.w3.org/TR/json-ld/">http://www.w3.org/TR/json-ld/</a>
-</dd><dt id="bib-N-TRIPLES">[N-TRIPLES]</dt><dd rel="dcterms:requires">Gavin Carothers, Andy Seabourne. <cite><a href="http://www.w3.org/TR/2013/CR-n-triples-20131105/">RDF 1.1 N-Triples</a></cite>. 5 November 2013. W3C Candidate Recommendation (work in progress). URL: <a href="http://www.w3.org/TR/2013/CR-n-triples-20131105/">http://www.w3.org/TR/2013/CR-n-triples-20131105/</a>. The latest edition is available at <a href="http://www.w3.org/TR/n-triples/">http://www.w3.org/TR/n-triples/</a>
-</dd><dt id="bib-RDF-SCHEMA">[RDF-SCHEMA]</dt><dd rel="dcterms:requires">Dan Brickley; Ramanathan Guha. <a href="http://www.w3.org/TR/rdf-schema"><cite>RDF Vocabulary Description Language 1.0: RDF Schema</cite></a>. 10 February 2004. W3C Recommendation. URL: <a href="http://www.w3.org/TR/rdf-schema">http://www.w3.org/TR/rdf-schema</a>
-</dd><dt id="bib-RDF11-CONCEPTS">[RDF11-CONCEPTS]</dt><dd rel="dcterms:requires">Richard Cyganiak, David Wood, Markus Lanthaler, Editors. <cite><a href="http://www.w3.org/TR/2013/CR-rdf11-concepts-20131105/">RDF 1.1 Concepts and Abstract Syntax.</a></cite> 5 November 2013. W3C Candidate Recommendation (work in progress). URL: <a href="http://www.w3.org/TR/2013/CR-rdf11-concepts-20131105/">http://www.w3.org/TR/2013/CR-rdf11-concepts-20131105/</a>. The latest edition is available at <a href="http://www.w3.org/TR/rdf11-concepts/">http://www.w3.org/TR/rdf11-concepts/</a>
-</dd><dt id="bib-RDF11-MT">[RDF11-MT]</dt><dd rel="dcterms:requires">Patrick J. Hayes, Peter F. Patel-Schneider, Editors. <cite><a href="http://www.w3.org/TR/2013/CR-rdf11-mt-20131105/">RDF 1.1 Semantics.</a></cite> 5 November 2013. W3C Candidate Recommendation (work in progress). URL: <a href="http://www.w3.org/TR/2013/CR-rdf11-mt-20131105/">http://www.w3.org/TR/2013/CR-rdf11-mt-20131105/</a>. The latest edition is available at <a href="http://www.w3.org/TR/rdf11-mt/">http://www.w3.org/TR/rdf11-mt/</a>
+</dd><dt id="bib-N-TRIPLES">[N-TRIPLES]</dt><dd rel="dcterms:requires">Gavin Carothers, Andy Seabourne. <cite><a href="http://www.w3.org/TR/2014/PR-n-triples-20140109/">RDF 1.1 N-Triples</a></cite>. 9 January 2014. W3C Proposed Recommendation (work in progress). URL: <a href="http://www.w3.org/TR/2014/PR-n-triples-20140109/">http://www.w3.org/TR/2014/PR-n-triples-20140109/</a>. The latest edition is available at <a href="http://www.w3.org/TR/n-triples/">http://www.w3.org/TR/n-triples/</a>
+</dd><dt id="bib-RDF11-CONCEPTS">[RDF11-CONCEPTS]</dt><dd rel="dcterms:requires">Richard Cyganiak, David Wood, Markus Lanthaler, Editors. <cite><a href="http://www.w3.org/TR/2014/PR-rdf11-concepts-20140109/">RDF 1.1 Concepts and Abstract Syntax.</a></cite> 9 January 2014. W3C Proposed Recommendation (work in progress). URL: <a href="http://www.w3.org/TR/2014/PR-rdf11-concepts-20140109/">http://www.w3.org/TR/2014/PR-rdf11-concepts-20140109/</a>. The latest edition is available at <a href="http://www.w3.org/TR/rdf11-concepts/">http://www.w3.org/TR/rdf11-concepts/</a>
+</dd><dt id="bib-RDF11-MT">[RDF11-MT]</dt><dd rel="dcterms:requires">Patrick J. Hayes, Peter F. Patel-Schneider, Editors. <cite><a href="http://www.w3.org/TR/2014/PR-rdf11-mt-20140109/">RDF 1.1 Semantics.</a></cite> 9 January 2014. W3C Proposed Recommendation (work in progress). URL: <a href="http://www.w3.org/TR/2014/PR-rdf11-mt-20140109/">http://www.w3.org/TR/2014/PR-rdf11-mt-20140109/</a>. The latest edition is available at <a href="http://www.w3.org/TR/rdf11-mt/">http://www.w3.org/TR/rdf11-mt/</a>
+</dd><dt id="bib-RDF11-SCHEMA">[RDF11-SCHEMA]</dt><dd rel="dcterms:requires">D. Brickley, R. Guha. <cite><a href="http://www.w3.org/TR/2014/PR-rdf-schema-20140109/">RDF Schema 1.1</a></cite>. 9 January 2014. W3C Proposed Edited Recimmendation (work in progress). URL: <a href="http://www.w3.org/TR/2014/PR-rdf-schema-20140109/">http://www.w3.org/TR/2014/PR-rdf-schema-20140109/</a>. The latest published version is available at <a href="http://www.w3.org/TR/rdf-schema/">http://www.w3.org/TR/rdf-schema/</a>.
</dd><dt id="bib-RDFA-PRIMER">[RDFA-PRIMER]</dt><dd rel="dcterms:requires">Ivan Herman; Ben Adida; Manu Sporny; Mark Birbeck. <a href="http://www.w3.org/TR/rdfa-primer/"><cite>RDFa 1.1 Primer - Second Edition</cite></a>. 22 August 2013. W3C Note. URL: <a href="http://www.w3.org/TR/rdfa-primer/">http://www.w3.org/TR/rdfa-primer/</a>
</dd><dt id="bib-RFC3023">[RFC3023]</dt><dd rel="dcterms:requires">M. Murata; S. St.Laurent; D. Kohn. <a href="http://www.ietf.org/rfc/rfc3023.txt"><cite>XML Media Types (RFC 3023)</cite></a>. January 2001. RFC. URL: <a href="http://www.ietf.org/rfc/rfc3023.txt">http://www.ietf.org/rfc/rfc3023.txt</a>
-</dd><dt id="bib-TRIG">[TRIG]</dt><dd rel="dcterms:requires">Gavin Carothers, Andy Seaborne, Editors. <cite><a href="http://www.w3.org/TR/2013/WD-trig-20130919/">TriG: RDF Dataset Language</a></cite>. 19 September 2013. W3C Candidate Recommendation (work in progress). URL: <a href="http://www.w3.org/TR/2013/WD-trig-20130919/">http://www.w3.org/TR/2013/WD-trig-20130919/</a>. The latest edition is available at <a href="http://www.w3.org/TR/trig/">http://www.w3.org/TR/trig/</a>
-</dd><dt id="bib-TURTLE">[TURTLE]</dt><dd rel="dcterms:requires">Eric Prud'hommeaux, Gavin Carothers, Editors. <cite><a href="http://www.w3.org/TR/2013/CR-turtle-20130219/">RDF 1.1 Turtle: Terse RDF Triple Language.</a></cite> 19 February 2013. W3C Candidate Recommendation (work in progress). URL: <a href="http://www.w3.org/TR/2013/CR-turtle-20130219/">http://www.w3.org/TR/2013/CR-turtle-20130219/</a>. The latest edition is available at <a href="http://www.w3.org/TR/turtle/">http://www.w3.org/TR/turtle/</a>
+</dd><dt id="bib-TRIG">[TRIG]</dt><dd rel="dcterms:requires">Gavin Carothers, Andy Seaborne, Editors. <cite><a href="http://www.w3.org/TR/2014/PR-trig-20140109/">TriG: RDF Dataset Language</a></cite>. 9 January 2014. W3C Proposed Recommendation (work in progress). URL: <a href="http://www.w3.org/TR/2014/PR-trig-20140109/">http://www.w3.org/TR/2014/PR-trig-20140109/</a>. The latest edition is available at <a href="http://www.w3.org/TR/trig/">http://www.w3.org/TR/trig/</a>
+</dd><dt id="bib-TURTLE">[TURTLE]</dt><dd rel="dcterms:requires">Eric Prud'hommeaux, Gavin Carothers, Editors. <cite><a href="http://www.w3.org/TR/2014/PR-turtle-20140109/">RDF 1.1 Turtle: Terse RDF Triple Language.</a></cite> 9 January 2014. W3C Proposed Recommendation (work in progress). URL: <a href="http://www.w3.org/TR/2014/PR-turtle-20140109/">http://www.w3.org/TR/2014/PR-turtle-20140109/</a>. The latest edition is available at <a href="http://www.w3.org/TR/turtle/">http://www.w3.org/TR/turtle/</a>
</dd><dt id="bib-XML-INFOSET">[XML-INFOSET]</dt><dd rel="dcterms:requires">John Cowan; Richard Tobin. <a href="http://www.w3.org/TR/xml-infoset"><cite>XML Information Set (Second Edition)</cite></a>. 4 February 2004. W3C Recommendation. URL: <a href="http://www.w3.org/TR/xml-infoset">http://www.w3.org/TR/xml-infoset</a>
</dd><dt id="bib-XML-NAMES">[XML-NAMES]</dt><dd rel="dcterms:requires">Tim Bray; Dave Hollander; Andrew Layman; Richard Tobin; Henry Thompson et al. <a href="http://www.w3.org/TR/xml-names"><cite>Namespaces in XML 1.0 (Third Edition)</cite></a>. 8 December 2009. W3C Recommendation. URL: <a href="http://www.w3.org/TR/xml-names">http://www.w3.org/TR/xml-names</a>
</dd><dt id="bib-XML10">[XML10]</dt><dd rel="dcterms:requires">Tim Bray; Jean Paoli; Michael Sperberg-McQueen; Eve Maler; François Yergeau et al. <a href="http://www.w3.org/TR/xml"><cite>Extensible Markup Language (XML) 1.0 (Fifth Edition)</cite></a>. 26 November 2008. W3C Recommendation. URL: <a href="http://www.w3.org/TR/xml">http://www.w3.org/TR/xml</a>
@@ -4276,4 +4168,6 @@
</dd><dt id="bib-XMLBASE">[XMLBASE]</dt><dd rel="dcterms:references">Jonathan Marsh; Richard Tobin. <a href="http://www.w3.org/TR/xmlbase/"><cite>XML Base (Second Edition)</cite></a>. 28 January 2009. W3C Recommendation. URL: <a href="http://www.w3.org/TR/xmlbase/">http://www.w3.org/TR/xmlbase/</a>
</dd><dt id="bib-XMLSCHEMA-1">[XMLSCHEMA-1]</dt><dd rel="dcterms:references">Henry Thompson; David Beech; Murray Maloney; Noah Mendelsohn et al. <a href="http://www.w3.org/TR/xmlschema-1/"><cite>XML Schema Part 1: Structures Second Edition</cite></a>. 28 October 2004. W3C Recommendation. URL: <a href="http://www.w3.org/TR/xmlschema-1/">http://www.w3.org/TR/xmlschema-1/</a>
</dd><dt id="bib-XPATH">[XPATH]</dt><dd rel="dcterms:references">James Clark; Steven DeRose. <a href="http://www.w3.org/TR/xpath"><cite>XML Path Language (XPath) Version 1.0</cite></a>. 16 November 1999. W3C Recommendation. URL: <a href="http://www.w3.org/TR/xpath">http://www.w3.org/TR/xpath</a>
+</dd><dt id="bib-XPATH-DATAMODEL-30">[XPATH-DATAMODEL-30]</dt><dd rel="dcterms:references">Norman Walsh; Anders Berglund; John Snelson. <a href="http://www.w3.org/TR/xpath-datamodel-30/"><cite>XQuery and XPath Data Model 3.0</cite></a>. 22 October 2013. W3C Proposed Recommendation. URL: <a href="http://www.w3.org/TR/xpath-datamodel-30/">http://www.w3.org/TR/xpath-datamodel-30/</a>
+</dd><dt id="bib-XPATH-FUNCTIONS-30">[XPATH-FUNCTIONS-30]</dt><dd rel="dcterms:references">Michael Kay. <a href="http://www.w3.org/TR/xpath-functions-30/"><cite>XPath and XQuery Functions and Operators 3.0</cite></a>. 22 October 2013. W3C Proposed Recommendation. URL: <a href="http://www.w3.org/TR/xpath-functions-30/">http://www.w3.org/TR/xpath-functions-30/</a>
</dd></dl></section></section></body></html>
\ No newline at end of file