--- a/rdf-concepts/index.html Tue May 29 22:44:41 2012 +0100
+++ b/rdf-concepts/index.html Tue May 29 22:53:41 2012 +0100
@@ -1,126 +1,496 @@
-<!DOCTYPE html>
-<html lang="en">
- <head>
- <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01+RDFa 1.1//EN"
+ "http://www.w3.org/MarkUp/DTD/html401-rdfa11-1.dtd">
+<html lang="en" dir="ltr" about="" property="dcterms:language" content="en" prefix="dcterms: http://purl.org/dc/terms/ bibo: http://purl.org/ontology/bibo/ foaf: http://xmlns.com/foaf/0.1/ xsd: http://www.w3.org/2001/XMLSchema#">
+<head>
+ <meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<title>RDF 1.1 Concepts and Abstract Syntax</title>
<style type="text/css">
.figure { text-align: center; }
.figure a[href]:hover { background: transparent; }
table td, table th { border: 1px solid #ddd; padding: 0.2em 0.5em; }
</style>
- <script src='../ReSpec.js/js/respec.js' class='remove'></script>
- <script class='remove'>
- var respecConfig = {
- // specification status (e.g. WD, LCWD, NOTE, etc.). If in doubt use ED.
- specStatus: "WD",
-
- // the specification's short name, as in http://www.w3.org/TR/short-name/
- shortName: "rdf11-concepts",
-
- // if your specification has a subtitle that goes below the main
- // formal title, define it here
- // subtitle : "an excellent document",
-
- // if you wish the publication date to be other than today, set this
- publishDate: "2012-06-05",
-
- // if the specification's copyright date is a range of years, specify
- // the start date here:
- copyrightStart: "2004",
-
- // if there is a previously published draft, uncomment this and set its YYYY-MM-DD date
- // and its maturity status
- previousPublishDate: "2011-08-30",
- previousMaturity: "WD",
-
- // if there a publicly available Editor's Draft, this is the link
- edDraftURI: "http://dvcs.w3.org/hg/rdf/raw-file/default/rdf-concepts/index.html",
-
- // if this is a LCWD, uncomment and set the end of its review period
- // lcEnd: "2009-08-05",
-
- // if there is an earler version of this specification at the Recommendation level,
- // set this to the shortname of that version. This is optional and not usually
- // necessary.
- prevRecShortname: "rdf-concepts",
-
- // if you want to have extra CSS, append them to this list
- // it is recommended that the respec.css stylesheet be kept
- extraCSS: ["http://dvcs.w3.org/hg/rdf/raw-file/default/ReSpec.js/css/respec.css"],
+
+
+ <style type="text/css">
+/*****************************************************************
+ * ReSpec CSS
+ * Robin Berjon (robin at berjon dot com)
+ * v0.05 - 2009-07-31
+ *****************************************************************/
- // editors, add as many as you like
- // only "name" is required
- editors: [
- { name: "Richard Cyganiak", url: "http://richard.cyganiak.de/",
- company: "DERI, NUI Galway", companyURL: "http://www.deri.ie/",
- },
- { name: "David Wood", // url: "http://example.org/",
- company: "3 Round Stones", companyURL:
- "http://www.3roundstones.com/",
- },
- ],
- otherContributors: {
- "Previous editor": [
- { name: "Graham Klyne",
- //url: "http://www.ninebynine.org/",
- company: "Nine by Nine",
- //companyURL: "http://example.com/"
- //mailto: "GK@NineByNine.org",
- },
- { name: "Jeremy J. Carroll",
- //url: "http://www-uk.hpl.hp.com/people/jjc/",
- company: "Hewlett Packard Labs",
- //companyURL: "http://example.com/"
- //mailto: "jjc@hpl.hp.com",
- },
- { name: "Brian McBride",
- //url: "http://www-uk.hpl.hp.com/people/bwm/",
- company: "Hewlett Packard Labs",
- //companyURL: "http://example.com/"
- //mailto: "bwm@hplb.hpl.hp.com",
- note: "RDF 2004 Series Editor",
- },
- ],
- },
- // authors, add as many as you like.
- // This is optional, uncomment if you have authors as well as editors.
- // only "name" is required. Same format as editors.
+/* --- INLINES --- */
+em.rfc2119 {
+ text-transform: lowercase;
+ font-variant: small-caps;
+ font-style: normal;
+ color: #900;
+}
- //authors: [
- // { name: "Your Name", url: "http://example.org/",
- // company: "Your Company", companyURL: "http://example.com/" },
- //],
-
- // name of the WG
- wg: "RDF Working Group",
-
- // URI of the public WG page
- wgURI: "http://www.w3.org/2011/rdf-wg/",
-
- // name (with the @w3c.org) of the public mailing to which comments are due
- wgPublicList: "public-rdf-comments",
-
- // URI of the patent status for this WG, for Rec-track documents
- // !!!! IMPORTANT !!!!
- // This is important for Rec-track documents, do not copy a patent URI from a random
- // document unless you know what you're doing. If in doubt ask your friendly neighbourhood
- // Team Contact.
- wgPatentURI: "http://www.w3.org/2004/01/pp-impl/46168/status",
+h1 acronym, h2 acronym, h3 acronym, h4 acronym, h5 acronym, h6 acronym, a acronym,
+h1 abbr, h2 abbr, h3 abbr, h4 abbr, h5 abbr, h6 abbr, a abbr {
+ border: none;
+}
- // if this parameter is set to true, ReSpec.js will embed various RDFa attributes
- // throughout the generated specification. The triples generated use vocabulary items
- // from the dcterms, foaf, and bibo. The parameter defaults to false.
- doRDFa: true,
- };
+dfn {
+ font-weight: bold;
+}
-// @@@ A number of references have been patched into the local berjon.biblio and need to be added to the global biblio in CVS:
- </script>
- </head>
+a.internalDFN {
+ color: inherit;
+ border-bottom: 1px solid #99c;
+ text-decoration: none;
+}
- <body>
+a.externalDFN {
+ color: inherit;
+ border-bottom: medium dotted #ccc;
+ text-decoration: none;
+}
-<section id="abstract">
+a.bibref {
+ text-decoration: none;
+}
+
+code {
+ color: #ff4500;
+}
+
+
+/* --- WEB IDL --- */
+pre.idl {
+ border-top: 1px solid #90b8de;
+ border-bottom: 1px solid #90b8de;
+ padding: 1em;
+ line-height: 120%;
+}
+
+pre.idl::before {
+ content: "WebIDL";
+ display: block;
+ width: 150px;
+ background: #90b8de;
+ color: #fff;
+ font-family: initial;
+ padding: 3px;
+ font-weight: bold;
+ margin: -1em 0 1em -1em;
+}
+
+.idlType {
+ color: #ff4500;
+ font-weight: bold;
+ text-decoration: none;
+}
+
+/*.idlModule*/
+/*.idlModuleID*/
+/*.idlInterface*/
+.idlInterfaceID {
+ font-weight: bold;
+ color: #005a9c;
+}
+
+.idlSuperclass {
+ font-style: italic;
+ color: #005a9c;
+}
+
+/*.idlAttribute*/
+.idlAttrType, .idlFieldType {
+ color: #005a9c;
+}
+.idlAttrName, .idlFieldName {
+ color: #ff4500;
+}
+.idlAttrName a, .idlFieldName a {
+ color: #ff4500;
+ border-bottom: 1px dotted #ff4500;
+ text-decoration: none;
+}
+
+/*.idlMethod*/
+.idlMethType {
+ color: #005a9c;
+}
+.idlMethName {
+ color: #ff4500;
+}
+.idlMethName a {
+ color: #ff4500;
+ border-bottom: 1px dotted #ff4500;
+ text-decoration: none;
+}
+
+/*.idlParam*/
+.idlParamType {
+ color: #005a9c;
+}
+.idlParamName {
+ font-style: italic;
+}
+
+.extAttr {
+ color: #666;
+}
+
+/*.idlConst*/
+.idlConstType {
+ color: #005a9c;
+}
+.idlConstName {
+ color: #ff4500;
+}
+.idlConstName a {
+ color: #ff4500;
+ border-bottom: 1px dotted #ff4500;
+ text-decoration: none;
+}
+
+/*.idlException*/
+.idlExceptionID {
+ font-weight: bold;
+ color: #c00;
+}
+
+.idlTypedefID, .idlTypedefType {
+ color: #005a9c;
+}
+
+.idlRaises, .idlRaises a.idlType, .idlRaises a.idlType code, .excName a, .excName a code {
+ color: #c00;
+ font-weight: normal;
+}
+
+.excName a {
+ font-family: monospace;
+}
+
+.idlRaises a.idlType, .excName a.idlType {
+ border-bottom: 1px dotted #c00;
+}
+
+.excGetSetTrue, .excGetSetFalse, .prmNullTrue, .prmNullFalse, .prmOptTrue, .prmOptFalse {
+ width: 45px;
+ text-align: center;
+}
+.excGetSetTrue, .prmNullTrue, .prmOptTrue { color: #0c0; }
+.excGetSetFalse, .prmNullFalse, .prmOptFalse { color: #c00; }
+
+.idlImplements a {
+ font-weight: bold;
+}
+
+dl.attributes, dl.methods, dl.constants, dl.fields {
+ margin-left: 2em;
+}
+
+.attributes dt, .methods dt, .constants dt, .fields dt {
+ font-weight: normal;
+}
+
+.attributes dt code, .methods dt code, .constants dt code, .fields dt code {
+ font-weight: bold;
+ color: #000;
+ font-family: monospace;
+}
+
+.attributes dt code, .fields dt code {
+ background: #ffffd2;
+}
+
+.attributes dt .idlAttrType code, .fields dt .idlFieldType code {
+ color: #005a9c;
+ background: transparent;
+ font-family: inherit;
+ font-weight: normal;
+ font-style: italic;
+}
+
+.methods dt code {
+ background: #d9e6f8;
+}
+
+.constants dt code {
+ background: #ddffd2;
+}
+
+.attributes dd, .methods dd, .constants dd, .fields dd {
+ margin-bottom: 1em;
+}
+
+table.parameters, table.exceptions {
+ border-spacing: 0;
+ border-collapse: collapse;
+ margin: 0.5em 0;
+ width: 100%;
+}
+table.parameters { border-bottom: 1px solid #90b8de; }
+table.exceptions { border-bottom: 1px solid #deb890; }
+
+.parameters th, .exceptions th {
+ color: #fff;
+ padding: 3px 5px;
+ text-align: left;
+ font-family: initial;
+ font-weight: normal;
+ text-shadow: #666 1px 1px 0;
+}
+.parameters th { background: #90b8de; }
+.exceptions th { background: #deb890; }
+
+.parameters td, .exceptions td {
+ padding: 3px 10px;
+ border-top: 1px solid #ddd;
+ vertical-align: top;
+}
+
+.parameters tr:first-child td, .exceptions tr:first-child td {
+ border-top: none;
+}
+
+.parameters td.prmName, .exceptions td.excName, .exceptions td.excCodeName {
+ width: 100px;
+}
+
+.parameters td.prmType {
+ width: 120px;
+}
+
+table.exceptions table {
+ border-spacing: 0;
+ border-collapse: collapse;
+ width: 100%;
+}
+
+/* --- TOC --- */
+.toc a {
+ text-decoration: none;
+}
+
+a .secno {
+ color: #000;
+}
+
+/* --- TABLE --- */
+table.simple {
+ border-spacing: 0;
+ border-collapse: collapse;
+ border-bottom: 3px solid #005a9c;
+}
+
+.simple th {
+ background: #005a9c;
+ color: #fff;
+ padding: 3px 5px;
+ text-align: left;
+}
+
+.simple th[scope="row"] {
+ background: inherit;
+ color: inherit;
+ border-top: 1px solid #ddd;
+}
+
+.simple td {
+ padding: 3px 10px;
+ border-top: 1px solid #ddd;
+}
+
+.simple tr:nth-child(even) {
+ background: #f0f6ff;
+}
+
+/* --- DL --- */
+.section dd > p:first-child {
+ margin-top: 0;
+}
+
+.section dd > p:last-child {
+ margin-bottom: 0;
+}
+
+.section dd {
+ margin-bottom: 1em;
+}
+
+.section dl.attrs dd, .section dl.eldef dd {
+ margin-bottom: 0;
+}
+
+/* --- EXAMPLES --- */
+pre.example {
+ border-top: 1px solid #ff4500;
+ border-bottom: 1px solid #ff4500;
+ padding: 1em;
+ margin-top: 1em;
+}
+
+pre.example::before {
+ content: "Example";
+ display: block;
+ width: 150px;
+ background: #ff4500;
+ color: #fff;
+ font-family: initial;
+ padding: 3px;
+ font-weight: bold;
+ margin: -1em 0 1em -1em;
+}
+
+/* --- EDITORIAL NOTES --- */
+.issue {
+ padding: 1em;
+ margin: 1em 0em 0em;
+ border: 1px solid #f00;
+ background: #ffc;
+}
+
+.issue::before {
+ content: "Issue";
+ display: block;
+ width: 150px;
+ margin: -1.5em 0 0.5em 0;
+ font-weight: bold;
+ border: 1px solid #f00;
+ background: #fff;
+ padding: 3px 1em;
+}
+
+.note {
+ margin: 1em 0em 0em;
+ padding: 1em;
+ border: 2px solid #cff6d9;
+ background: #e2fff0;
+}
+
+.note::before {
+ content: "Note";
+ display: block;
+ width: 150px;
+ margin: -1.5em 0 0.5em 0;
+ font-weight: bold;
+ border: 1px solid #cff6d9;
+ background: #fff;
+ padding: 3px 1em;
+}
+
+/* --- Best Practices --- */
+div.practice {
+ border: solid #bebebe 1px;
+ margin: 2em 1em 1em 2em;
+}
+
+span.practicelab {
+ margin: 1.5em 0.5em 1em 1em;
+ font-weight: bold;
+ font-style: italic;
+}
+
+span.practicelab { background: #dfffff; }
+
+span.practicelab {
+ position: relative;
+ padding: 0 0.5em;
+ top: -1.5em;
+}
+
+p.practicedesc {
+ margin: 1.5em 0.5em 1em 1em;
+}
+
+@media screen {
+ p.practicedesc {
+ position: relative;
+ top: -2em;
+ padding: 0;
+ margin: 1.5em 0.5em -1em 1em;
+ }
+}
+
+/* --- SYNTAX HIGHLIGHTING --- */
+pre.sh_sourceCode {
+ background-color: white;
+ color: black;
+ font-style: normal;
+ font-weight: normal;
+}
+
+pre.sh_sourceCode .sh_keyword { color: #005a9c; font-weight: bold; } /* language keywords */
+pre.sh_sourceCode .sh_type { color: #666; } /* basic types */
+pre.sh_sourceCode .sh_usertype { color: teal; } /* user defined types */
+pre.sh_sourceCode .sh_string { color: red; font-family: monospace; } /* strings and chars */
+pre.sh_sourceCode .sh_regexp { color: orange; font-family: monospace; } /* regular expressions */
+pre.sh_sourceCode .sh_specialchar { color: #ffc0cb; font-family: monospace; } /* e.g., \n, \t, \\ */
+pre.sh_sourceCode .sh_comment { color: #A52A2A; font-style: italic; } /* comments */
+pre.sh_sourceCode .sh_number { color: purple; } /* literal numbers */
+pre.sh_sourceCode .sh_preproc { color: #00008B; font-weight: bold; } /* e.g., #include, import */
+pre.sh_sourceCode .sh_symbol { color: blue; } /* e.g., *, + */
+pre.sh_sourceCode .sh_function { color: black; font-weight: bold; } /* function calls and declarations */
+pre.sh_sourceCode .sh_cbracket { color: red; } /* block brackets (e.g., {, }) */
+pre.sh_sourceCode .sh_todo { font-weight: bold; background-color: #00FFFF; } /* TODO and FIXME */
+
+/* Predefined variables and functions (for instance glsl) */
+pre.sh_sourceCode .sh_predef_var { color: #00008B; }
+pre.sh_sourceCode .sh_predef_func { color: #00008B; font-weight: bold; }
+
+/* for OOP */
+pre.sh_sourceCode .sh_classname { color: teal; }
+
+/* line numbers (not yet implemented) */
+pre.sh_sourceCode .sh_linenum { display: none; }
+
+/* Internet related */
+pre.sh_sourceCode .sh_url { color: blue; text-decoration: underline; font-family: monospace; }
+
+/* for ChangeLog and Log files */
+pre.sh_sourceCode .sh_date { color: blue; font-weight: bold; }
+pre.sh_sourceCode .sh_time, pre.sh_sourceCode .sh_file { color: #00008B; font-weight: bold; }
+pre.sh_sourceCode .sh_ip, pre.sh_sourceCode .sh_name { color: #006400; }
+
+/* for Prolog, Perl... */
+pre.sh_sourceCode .sh_variable { color: #006400; }
+
+/* for LaTeX */
+pre.sh_sourceCode .sh_italics { color: #006400; font-style: italic; }
+pre.sh_sourceCode .sh_bold { color: #006400; font-weight: bold; }
+pre.sh_sourceCode .sh_underline { color: #006400; text-decoration: underline; }
+pre.sh_sourceCode .sh_fixed { color: green; font-family: monospace; }
+pre.sh_sourceCode .sh_argument { color: #006400; }
+pre.sh_sourceCode .sh_optionalargument { color: purple; }
+pre.sh_sourceCode .sh_math { color: orange; }
+pre.sh_sourceCode .sh_bibtex { color: blue; }
+
+/* for diffs */
+pre.sh_sourceCode .sh_oldfile { color: orange; }
+pre.sh_sourceCode .sh_newfile { color: #006400; }
+pre.sh_sourceCode .sh_difflines { color: blue; }
+
+/* for css */
+pre.sh_sourceCode .sh_selector { color: purple; }
+pre.sh_sourceCode .sh_property { color: blue; }
+pre.sh_sourceCode .sh_value { color: #006400; font-style: italic; }
+
+/* other */
+pre.sh_sourceCode .sh_section { color: black; font-weight: bold; }
+pre.sh_sourceCode .sh_paren { color: red; }
+pre.sh_sourceCode .sh_attribute { color: #006400; }
+
+</style><link href="http://www.w3.org/StyleSheets/TR/W3C-WD" rel="stylesheet" type="text/css" charset="utf-8"></head>
+
+ <body style="display: inherit; "><div class="head"><p><a href="http://www.w3.org/"><img width="72" height="48" src="http://www.w3.org/Icons/w3c_home" alt="W3C"></a></p><h1 property="dcterms:title" class="title" id="title">RDF 1.1 Concepts and Abstract Syntax</h1><h2 property="dcterms:issued" datatype="xsd:dateTime" content="2012-06-04T23:00:00+0000" id="w3c-working-draft-05-june-2012">W3C Working Draft 05 June 2012</h2><dl><dt>This version:</dt><dd><a href="http://www.w3.org/TR/2012/WD-rdf11-concepts-20120605/">http://www.w3.org/TR/2012/WD-rdf11-concepts-20120605/</a></dd><dt>Latest published version:</dt><dd><a href="http://www.w3.org/TR/rdf11-concepts/">http://www.w3.org/TR/rdf11-concepts/</a></dd><dt>Latest editor's draft:</dt><dd><a href="http://dvcs.w3.org/hg/rdf/raw-file/default/rdf-concepts/index.html">http://dvcs.w3.org/hg/rdf/raw-file/default/rdf-concepts/index.html</a></dd><dt>Previous version:</dt><dd><a rel="dcterms:replaces" href="http://www.w3.org/TR/2011/WD-rdf11-concepts-20110830/">http://www.w3.org/TR/2011/WD-rdf11-concepts-20110830/</a></dd><dt>Latest recommendation:</dt><dd><a href="http://www.w3.org/TR/rdf-concepts/">http://www.w3.org/TR/rdf-concepts/</a></dd><dt>Editors:</dt><dd rel="bibo:editor"><span typeof="foaf:Person"><a rel="foaf:homepage" property="foaf:name" content="Richard Cyganiak" href="http://richard.cyganiak.de/">Richard Cyganiak</a>, <a rel="foaf:workplaceHomepage" href="http://www.deri.ie/">DERI, NUI Galway</a></span>
+</dd>
+<dd rel="bibo:editor"><span typeof="foaf:Person"><span property="foaf:name">David Wood</span>, <a rel="foaf:workplaceHomepage" href="http://www.3roundstones.com/">3 Round Stones</a></span>
+</dd>
+<dt>Previous editors:</dt><dd><span><span>Graham Klyne</span>, Nine by Nine</span>
+</dd>
+<dd><span><span>Jeremy J. Carroll</span>, Hewlett Packard Labs</span>
+</dd>
+<dd><span><span>Brian McBride</span>, Hewlett Packard Labs (RDF 2004 Series Editor)</span>
+</dd>
+</dl><p class="copyright"><a rel="license" href="http://www.w3.org/Consortium/Legal/ipr-notice#Copyright">Copyright</a> © 2004-2012 <span rel="dcterms:publisher"><span typeof="foaf:Organization"><a rel="foaf:homepage" property="foaf:name" content="World Wide Web Consotrium" href="http://www.w3.org/"><acronym title="World Wide Web Consortium">W3C</acronym></a><sup>®</sup></span></span> (<a href="http://www.csail.mit.edu/"><acronym title="Massachusetts Institute of Technology">MIT</acronym></a>, <a href="http://www.ercim.eu/"><acronym title="European Research Consortium for Informatics and Mathematics">ERCIM</acronym></a>, <a href="http://www.keio.ac.jp/">Keio</a>), All Rights Reserved. W3C <a href="http://www.w3.org/Consortium/Legal/ipr-notice#Legal_Disclaimer">liability</a>, <a href="http://www.w3.org/Consortium/Legal/ipr-notice#W3C_Trademarks">trademark</a> and <a href="http://www.w3.org/Consortium/Legal/copyright-documents">document use</a> rules apply.</p><hr></div>
+
+<div id="abstract" class="introductory section" property="dcterms:abstract" datatype="" typeof="bibo:Chapter" about="#abstract"><h2>Abstract</h2>
<p>The Resource Description Framework (RDF) is a framework for
representing information in the Web.</p>
<p>RDF Concepts and Abstract Syntax defines an abstract syntax
@@ -128,10 +498,7 @@
syntax to its formal semantics. It also includes discussion of
key concepts, datatyping, character normalization
and handling of IRIs.</p>
-</section>
-
-
-<section id='sotd'>
+</div><div id="sotd" class="introductory section" typeof="bibo:Chapter" about="#sotd"><h2>Status of This Document</h2><p><em>This section describes the status of this document at the time of its publication. Other documents may supersede this document. A list of current W3C publications and the latest revision of this technical report can be found in the <a href="http://www.w3.org/TR/">W3C technical reports index</a> at http://www.w3.org/TR/.</em></p>
<p>This document is a snapshot of the
<a href="http://www.w3.org/2011/rdf-wg/">RDF Working Group</a>'s
progress towards updating the RDF data model for RDF 1.1.
@@ -140,8 +507,8 @@
is provided as an appendix. Notable highlights include:</p>
<ul>
- <li>Introduced a datatype for <a title="language-tagged string">language-tagged strings</a>, and <a href="#section-html">one for HTML fragments</a></li>
- <li>Modified the lexical space and value space of the <code><a>rdf:XMLLiteral</a></code> datatype</li>
+ <li>Introduced a datatype for <a title="language-tagged string" href="#dfn-language-tagged-string" class="internalDFN">language-tagged strings</a>, and <a href="#section-html">one for HTML fragments</a></li>
+ <li>Modified the lexical space and value space of the <code><a href="#dfn-rdf-xmlliteral" class="internalDFN">rdf:XMLLiteral</a></code> datatype</li>
<li>Updated the list of <a href="#xsd-datatypes">RDF-compatible XSD types</a> to reflect XML Schema 1.1</li>
<li>Added a <a href="#conformance">Conformance section</a></li>
<li>Replaced the informative early sections with a <a href="#section-Introduction">new Introduction</a></li>
@@ -153,11 +520,14 @@
Besides that, some content may still be moved between
this and other RDF documents, and various editorial changes
under consideration are highlighted throughout the document.</p>
-</section>
+<p>This document was published by the <a href="http://www.w3.org/2011/rdf-wg/">RDF Working Group</a> as a Working Draft. This document is intended to become a W3C Recommendation. If you wish to make comments regarding this document, please send them to <a href="mailto:public-rdf-comments@w3.org">public-rdf-comments@w3.org</a> (<a href="mailto:public-rdf-comments-request@w3.org?subject=subscribe">subscribe</a>, <a href="http://lists.w3.org/Archives/Public/public-rdf-comments/">archives</a>). All feedback is welcome.</p><p>Publication as a Working Draft does not imply endorsement by the W3C Membership. This is a draft document and may be updated, replaced or obsoleted by other documents at any time. It is inappropriate to cite this document as other than work in progress.</p><p>This document was produced by a group operating under the <a href="http://www.w3.org/Consortium/Patent-Policy-20040205/">5 February 2004 W3C Patent Policy</a>. W3C maintains a <a href="http://www.w3.org/2004/01/pp-impl/46168/status" rel="disclosure">public list of any patent disclosures</a> made in connection with the deliverables of the group; that page also includes instructions for disclosing a patent. An individual who has actual knowledge of a patent which the individual believes contains <a href="http://www.w3.org/Consortium/Patent-Policy-20040205/#def-essential">Essential Claim(s)</a> must disclose the information in accordance with <a href="http://www.w3.org/Consortium/Patent-Policy-20040205/#sec-Disclosure">section 6 of the W3C Patent Policy</a>.</p></div><div id="toc" typeof="bibo:Chapter" about="#toc" class="section"><h2 class="introductory">Table of Contents</h2><ul class="toc"><li class="tocline"><a href="#section-Introduction" class="tocxref"><span class="secno">1 </span>Introduction</a><ul class="toc"><li class="tocline"><a href="#data-model" class="tocxref"><span class="secno">1.1 </span>Graph-based Data Model</a></li><li class="tocline"><a href="#resources-and-statements" class="tocxref"><span class="secno">1.2 </span>Resources and Statements</a></li><li class="tocline"><a href="#referents" class="tocxref"><span class="secno">1.3 </span>The Referent of an IRI</a></li><li class="tocline"><a href="#vocabularies" class="tocxref"><span class="secno">1.4 </span>RDF Vocabularies and Namespace IRIs</a></li><li class="tocline"><a href="#entailment" class="tocxref"><span class="secno">1.5 </span>Formal Meaning and Entailment</a></li><li class="tocline"><a href="#managing-graphs" class="tocxref"><span class="secno">1.6 </span>Merging and Managing RDF Graphs</a></li></ul></li><li class="tocline"><a href="#conformance" class="tocxref"><span class="secno">2 </span>Conformance</a></li><li class="tocline"><a href="#section-rdf-graph" class="tocxref"><span class="secno">3 </span>RDF Graphs</a><ul class="toc"><li class="tocline"><a href="#section-triples" class="tocxref"><span class="secno">3.1 </span>Triples</a></li><li class="tocline"><a href="#section-IRIs" class="tocxref"><span class="secno">3.2 </span>IRIs</a></li><li class="tocline"><a href="#section-Graph-Literal" class="tocxref"><span class="secno">3.3 </span>Literals</a></li><li class="tocline"><a href="#section-blank-nodes" class="tocxref"><span class="secno">3.4 </span>Blank Nodes</a></li><li class="tocline"><a href="#section-skolemization" class="tocxref"><span class="secno">3.5 </span>Replacing Blank Nodes with IRIs</a></li></ul></li><li class="tocline"><a href="#section-dataset" class="tocxref"><span class="secno">4 </span>RDF Datasets</a></li><li class="tocline"><a href="#section-Datatypes" class="tocxref"><span class="secno">5 </span>Datatypes</a><ul class="toc"><li class="tocline"><a href="#xsd-datatypes" class="tocxref"><span class="secno">5.1 </span>The XML Schema Built-in Datatypes</a></li><li class="tocline"><a href="#section-html" class="tocxref"><span class="secno">5.2 </span>The <code>rdf:HTML</code> Datatype</a></li><li class="tocline"><a href="#section-XMLLiteral" class="tocxref"><span class="secno">5.3 </span>The <code>rdf:XMLLiteral</code> Datatype</a></li><li class="tocline"><a href="#datatype-maps" class="tocxref"><span class="secno">5.4 </span>Datatype Maps</a></li><li class="tocline"><a href="#section-Literal-Value" class="tocxref"><span class="secno">5.5 </span>The Value Corresponding to a Literal</a></li></ul></li><li class="tocline"><a href="#section-fragID" class="tocxref"><span class="secno">6 </span>Fragment Identifiers</a></li><li class="tocline"><a href="#section-Acknowledgments" class="tocxref"><span class="secno">7 </span>Acknowledgments</a></li><li class="tocline"><a href="#changes" class="tocxref"><span class="secno">A </span>Changes from RDF 2004</a><ul class="toc"><li class="tocline"><a href="#changes-wd2" class="tocxref"><span class="secno">A.1 </span>Changes from FPWD to this version</a></li><li class="tocline"><a href="#changes-fpwd" class="tocxref"><span class="secno">A.2 </span>Changes from RDF 2004 to FPWD</a></li></ul></li><li class="tocline"><a href="#references" class="tocxref"><span class="secno">B </span>References</a><ul class="toc"><li class="tocline"><a href="#normative-references" class="tocxref"><span class="secno">B.1 </span>Normative references</a></li><li class="tocline"><a href="#informative-references" class="tocxref"><span class="secno">B.2 </span>Informative references</a></li></ul></li></ul></div>
-<section id="section-Introduction" class="informative">
- <h2>Introduction</h2>
+
+
+
+<div id="section-Introduction" class="informative section" typeof="bibo:Chapter" about="#section-Introduction">
+ <h2><span class="secno">1 </span>Introduction</h2><p><em>This section is non-normative.</em></p>
<p>The <em>Resource Description Framework</em> (RDF) is a framework
for representing information in the Web.</p>
@@ -168,115 +538,115 @@
<ul>
<li>Serialization syntaxes for storing and exchanging RDF
- (e.g., <a href="http://www.w3.org/TR/turtle/">Turtle</a> [[TURTLE-TR]]
+ (e.g., <a href="http://www.w3.org/TR/turtle/">Turtle</a> [<cite><a class="bibref" rel="biblioentry" href="#bib-TURTLE-TR">TURTLE-TR</a></cite>]
and <a href="http://www.w3.org/TR/REC-rdf-syntax/">RDF/XML</a>
- [[RDF-SYNTAX-GRAMMAR]]),</li>
+ [<cite><a class="bibref" rel="biblioentry" href="#bib-RDF-SYNTAX-GRAMMAR">RDF-SYNTAX-GRAMMAR</a></cite>]),</li>
<li>the <a href="http://www.w3.org/TR/rdf-sparql-query/">SPARQL
- Query Language</a> [[RDF-SPARQL-QUERY]],</li>
+ Query Language</a> [<cite><a class="bibref" rel="biblioentry" href="#bib-RDF-SPARQL-QUERY">RDF-SPARQL-QUERY</a></cite>],</li>
<li>the <a href="http://www.w3.org/TR/rdf-schema/">RDF Vocabulary
- Description Language</a> [[RDF-SCHEMA]],</li>
+ Description Language</a> [<cite><a class="bibref" rel="biblioentry" href="#bib-RDF-SCHEMA">RDF-SCHEMA</a></cite>],</li>
<li>a <a href="http://www.w3.org/TR/rdf-mt/">formal
- model-theoretic semantics for RDF</a> [[RDF-MT]].</li>
+ model-theoretic semantics for RDF</a> [<cite><a class="bibref" rel="biblioentry" href="#bib-RDF-MT">RDF-MT</a></cite>].</li>
</ul>
-<section id="data-model">
- <h3>Graph-based Data Model</h3>
+<div id="data-model" typeof="bibo:Chapter" about="#data-model" class="section">
+ <h3><span class="secno">1.1 </span>Graph-based Data Model</h3>
<p>The core structure of the abstract syntax is a collection of
- <a title="RDF triple">triples</a>, each consisting of a <a>subject</a>,
- a <a>predicate</a> and an <a>object</a>. A set of such triples is called
- an <a>RDF graph</a>. This can be illustrated by a node and
+ <a title="RDF triple" href="#dfn-rdf-triple" class="internalDFN">triples</a>, each consisting of a <a href="#dfn-subject" class="internalDFN">subject</a>,
+ a <a href="#dfn-predicate" class="internalDFN">predicate</a> and an <a href="#dfn-object" class="internalDFN">object</a>. A set of such triples is called
+ an <a href="#dfn-rdf-graph" class="internalDFN">RDF graph</a>. This can be illustrated by a node and
directed-arc diagram, in which each triple is represented as a
node-arc-node link; hence the term “graph”.</p>
<div class="figure">
- <a href="rdf-graph.png"><img src="rdf-graph.svg" alt="An RDF graph with two nodes (Subject and Object) and a triple connecting them (Predicate)" /></a>
+ <a href="rdf-graph.png"><img src="rdf-graph.svg" alt="An RDF graph with two nodes (Subject and Object) and a triple connecting them (Predicate)"></a>
</div>
- <p>There may be three kinds of <a title="node">nodes</a> in an
- <a>RDF graph</a>: <a title="IRI">IRIs</a>, <a title="literal">literals</a>,
- and <a title="blank node">blank nodes</a>.</p>
-</section>
+ <p>There may be three kinds of <a title="node" href="#dfn-node" class="internalDFN">nodes</a> in an
+ <a href="#dfn-rdf-graph" class="internalDFN">RDF graph</a>: <a title="IRI" href="#dfn-iri" class="internalDFN">IRIs</a>, <a title="literal" href="#dfn-literal" class="internalDFN">literals</a>,
+ and <a title="blank node" href="#dfn-blank-node" class="internalDFN">blank nodes</a>.</p>
+</div>
-<section id="resources-and-statements">
- <h3>Resources and Statements</h3>
+<div id="resources-and-statements" typeof="bibo:Chapter" about="#resources-and-statements" class="section">
+ <h3><span class="secno">1.2 </span>Resources and Statements</h3>
- <p>Any <a>IRI</a> and <a>literal</a> <dfn title="denote">denotes</dfn>
+ <p>Any <a href="#dfn-iri" class="internalDFN">IRI</a> and <a href="#dfn-literal" class="internalDFN">literal</a> <dfn title="denote" id="dfn-denote">denotes</dfn>
some thing in the universe of discourse. These things are called
- <dfn title="resource">resources</dfn>. Anything can be a resource,
+ <dfn title="resource" id="dfn-resource">resources</dfn>. Anything can be a resource,
including physical things, documents, abstract concepts, numbers
and strings; the term is synonymous with “entity”.
- The resource denoted by an IRI is called its <a>referent</a>, and the
+ The resource denoted by an IRI is called its <a href="#dfn-referent" class="internalDFN">referent</a>, and the
resource denoted by a literal is called its
- <a title="literal value">value</a>. Literals have
- <a title="datatype">datatypes</a> that define the range of possible
+ <a title="literal value" href="#dfn-literal-value" class="internalDFN">value</a>. Literals have
+ <a title="datatype" href="#dfn-datatype" class="internalDFN">datatypes</a> that define the range of possible
values, such as strings, numbers, and dates. A special kind of literals,
<a>language-tagged strings</a>, denote plain-text strings in a
natural language.</p>
- <p>The assertion of an <a>RDF triple</a> says that <em>some relationship,
- indicated by the <a>predicate</a>, holds between the
- <a title="resource">resources</a> <a title="denote">denoted</a> by
- the <a>subject</a> and <a>object</a></em>. This statement corresponding
- to an RDF triple is known as an <dfn>RDF statement</dfn>.
- The predicate itself is an <a>IRI</a> and denotes a binary relation,
- also known as a <dfn>property</dfn>. (Relations that involve more than
+ <p>The assertion of an <a href="#dfn-rdf-triple" class="internalDFN">RDF triple</a> says that <em>some relationship,
+ indicated by the <a href="#dfn-predicate" class="internalDFN">predicate</a>, holds between the
+ <a title="resource" href="#dfn-resource" class="internalDFN">resources</a> <a title="denote" href="#dfn-denote" class="internalDFN">denoted</a> by
+ the <a href="#dfn-subject" class="internalDFN">subject</a> and <a href="#dfn-object" class="internalDFN">object</a></em>. This statement corresponding
+ to an RDF triple is known as an <dfn id="dfn-rdf-statement">RDF statement</dfn>.
+ The predicate itself is an <a href="#dfn-iri" class="internalDFN">IRI</a> and denotes a binary relation,
+ also known as a <dfn id="dfn-property">property</dfn>. (Relations that involve more than
two entities can only be
<a href="http://www.w3.org/TR/swbp-n-aryRelations/">indirectly
- expressed in RDF</a> [[SWBP-N-ARYRELATIONS]].)</p>
+ expressed in RDF</a> [<cite><a class="bibref" rel="biblioentry" href="#bib-SWBP-N-ARYRELATIONS">SWBP-N-ARYRELATIONS</a></cite>].)</p>
- <p>The assertion of an <a>RDF graph</a> amounts to asserting all the
+ <p>The assertion of an <a href="#dfn-rdf-graph" class="internalDFN">RDF graph</a> amounts to asserting all the
triples in it, so the meaning of an RDF graph is the conjunction
- (logical AND) of the <a title="RDF statement">statements</a>
+ (logical AND) of the <a title="RDF statement" href="#dfn-rdf-statement" class="internalDFN">statements</a>
corresponding to all the triples it contains.</p>
- <p>Unlike <a title="IRI">IRIs</a> and <a title="literal">literals</a>,
- <a title="blank node">blank nodes</a> do not denote specific
- <a title="resource">resources</a>.
- <a title="RDF statement">Statements</a> involving
+ <p>Unlike <a title="IRI" href="#dfn-iri" class="internalDFN">IRIs</a> and <a title="literal" href="#dfn-literal" class="internalDFN">literals</a>,
+ <a title="blank node" href="#dfn-blank-node" class="internalDFN">blank nodes</a> do not denote specific
+ <a title="resource" href="#dfn-resource" class="internalDFN">resources</a>.
+ <a title="RDF statement" href="#dfn-rdf-statement" class="internalDFN">Statements</a> involving
blank nodes say that something with the given
relationships exists, without explicitly naming it.</p>
-</section>
+</div>
-<section id="referents">
- <h3>The Referent of an IRI</h3>
+<div id="referents" typeof="bibo:Chapter" about="#referents" class="section">
+ <h3><span class="secno">1.3 </span>The Referent of an IRI</h3>
- <p>The <a>resource</a> <a title="denote">denoted</a> by an <a>IRI</a>
- is also called its <dfn>referent</dfn>.
+ <p>The <a href="#dfn-resource" class="internalDFN">resource</a> <a title="denote" href="#dfn-denote" class="internalDFN">denoted</a> by an <a href="#dfn-iri" class="internalDFN">IRI</a>
+ is also called its <dfn id="dfn-referent">referent</dfn>.
What exactly is denoted by any given IRI is not defined by this
specification. The question is treated in other documents like
<em><a href="http://www.w3.org/TR/webarch/">Architecture of the
- World Wide Web, Volume One</a></em> [[WEBARCH]] and
+ World Wide Web, Volume One</a></em> [<cite><a class="bibref" rel="biblioentry" href="#bib-WEBARCH">WEBARCH</a></cite>] and
<em><a href="http://www.w3.org/TR/cooluris/">Cool URIs for the
- Semantic Web</a></em> [[COOLURIS]].
+ Semantic Web</a></em> [<cite><a class="bibref" rel="biblioentry" href="#bib-COOLURIS">COOLURIS</a></cite>].
A very brief, informal and partial account follows:</p>
<ul>
<li>By social convention, the
<a href="http://www.w3.org/TR/webarch/#uri-ownership">IRI owner</a>
- [[WEBARCH]] gets to say what an <a>IRI</a> <a title="denote">denotes</a>.
- They do this when “<dfn>minting</dfn>” a new IRI.</li>
+ [<cite><a class="bibref" rel="biblioentry" href="#bib-WEBARCH">WEBARCH</a></cite>] gets to say what an <a href="#dfn-iri" class="internalDFN">IRI</a> <a title="denote" href="#dfn-denote" class="internalDFN">denotes</a>.
+ They do this when “<dfn id="dfn-minting">minting</dfn>” a new IRI.</li>
- <li>The IRI owner can establish the intended <a>referent</a>
+ <li>The IRI owner can establish the intended <a href="#dfn-referent" class="internalDFN">referent</a>
by means of a specification or other document that explains
- what is denoted. For example, [[RDF-SCHEMA]] specifies the referents
+ what is denoted. For example, [<cite><a class="bibref" rel="biblioentry" href="#bib-RDF-SCHEMA">RDF-SCHEMA</a></cite>] specifies the referents
of various IRIs that start with
<code>http://www.w3.org/2000/01/rdf-schema#</code>.</li>
<li>A good way of communicating the intended referent to the world
is to set up the IRI so that it
<a href="http://www.w3.org/TR/webarch/#uri-dereference">dereferences</a>
- [[WEBARCH]] to such a document.</li>
+ [<cite><a class="bibref" rel="biblioentry" href="#bib-WEBARCH">WEBARCH</a></cite>] to such a document.</li>
- <li>Such a document can, in fact, be an <a>RDF document</a>
+ <li>Such a document can, in fact, be an <a href="#dfn-rdf-document" class="internalDFN">RDF document</a>
that describes the denoted resource by means of
- <a title="RDF statement">RDF statements</a>.</li>
+ <a title="RDF statement" href="#dfn-rdf-statement" class="internalDFN">RDF statements</a>.</li>
</ul>
<p class="issue">This should explain better that IRIs in RDF play
@@ -287,93 +657,95 @@
This specification is only concerned with the first aspect.
Alignment between the two aspects is generally important, but out
of scope for this spec.</p>
-</section>
+</div>
-<section id="vocabularies">
- <h3>RDF Vocabularies and Namespace IRIs</h3>
+<div id="vocabularies" typeof="bibo:Chapter" about="#vocabularies" class="section">
+ <h3><span class="secno">1.4 </span>RDF Vocabularies and Namespace IRIs</h3>
- <p>An <dfn>RDF vocabulary</dfn> is a collection of <a title="IRI">IRIs</a>
- with clearly established <a title="referent">referents</a>
- intended for use in <a title="RDF graph">RDF graphs</a>. For example,
- the IRIs documented in [[RDF-SCHEMA]] are the RDF Schema vocabulary.
+ <p>An <dfn id="dfn-rdf-vocabulary">RDF vocabulary</dfn> is a collection of <a title="IRI" href="#dfn-iri" class="internalDFN">IRIs</a>
+ with clearly established <a title="referent" href="#dfn-referent" class="internalDFN">referents</a>
+ intended for use in <a title="RDF graph" href="#dfn-rdf-graph" class="internalDFN">RDF graphs</a>. For example,
+ the IRIs documented in [<cite><a class="bibref" rel="biblioentry" href="#bib-RDF-SCHEMA">RDF-SCHEMA</a></cite>] are the RDF Schema vocabulary.
RDF Schema can itself be used to define and document additional
RDF vocabularies. Some such vocabularies are mentioned in the
- Primer [[RDF-PRIMER]].</p>
+ Primer [<cite><a class="bibref" rel="biblioentry" href="#bib-RDF-PRIMER">RDF-PRIMER</a></cite>].</p>
<p class="issue">The material below may be moved to the new
<em>RDF 1.1 Primer</em> document once it becomes available.</p>
- <p>The <a title="IRI">IRIs</a> in an <a>RDF vocabulary</a> often share
- a common substring known as a <dfn>namespace IRI</dfn>.
+ <p>The <a title="IRI" href="#dfn-iri" class="internalDFN">IRIs</a> in an <a href="#dfn-rdf-vocabulary" class="internalDFN">RDF vocabulary</a> often share
+ a common substring known as a <dfn id="dfn-namespace-iri">namespace IRI</dfn>.
Some namespace IRIs are associated by convention with a short name
- known as a <dfn>namespace prefix</dfn>. Some examples:
+ known as a <dfn id="dfn-namespace-prefix">namespace prefix</dfn>. Some examples:
- <table rules="all" summary="Some example namespace prefixes and IRIs">
- <tr><th>Namespace prefix</th><th>Namespace IRI</th><th>RDF vocabulary</th></tr>
- <tr><td>rdf</td><td><a href="http://www.w3.org/1999/02/22-rdf-syntax-ns#"><code>http://www.w3.org/1999/02/22-rdf-syntax-ns#</code></a></td><td>The RDF built-in vocabulary [[RDF-SCHEMA]]</td></tr>
- <tr><td>rdfs</td><td><a href="http://www.w3.org/2000/01/rdf-schema#"><code>http://www.w3.org/2000/01/rdf-schema#</code></a></td><td>The RDF Schema vocabulary [[RDF-SCHEMA]]</td></tr>
- <tr><td>xsd</td><td><a href="http://www.w3.org/2001/XMLSchema#"><code>http://www.w3.org/2001/XMLSchema#</code></a></td><td>The <a>RDF-compatible XSD types</a></td></tr>
- </table>
+ </p><table rules="all" summary="Some example namespace prefixes and IRIs">
+ <tbody><tr><th>Namespace prefix</th><th>Namespace IRI</th><th>RDF vocabulary</th></tr>
+ <tr><td>rdf</td><td><a href="http://www.w3.org/1999/02/22-rdf-syntax-ns#"><code>http://www.w3.org/1999/02/22-rdf-syntax-ns#</code></a></td><td>The RDF built-in vocabulary [<cite><a class="bibref" rel="biblioentry" href="#bib-RDF-SCHEMA">RDF-SCHEMA</a></cite>]</td></tr>
+ <tr><td>rdfs</td><td><a href="http://www.w3.org/2000/01/rdf-schema#"><code>http://www.w3.org/2000/01/rdf-schema#</code></a></td><td>The RDF Schema vocabulary [<cite><a class="bibref" rel="biblioentry" href="#bib-RDF-SCHEMA">RDF-SCHEMA</a></cite>]</td></tr>
+ <tr><td>xsd</td><td><a href="http://www.w3.org/2001/XMLSchema#"><code>http://www.w3.org/2001/XMLSchema#</code></a></td><td>The <a href="#dfn-rdf-compatible-xsd-types" class="internalDFN">RDF-compatible XSD types</a></td></tr>
+ </tbody></table>
- <p>In some contexts it is common to abbreviate <a title="IRI">IRIs</a>
- that start with <a title="namespace IRI">namespace IRIs</a> by using the
- associated <a>namespace prefix</a>. For example, the IRI
+ <p>In some contexts it is common to abbreviate <a title="IRI" href="#dfn-iri" class="internalDFN">IRIs</a>
+ that start with <a title="namespace IRI" href="#dfn-namespace-iri" class="internalDFN">namespace IRIs</a> by using the
+ associated <a href="#dfn-namespace-prefix" class="internalDFN">namespace prefix</a>. For example, the IRI
<code>http://www.w3.org/1999/02/22-rdf-syntax-ns#XMLLiteral</code>
would be abbreviated as <code>rdf:XMLLiteral</code>.
Note however that these abbreviations are <em>not</em> valid IRIs,
- and MUST NOT be used in contexts where IRIs are expected.
+ and <em class="rfc2119" title="must not">must not</em> be used in contexts where IRIs are expected.
Namespace IRIs and namespace prefixes are <em>not</em> a formal part of the
RDF data model. They are merely a syntactic convenience for
abbreviating IRIs.</p>
- <p>The term “<dfn>namespace</dfn>” on its own does not have a
+ <p>The term “<dfn id="dfn-namespace">namespace</dfn>” on its own does not have a
well-defined meaning in the context of RDF, but is sometimes informally
- used to mean “<a>namespace IRI</a>” or “<a>RDF vocabulary</a>”.</p>
-</section>
+ used to mean “<a href="#dfn-namespace-iri" class="internalDFN">namespace IRI</a>” or “<a href="#dfn-rdf-vocabulary" class="internalDFN">RDF vocabulary</a>”.</p>
+</div>
-<section id="entailment">
- <h3>Formal Meaning and Entailment</h3>
+<div id="entailment" typeof="bibo:Chapter" about="#entailment" class="section">
+ <h3><span class="secno">1.5 </span>Formal Meaning and Entailment</h3>
<p>The idea of meaning in RDF is underpinned by the formal concept
- of <dfn>entailment</dfn>. In brief, an <a>RDF graph</a> <em>A</em>
+ of <dfn id="dfn-entailment">entailment</dfn>. In brief, an <a href="#dfn-rdf-graph" class="internalDFN">RDF graph</a> <em>A</em>
is said to <em>entail</em> another RDF graph <em>B</em> if every
possible arrangement of things in the world that makes <em>A</em> true
also makes <em>B</em> true. On this basis, if the truth of <em>A</em>
is presumed or demonstrated then the truth of <em>B</em> can be inferred.
An account of meaning and entailment in RDF, using the formalism of
- model theory, is given in [[RDF-MT]].</p>
+ model theory, is given in [<cite><a class="bibref" rel="biblioentry" href="#bib-RDF-MT">RDF-MT</a></cite>].</p>
<p class="issue">The Working Group is considering removing the
<a href="http://www.w3.org/TR/rdf-mt/#rules">informative entailment rules</a>
from the <em>RDF Semantics</em> document, and moving them to another
document. Moving them to this document is one possibility.</p>
-</section>
+</div>
-<section id="managing-graphs">
- <h3>Merging and Managing RDF Graphs</h3>
+<div id="managing-graphs" typeof="bibo:Chapter" about="#managing-graphs" class="section">
+ <h3><span class="secno">1.6 </span>Merging and Managing RDF Graphs</h3>
<p class="issue">This section should explain terminology around
<a href="#section-dataset">working with multiple graphs</a>,
and explain the fact that graphs merge easily.
This will be added once the Working Group has finalised a design.</p>
- <p>An <dfn>RDF document</dfn> is a document that encodes an
- <a>RDF graph</a> in a <dfn>concrete RDF syntax</dfn>, such as
- Turtle [[TURTLE-TR]], RDFa [[RDFA-PRIMER]], RDF/XML [[RDF-SYNTAX-GRAMMAR]],
- or N-Triples [[N-TRIPLES]].</p>
-</section>
+ <p>An <dfn id="dfn-rdf-document">RDF document</dfn> is a document that encodes an
+ <a href="#dfn-rdf-graph" class="internalDFN">RDF graph</a> in a <dfn id="dfn-concrete-rdf-syntax">concrete RDF syntax</dfn>, such as
+ Turtle [<cite><a class="bibref" rel="biblioentry" href="#bib-TURTLE-TR">TURTLE-TR</a></cite>], RDFa [<cite><a class="bibref" rel="biblioentry" href="#bib-RDFA-PRIMER">RDFA-PRIMER</a></cite>], RDF/XML [<cite><a class="bibref" rel="biblioentry" href="#bib-RDF-SYNTAX-GRAMMAR">RDF-SYNTAX-GRAMMAR</a></cite>],
+ or N-Triples [<cite><a class="bibref" rel="biblioentry" href="#bib-N-TRIPLES">N-TRIPLES</a></cite>].</p>
+</div>
-</section>
+</div>
-<section id="conformance">
+<div id="conformance" typeof="bibo:Chapter" about="#conformance" class="section"><h2><span class="secno">2 </span>Conformance</h2><p>As well as sections marked as non-normative, all authoring guidelines, diagrams, examples, and notes in this specification are non-normative. Everything else in this specification is normative.</p>
+<p>The key words <em class="rfc2119" title="must">must</em>, <em class="rfc2119" title="must not">must not</em>, <em class="rfc2119" title="required">required</em>, <em class="rfc2119" title="should">should</em>, <em class="rfc2119" title="should not">should not</em>, <em class="rfc2119" title="recommended">recommended</em>, <em class="rfc2119" title="may">may</em>, and <em class="rfc2119" title="optional">optional</em> in this specification are to be interpreted as described in [<cite><a class="bibref" rel="biblioentry" href="#bib-RFC2119">RFC2119</a></cite>].</p>
+
<p>This specification, <em>RDF 1.1 Concepts and Abstract Syntax</em>,
defines a data model and related terminology for use in
other specifications, such as
- <a title="concrete RDF syntax">concrete RDF syntaxes</a>,
+ <a title="concrete RDF syntax" href="#dfn-concrete-rdf-syntax" class="internalDFN">concrete RDF syntaxes</a>,
API specifications, and query languages.
Implementations cannot directly conform to
<em>RDF 1.1 Concepts and Abstract Syntax</em>,
@@ -382,32 +754,32 @@
<p>Another specification conforms to
<em>RDF 1.1 Concepts and Abstract Syntax</em> if it defines operations
- in terms of <a title="RDF graph">RDF graphs</a>
- or <a title="RDF dataset">RDF datasets</a>, and if any use of
+ in terms of <a title="RDF graph" href="#dfn-rdf-graph" class="internalDFN">RDF graphs</a>
+ or <a title="RDF dataset" href="#dfn-rdf-dataset" class="internalDFN">RDF datasets</a>, and if any use of
terminology defined in normative sections of
<em>RDF 1.1 Concepts and Abstract Syntax</em>
is consistent with its definitions and conformance requirements.</p>
-</section>
+</div>
-<section id="section-rdf-graph">
- <h2>RDF Graphs</h2>
+<div id="section-rdf-graph" typeof="bibo:Chapter" about="#section-rdf-graph" class="section">
+ <h2><span class="secno">3 </span>RDF Graphs</h2>
- <p>An <dfn>RDF graph</dfn> is a set of
- <a title="RDF triple">RDF triples</a>.</p>
+ <p>An <dfn id="dfn-rdf-graph">RDF graph</dfn> is a set of
+ <a title="RDF triple" href="#dfn-rdf-triple" class="internalDFN">RDF triples</a>.</p>
- <p><a name="section-graph-equality"></a><dfn>Graph isomorphism</dfn>:
- Two <a title="RDF graph">RDF graphs</a>
+ <p><a name="section-graph-equality"></a><dfn id="dfn-graph-isomorphism">Graph isomorphism</dfn>:
+ Two <a title="RDF graph" href="#dfn-rdf-graph" class="internalDFN">RDF graphs</a>
<var>G</var> and <var>G'</var> are <em>isomorphic</em> if there
is a bijection <var>M</var> between the sets of nodes of the two graphs,
such that:</p>
<ol>
<li><var>M</var> maps blank nodes to blank nodes.</li>
- <li><var>M(lit)=lit</var> for all <a title="literal">RDF literals</a> <var>lit</var> which
+ <li><var>M(lit)=lit</var> for all <a title="literal" href="#dfn-literal" class="internalDFN">RDF literals</a> <var>lit</var> which
are nodes of <var>G</var>.</li>
- <li><var>M(uri)=uri</var> for all <a title="IRI">IRIs</a> <var>uri</var>
+ <li><var>M(uri)=uri</var> for all <a title="IRI" href="#dfn-iri" class="internalDFN">IRIs</a> <var>uri</var>
which are nodes of <var>G</var>.</li>
<li>The triple <var>( s, p, o )</var> is in <var>G</var> if and
@@ -417,62 +789,62 @@
<p>With this definition, <var>M</var> shows how each blank node
in <var>G</var> can be replaced with
a new blank node to give <var>G'</var>. Graph isomorphism
- is needed to support the RDF Test Cases [[RDF-TESTCASES]] specification.</p>
+ is needed to support the RDF Test Cases [<cite><a class="bibref" rel="biblioentry" href="#bib-RDF-TESTCASES">RDF-TESTCASES</a></cite>] specification.</p>
-<section id="section-triples">
- <h3>Triples</h3>
+<div id="section-triples" typeof="bibo:Chapter" about="#section-triples" class="section">
+ <h3><span class="secno">3.1 </span>Triples</h3>
- <p>An <dfn>RDF triple</dfn> contains three components:</p>
+ <p>An <dfn id="dfn-rdf-triple">RDF triple</dfn> contains three components:</p>
<ul>
- <li>the <dfn>subject</dfn>, which is an
- <a>IRI</a> or a <a>blank node</a></li>
+ <li>the <dfn id="dfn-subject">subject</dfn>, which is an
+ <a href="#dfn-iri" class="internalDFN">IRI</a> or a <a href="#dfn-blank-node" class="internalDFN">blank node</a></li>
- <li>the <dfn>predicate</dfn>, which is an <a>IRI</a></li>
+ <li>the <dfn id="dfn-predicate">predicate</dfn>, which is an <a href="#dfn-iri" class="internalDFN">IRI</a></li>
- <li>the <dfn>object</dfn>, which is an <a>IRI</a>,
- a <a>literal</a> or a <a>blank node</a></li>
+ <li>the <dfn id="dfn-object">object</dfn>, which is an <a href="#dfn-iri" class="internalDFN">IRI</a>,
+ a <a href="#dfn-literal" class="internalDFN">literal</a> or a <a href="#dfn-blank-node" class="internalDFN">blank node</a></li>
</ul>
<p>An RDF triple is conventionally written in the order subject,
predicate, object.</p>
- <p>The set of <dfn title="node">nodes</dfn> of an <a>RDF graph</a>
+ <p>The set of <dfn title="node" id="dfn-node">nodes</dfn> of an <a href="#dfn-rdf-graph" class="internalDFN">RDF graph</a>
is the set of subjects and objects of triples in the graph.
- Predicate IRIs MAY also appear as nodes in the graph.</p>
+ Predicate IRIs <em class="rfc2119" title="may">may</em> also appear as nodes in the graph.</p>
- <p><a title="IRI">IRIs</a>, <a title="blank node">blank nodes</a> and
- <a title="literal">literals</a> are collectively known as
- <dfn title="RDF term">RDF terms</dfn>.</p>
-</section>
+ <p><a title="IRI" href="#dfn-iri" class="internalDFN">IRIs</a>, <a title="blank node" href="#dfn-blank-node" class="internalDFN">blank nodes</a> and
+ <a title="literal" href="#dfn-literal" class="internalDFN">literals</a> are collectively known as
+ <dfn title="RDF term" id="dfn-rdf-term">RDF terms</dfn>.</p>
+</div>
-<section id="section-IRIs">
- <h3>IRIs</h3>
+<div id="section-IRIs" typeof="bibo:Chapter" about="#section-IRIs" class="section">
+ <h3><span class="secno">3.2 </span>IRIs</h3>
- <p>An <dfn title="IRI"><acronym title="Internationalized Resource Identifier">IRI</acronym></dfn>
+ <p>An <dfn title="IRI" id="dfn-iri"><acronym title="Internationalized Resource Identifier">IRI</acronym></dfn>
(Internationalized Resource Identifier) within an RDF graph
- is a Unicode string [[!UNICODE]] that conforms to the syntax
- defined in RFC 3987 [[!IRI]]. IRIs are a generalization of
- <dfn title="URI"><acronym title="Uniform Resource Identifier">URI</acronym>s</dfn>
- [[URI]]. Every absolute URI and URL is an IRI.</p>
+ is a Unicode string [<cite><a class="bibref" rel="biblioentry" href="#bib-UNICODE">UNICODE</a></cite>] that conforms to the syntax
+ defined in RFC 3987 [<cite><a class="bibref" rel="biblioentry" href="#bib-IRI">IRI</a></cite>]. IRIs are a generalization of
+ <dfn title="URI" id="dfn-uri"><acronym title="Uniform Resource Identifier">URI</acronym>s</dfn>
+ [<cite><a class="bibref" rel="biblioentry" href="#bib-URI">URI</a></cite>]. Every absolute URI and URL is an IRI.</p>
- <p>IRIs in the RDF abstract syntax MUST be absolute, and MAY
+ <p>IRIs in the RDF abstract syntax <em class="rfc2119" title="must">must</em> be absolute, and <em class="rfc2119" title="may">may</em>
contain a fragment identifier.</p>
- <p><dfn>IRI equality</dfn>:
+ <p><dfn id="dfn-iri-equality">IRI equality</dfn>:
Two IRIs are equal if and only if they are equivalent
under Simple String Comparison according to
<a href="http://tools.ietf.org/html/rfc3987#section-5.1">section 5.1</a>
- of [[!IRI]]. Further normalization MUST NOT be performed when
+ of [<cite><a class="bibref" rel="biblioentry" href="#bib-IRI">IRI</a></cite>]. Further normalization <em class="rfc2119" title="must not">must not</em> be performed when
comparing IRIs for equality.</p>
<p class="note">When IRIs are used in operations that are only
defined for URIs, they must first be converted according to
the mapping defined in
<a href="http://tools.ietf.org/html/rfc3987#section-3.1">section 3.1</a>
- of [[!IRI]]. A notable example is retrieval over the HTTP
+ of [<cite><a class="bibref" rel="biblioentry" href="#bib-IRI">IRI</a></cite>]. A notable example is retrieval over the HTTP
protocol. The mapping involves UTF-8 encoding of non-ASCII
characters, %-encoding of octets not allowed in URIs, and
Punycode-encoding of domain names.</p>
@@ -482,7 +854,7 @@
the relative IRIs against a base IRI.</p>
<p class="note">Previous versions of RDF used the term
- “<dfn>RDF URI Reference</dfn>” instead of “IRI” and allowed
+ “<dfn id="dfn-rdf-uri-reference">RDF URI Reference</dfn>” instead of “IRI” and allowed
additional characters:
“<code><</code>”, “<code>></code>”,
“<code>{</code>”, “<code>}</code>”,
@@ -491,13 +863,13 @@
‘<code>“</code>’ (double quote), and “<code> </code>” (space).
In IRIs, these characters must be percent-encoded as
described in <a href="http://tools.ietf.org/html/rfc3986#section-2.1">section 2.1</a>
- of [[URI]].</p>
+ of [<cite><a class="bibref" rel="biblioentry" href="#bib-URI">URI</a></cite>].</p>
<div class="note" id="note-iri-interop">
<p>Interoperability problems can be avoided by minting
only IRIs that are normalized according to
<a href="http://tools.ietf.org/html/rfc3987#section-5">Section 5</a>
- of [[!IRI]]. Non-normalized forms that should be avoided
+ of [<cite><a class="bibref" rel="biblioentry" href="#bib-IRI">IRI</a></cite>]. Non-normalized forms that should be avoided
include:</p>
<ul>
@@ -518,76 +890,76 @@
<li>Punycode-encoding of Internationalized Domain Names
in IRIs</li>
<li>IRIs that are not in Unicode Normalization
- Form C [[!NFC]]</li>
+ Form C [<cite><a class="bibref" rel="biblioentry" href="#bib-NFC">NFC</a></cite>]</li>
</ul>
</div>
-</section>
+</div>
-<section id="section-Graph-Literal">
- <h2>Literals</h2>
+<div id="section-Graph-Literal" typeof="bibo:Chapter" about="#section-Graph-Literal" class="section">
+ <h3><span class="secno">3.3 </span>Literals</h3>
<p>Literals are used to denote values such as strings, numbers and dates
by means of a lexical representation.</p>
- <p>A <dfn>literal</dfn> in an <a>RDF graph</a> consists of:</p>
+ <p>A <dfn id="dfn-literal">literal</dfn> in an <a href="#dfn-rdf-graph" class="internalDFN">RDF graph</a> consists of:</p>
<ul>
- <li>a <dfn>lexical form</dfn> being a Unicode [[!UNICODE]] string,
- which SHOULD be in Normal Form C [[!NFC]],</li>
- <li>a <dfn>datatype IRI</dfn> being an <a>IRI</a> that establishes
- the <a>literal value</a>.</li>
+ <li>a <dfn id="dfn-lexical-form">lexical form</dfn> being a Unicode [<cite><a class="bibref" rel="biblioentry" href="#bib-UNICODE">UNICODE</a></cite>] string,
+ which <em class="rfc2119" title="should">should</em> be in Normal Form C [<cite><a class="bibref" rel="biblioentry" href="#bib-NFC">NFC</a></cite>],</li>
+ <li>a <dfn id="dfn-datatype-iri">datatype IRI</dfn> being an <a href="#dfn-iri" class="internalDFN">IRI</a> that establishes
+ the <a href="#dfn-literal-value" class="internalDFN">literal value</a>.</li>
</ul>
- <p>A <dfn>language-tagged string</dfn> is any <a>literal</a>
- whose <a>datatype IRI</a> is equal to
+ <p>A <dfn id="dfn-language-tagged-string">language-tagged string</dfn> is any <a href="#dfn-literal" class="internalDFN">literal</a>
+ whose <a href="#dfn-datatype-iri" class="internalDFN">datatype IRI</a> is equal to
<code>http://www.w3.org/1999/02/22-rdf-syntax-ns#langString</code>.
- In addition to <a>lexical form</a> and datatype IRI,
+ In addition to <a href="#dfn-lexical-form" class="internalDFN">lexical form</a> and datatype IRI,
a language-tagged string also has:</p>
<ul>
- <li>a non-empty <dfn>language tag</dfn> as defined by [[!BCP47]].
- The language tag MUST be well-formed according to
+ <li>a non-empty <dfn id="dfn-language-tag">language tag</dfn> as defined by [<cite><a class="bibref" rel="biblioentry" href="#bib-BCP47">BCP47</a></cite>].
+ The language tag <em class="rfc2119" title="must">must</em> be well-formed according to
<a href="http://tools.ietf.org/html/bcp47#section-2.2.9">section 2.2.9</a>
- of [[!BCP47]], and MUST be normalized to lowercase.</li>
+ of [<cite><a class="bibref" rel="biblioentry" href="#bib-BCP47">BCP47</a></cite>], and <em class="rfc2119" title="must">must</em> be normalized to lowercase.</li>
</ul>
- <p>Concrete syntaxes MAY support <dfn title="simple literal">simple
- literals</dfn>, consisting of only a <a>lexical form</a>
+ <p>Concrete syntaxes <em class="rfc2119" title="may">may</em> support <dfn title="simple literal" id="dfn-simple-literal">simple
+ literals</dfn>, consisting of only a <a href="#dfn-lexical-form" class="internalDFN">lexical form</a>
without any datatype IRI or language tag. Simple literals only
exist in concrete syntaxes, and are treated as
syntactic sugar for abstract syntax
- <a title="literal">literals</a> with the <a>datatype IRI</a>
+ <a title="literal" href="#dfn-literal" class="internalDFN">literals</a> with the <a href="#dfn-datatype-iri" class="internalDFN">datatype IRI</a>
<code>http://www.w3.org/2001/XMLSchema#string</code>.</p>
- <p><dfn>Literal equality</dfn>:
+ <p><dfn id="dfn-literal-equality">Literal equality</dfn>:
Two literals are equal if and only if the two
- <a title="lexical form">lexical forms</a>, the two
- <a title="datatype IRI">datatype IRIs</a>, and the two
- <a title="language tag">language tags</a> (if any)
+ <a title="lexical form" href="#dfn-lexical-form" class="internalDFN">lexical forms</a>, the two
+ <a title="datatype IRI" href="#dfn-datatype-iri" class="internalDFN">datatype IRIs</a>, and the two
+ <a title="language tag" href="#dfn-language-tag" class="internalDFN">language tags</a> (if any)
compare equal, character by character.</p>
<p class="note">In earlier versions of RDF, literals with a
- <a>language tag</a> did not have a <a>datatype IRI</a>, and
- <a title="simple literal">simple literals</a> could appear
+ <a href="#dfn-language-tag" class="internalDFN">language tag</a> did not have a <a href="#dfn-datatype-iri" class="internalDFN">datatype IRI</a>, and
+ <a title="simple literal" href="#dfn-simple-literal" class="internalDFN">simple literals</a> could appear
directly in the abstract syntax. Simple literals and literals with a
language tag were collectively known as
- <dfn title="plain literal">plain literals</dfn>.</p>
+ <dfn title="plain literal" id="dfn-plain-literal">plain literals</dfn>.</p>
<p class="note">Literals in which the lexical form begins with a
- composing character (as defined by [[CHARMOD]]) are allowed however they may cause
- interoperability problems, particularly with XML version 1.1 [[XML11]].</p>
+ composing character (as defined by [<cite><a class="bibref" rel="biblioentry" href="#bib-CHARMOD">CHARMOD</a></cite>]) are allowed however they may cause
+ interoperability problems, particularly with XML version 1.1 [<cite><a class="bibref" rel="biblioentry" href="#bib-XML11">XML11</a></cite>].</p>
<p class="note">Earlier versions of RDF permitted tags that
adhered to the generic tag/subtag syntax of language tags,
- but were not well-formed according to [[!BCP47]]. Such
+ but were not well-formed according to [<cite><a class="bibref" rel="biblioentry" href="#bib-BCP47">BCP47</a></cite>]. Such
language tags do not conform to RDF 1.1.</p>
<p class="note">The <code>xsd:string</code> datatype does not
permit the <code>#x0</code> character, and implementations may not permit
control codes in the <code>#x1-#x1F</code> range. Earlier versions of
RDF allowed these characters in
- <a title="simple literal">simple literals</a>, although they
+ <a title="simple literal" href="#dfn-simple-literal" class="internalDFN">simple literals</a>, although they
could never be serialized in a W3C-recommended concrete syntax.</p>
<p class="note">When using the language tag, care must be
@@ -605,21 +977,21 @@
the original input.</p>
<p class="note">RDF Literals are distinct and distinguishable
- from <a title="IRI">IRIs</a>; e.g. <code>http://example.org/</code>
- as a string <a>literal</a> is not equal to <code>http://example.org/</code>
+ from <a title="IRI" href="#dfn-iri" class="internalDFN">IRIs</a>; e.g. <code>http://example.org/</code>
+ as a string <a href="#dfn-literal" class="internalDFN">literal</a> is not equal to <code>http://example.org/</code>
as an IRI.</p>
-</section>
+</div>
-<section id="section-blank-nodes">
- <h2>Blank Nodes</h2>
+<div id="section-blank-nodes" typeof="bibo:Chapter" about="#section-blank-nodes" class="section">
+ <h3><span class="secno">3.4 </span>Blank Nodes</h3>
- <p>The <dfn title="blank node">blank nodes</dfn> in an RDF graph
+ <p>The <dfn title="blank node" id="dfn-blank-node">blank nodes</dfn> in an RDF graph
are drawn from an infinite set. This set is disjoint from the set
- of all <a title="IRI">IRIs</a> and the set of all
- <a title="literal">literals</a>.
+ of all <a title="IRI" href="#dfn-iri" class="internalDFN">IRIs</a> and the set of all
+ <a title="literal" href="#dfn-literal" class="internalDFN">literals</a>.
Otherwise, this set of blank nodes is arbitrary.</p>
<p>Given two blank nodes, it is
@@ -628,9 +1000,9 @@
of blank nodes.</p>
<p class="note" id="note-bnode-id">
- <dfn title="blank node identifier">Blank node identifiers</dfn>
+ <dfn title="blank node identifier" id="dfn-blank-node-identifier">Blank node identifiers</dfn>
are local identifiers that are used in some
- <a title="concrete RDF syntax">concrete RDF syntaxes</a>
+ <a title="concrete RDF syntax" href="#dfn-concrete-rdf-syntax" class="internalDFN">concrete RDF syntaxes</a>
or RDF store implementations.
They are always locally scoped to the file or RDF store,
and are <em>not</em> persistent or portable identifiers
@@ -639,21 +1011,21 @@
on the concrete syntax or implementation. The syntactic restrictions
on blank node identifiers, if any, therefore also depend on
the concrete RDF syntax or implementation.</p>
-</section>
+</div>
-<section id="section-skolemization">
- <h3>Replacing Blank Nodes with IRIs</h3>
+<div id="section-skolemization" typeof="bibo:Chapter" about="#section-skolemization" class="section">
+ <h3><span class="secno">3.5 </span>Replacing Blank Nodes with IRIs</h3>
<p>Blank nodes do not have identifiers in the RDF abstract syntax. The
- <a title="blank node identifier">blank node identifiers</a> introduced
+ <a title="blank node identifier" href="#dfn-blank-node-identifier" class="internalDFN">blank node identifiers</a> introduced
by some concrete syntaxes have only
local scope and are purely an artifact of the serialization.</p>
- <p>In situations where stronger identification is needed, systems MAY
+ <p>In situations where stronger identification is needed, systems <em class="rfc2119" title="may">may</em>
systematically transform some or all of the blank nodes in an RDF graph
- into IRIs [[!IRI]]. Systems wishing to do this SHOULD mint a new, globally
- unique IRI (a <dfn>Skolem IRI</dfn>) for each blank node so transformed.</p>
+ into IRIs [<cite><a class="bibref" rel="biblioentry" href="#bib-IRI">IRI</a></cite>]. Systems wishing to do this <em class="rfc2119" title="should">should</em> mint a new, globally
+ unique IRI (a <dfn id="dfn-skolem-iri">Skolem IRI</dfn>) for each blank node so transformed.</p>
<p>This transformation does not change the meaning of an RDF graph,
provided that the Skolem IRIs do not occur anywhere else.</p>
@@ -663,12 +1035,12 @@
node, and map back to the source blank node where possible.</p>
<p>Systems that want Skolem IRIs to be recognizable outside of the system
- boundaries SHOULD use a well-known IRI [[WELL-KNOWN]] with the registered
+ boundaries <em class="rfc2119" title="should">should</em> use a well-known IRI [<cite><a class="bibref" rel="biblioentry" href="#bib-WELL-KNOWN">WELL-KNOWN</a></cite>] with the registered
name <code>genid</code>. This is an IRI that uses the HTTP or HTTPS scheme,
or another scheme that has been specified to use well-known IRIs; and whose
path component starts with <code>/.well-known/genid/</code>.
- <p>For example, the authority responsible for the domain
+ </p><p>For example, the authority responsible for the domain
<code>example.com</code> could mint the following recognizable Skolem IRI:</p>
<pre>http://example.com/.well-known/genid/d26a2d0e98334696f4ad70a677abc1f6</pre>
@@ -677,33 +1049,33 @@
currently in progress. This is
<a href="http://www.w3.org/2011/rdf-wg/track/actions/82">ACTION-82</a>.</p>
- <p class="note">RFC 5785 [[WELL-KNOWN]] only specifies well-known URIs,
+ <p class="note">RFC 5785 [<cite><a class="bibref" rel="biblioentry" href="#bib-WELL-KNOWN">WELL-KNOWN</a></cite>] only specifies well-known URIs,
not IRIs. For the purpose of this document, a well-known IRI is any
- IRI that results in a well-known URI after IRI-to-URI mapping [[!IRI]].</p>
-</section>
+ IRI that results in a well-known URI after IRI-to-URI mapping [<cite><a class="bibref" rel="biblioentry" href="#bib-IRI">IRI</a></cite>].</p>
+</div>
-</section>
+</div>
-<section id="section-dataset">
- <h2>RDF Datasets</h2>
+<div id="section-dataset" typeof="bibo:Chapter" about="#section-dataset" class="section">
+ <h2><span class="secno">4 </span>RDF Datasets</h2>
<p>The RDF data model expresses information as
- <a title="RDF graph">RDF graphs</a> consisting of
+ <a title="RDF graph" href="#dfn-rdf-graph" class="internalDFN">RDF graphs</a> consisting of
<a title="triple">triples</a> with subject, predicate and object.
Often, one wants to hold multiple RDF graphs and record information
about each graph, allowing an application to work with datasets
that involve information from more than one graph.</p>
- <p>An <dfn>RDF Dataset</dfn> is a collection of
- <a title="RDF graph">RDF graphs</a> and comprises:</p>
+ <p>An <dfn id="dfn-rdf-dataset">RDF Dataset</dfn> is a collection of
+ <a title="RDF graph" href="#dfn-rdf-graph" class="internalDFN">RDF graphs</a> and comprises:</p>
<ul>
- <li>Exactly one <dfn>default graph</dfn>, being an <a>RDF graph</a>.
- The default graph does not have a name and MAY be empty.</li>
- <li>Zero or more <dfn title="named graph">named graphs</dfn>.
- Each named graph is a pair consisting of an <a>IRI</a>
- (the <dfn>graph name</dfn>), and an <a>RDF graph</a>.
+ <li>Exactly one <dfn id="dfn-default-graph">default graph</dfn>, being an <a href="#dfn-rdf-graph" class="internalDFN">RDF graph</a>.
+ The default graph does not have a name and <em class="rfc2119" title="may">may</em> be empty.</li>
+ <li>Zero or more <dfn title="named graph" id="dfn-named-graph">named graphs</dfn>.
+ Each named graph is a pair consisting of an <a href="#dfn-iri" class="internalDFN">IRI</a>
+ (the <dfn id="dfn-graph-name">graph name</dfn>), and an <a href="#dfn-rdf-graph" class="internalDFN">RDF graph</a>.
Graph names are unique within an RDF dataset.</li>
</ul>
@@ -737,37 +1109,37 @@
<p class="note">When RDF graphs are merged, their blank nodes must be kept
distinct if meaning is to be preserved; this may call for re-allocation of
blank node identifiers.</p>
- </div>
+
<p class="issue">Should “Graph merge” be defined in this spec?
If not, then the previous note could just as well go. This will be
decided once a multigraph design has been decided upon.</p>
-</section>
+</div>
-<section id="section-Datatypes">
- <h2>Datatypes</h2>
+<div id="section-Datatypes" typeof="bibo:Chapter" about="#section-Datatypes" class="section">
+ <h2><span class="secno">5 </span>Datatypes</h2>
- <p>Datatypes are used with RDF <a title="literal">literals</a>
+ <p>Datatypes are used with RDF <a title="literal" href="#dfn-literal" class="internalDFN">literals</a>
to represent values such as string, numbers and dates.
The datatype abstraction used in RDF is compatible with XML Schema
- [[!XMLSCHEMA11-2]]. Any datatype definition that conforms
- to this abstraction MAY be used in RDF, even if not defined
+ [<cite><a class="bibref" rel="biblioentry" href="#bib-XMLSCHEMA11-2">XMLSCHEMA11-2</a></cite>]. Any datatype definition that conforms
+ to this abstraction <em class="rfc2119" title="may">may</em> be used in RDF, even if not defined
in terms of XML Schema. RDF re-uses the XML Schema built-in datatypes,
and provides two additional built-in datatypes,
- <code><a>rdf:HTML</a></code> and <code><a>rdf:XMLLiteral</a></code>.</p>
-
- <p>A <dfn>datatype</dfn> consists of a <a>lexical space</a>,
- a <a>value space</a> and a <a>lexical-to-value mapping</a>, and
- is denoted by one or more <a title="IRI">IRIs</a>.</p>
+ <code><a href="#dfn-rdf-html" class="internalDFN">rdf:HTML</a></code> and <code><a href="#dfn-rdf-xmlliteral" class="internalDFN">rdf:XMLLiteral</a></code>.</p>
-<p>The <dfn>lexical space</dfn> of a datatype is a set of Unicode [[!UNICODE]] strings.</p>
+ <p>A <dfn id="dfn-datatype">datatype</dfn> consists of a <a href="#dfn-lexical-space" class="internalDFN">lexical space</a>,
+ a <a href="#dfn-value-space" class="internalDFN">value space</a> and a <a href="#dfn-lexical-to-value-mapping" class="internalDFN">lexical-to-value mapping</a>, and
+ is denoted by one or more <a title="IRI" href="#dfn-iri" class="internalDFN">IRIs</a>.</p>
+
+<p>The <dfn id="dfn-lexical-space">lexical space</dfn> of a datatype is a set of Unicode [<cite><a class="bibref" rel="biblioentry" href="#bib-UNICODE">UNICODE</a></cite>] strings.</p>
<p>
-The <dfn>lexical-to-value mapping</dfn> of a datatype is a set of pairs whose
+The <dfn id="dfn-lexical-to-value-mapping">lexical-to-value mapping</dfn> of a datatype is a set of pairs whose
first element belongs to
-the <a>lexical space</a> of the datatype,
+the <a href="#dfn-lexical-space" class="internalDFN">lexical space</a> of the datatype,
and the second element belongs to the
- <dfn>value space</dfn> of the datatype:
+ <dfn id="dfn-value-space">value space</dfn> of the datatype:
</p>
<ul>
<li>
@@ -796,7 +1168,7 @@
Schema mechanisms that control the lexical space and the value space;
however, RDF does not define a standard mechanism to access these facets.</li>
- <li>In [[XMLSCHEMA11-1]],
+ <li>In [<cite><a class="bibref" rel="biblioentry" href="#bib-XMLSCHEMA11-1">XMLSCHEMA11-1</a></cite>],
<a href="http://www.w3.org/TR/xmlschema11-1/#sec-wsnormalization">white space normalization</a>
occurs during
<a href="http://www.w3.org/TR/xmlschema11-1/#key-vn">validation</a>
@@ -808,17 +1180,17 @@
</ul>
</div>
- <p class="note"><a title="language-tagged string">Language-tagged
- strings</a> have the <a>datatype IRI</a>
+ <p class="note"><a title="language-tagged string" href="#dfn-language-tagged-string" class="internalDFN">Language-tagged
+ strings</a> have the <a href="#dfn-datatype-iri" class="internalDFN">datatype IRI</a>
<code>http://www.w3.org/1999/02/22-rdf-syntax-ns#langString</code>.
No datatype is formally defined for this IRI because the definition
- of <a title="datatype">datatypes</a> does not accommodate
- <a title="language tag">language tags</a> in the <a>lexical space</a>.
- The <a>value space</a> associated with the datatype IRI is the set
+ of <a title="datatype" href="#dfn-datatype" class="internalDFN">datatypes</a> does not accommodate
+ <a title="language tag" href="#dfn-language-tag" class="internalDFN">language tags</a> in the <a href="#dfn-lexical-space" class="internalDFN">lexical space</a>.
+ The <a href="#dfn-value-space" class="internalDFN">value space</a> associated with the datatype IRI is the set
of all pairs of strings and language tags.</p>
<p>For example, the XML Schema datatype <code>xsd:boolean</code>,
- where each member of the <a>value space</a> has two lexical
+ where each member of the <a href="#dfn-value-space" class="internalDFN">value space</a> has two lexical
representations, is defined as follows:</p>
<dl>
@@ -835,11 +1207,11 @@
}</dd>
</dl>
- <p>The <a title="literal">literals</a> that can be defined using this
+ <p>The <a title="literal" href="#dfn-literal" class="internalDFN">literals</a> that can be defined using this
datatype are:</p>
<table rules="all" summary="This table lists the literals of type xsd:boolean.">
- <tr>
+ <tbody><tr>
<th>Literal</th>
<th>Value</th>
</tr>
@@ -859,30 +1231,30 @@
<td align="center"><“<code>0</code>”, <code>xsd:boolean</code>></td>
<td align="center"><em><strong>false</strong></em></td>
</tr>
- </table>
+ </tbody></table>
-<section id="xsd-datatypes">
- <h3>The XML Schema Built-in Datatypes</h3>
+<div id="xsd-datatypes" typeof="bibo:Chapter" about="#xsd-datatypes" class="section">
+ <h3><span class="secno">5.1 </span>The XML Schema Built-in Datatypes</h3>
- <p><a title="IRI">IRIs</a> of the form
+ <p><a title="IRI" href="#dfn-iri" class="internalDFN">IRIs</a> of the form
<code>http://www.w3.org/2001/XMLSchema#<em>xxx</em></code>,
where <code><em>xxx</em></code>
is the name of a datatype, denote the built-in datatypes defined in
<em><a href="http://www.w3.org/TR/xmlschema11-2/">XML Schema 1.1 Part 2:
- Datatypes</a></em> [[!XMLSCHEMA11-2]]. The XML Schema built-in types
+ Datatypes</a></em> [<cite><a class="bibref" rel="biblioentry" href="#bib-XMLSCHEMA11-2">XMLSCHEMA11-2</a></cite>]. The XML Schema built-in types
listed in the following table are the
- <dfn>RDF-compatible XSD types</dfn>. Their use is RECOMMENDED.</p>
+ <dfn id="dfn-rdf-compatible-xsd-types">RDF-compatible XSD types</dfn>. Their use is <em class="rfc2119" title="recommended">recommended</em>.</p>
<table rules="all" summary="A list of the RDF-compatible XSD types, with short descriptions">
- <tr><th></th><th>Datatype</th><th>Value space (informative)</th></tr>
+ <tbody><tr><th></th><th>Datatype</th><th>Value space (informative)</th></tr>
<tr><th rowspan="4">Core types</th><td><a href="http://www.w3.org/TR/xmlschema11-2/#string"><code>xsd:string</code></a></td><td>Character strings</td></tr>
<tr><td><a href="http://www.w3.org/TR/xmlschema11-2/#boolean"><code>xsd:boolean</code></a></td><td>true, false</td></tr>
<tr><td><a href="http://www.w3.org/TR/xmlschema11-2/#decimal"><code>xsd:decimal</code></a></td><td>Arbitrary-precision decimal numbers</td></tr>
<tr><td><a href="http://www.w3.org/TR/xmlschema11-2/#integer"><code>xsd:integer</code></a></td><td>Arbitrary-size integer numbers</td></tr>
- <tr><th rowspan="2">IEEE floating-point<br />numbers</th>
+ <tr><th rowspan="2">IEEE floating-point<br>numbers</th>
<td><a href="http://www.w3.org/TR/xmlschema11-2/#double"><code>xsd:double</code></a></td><td>64-bit floating point numbers incl. ±Inf, ±0, NaN</td></tr>
<tr><td><a href="http://www.w3.org/TR/xmlschema11-2/#float"><code>xsd:float</code></a></td><td>32-bit floating point numbers incl. ±Inf, ±0, NaN</td></tr>
@@ -892,7 +1264,7 @@
<tr><td><a href="http://www.w3.org/TR/xmlschema11-2/#dateTime"><code>xsd:dateTime</code></a></td><td>Date and time with or without timezone</td></tr>
<tr><td><a href="http://www.w3.org/TR/xmlschema11-2/#dateTimeStamp"><code>xsd:dateTimeStamp</code></a></td><td>Date and time with required timezone</td></tr>
- <tr><th rowspan="8">Recurring and<br />partial dates</th>
+ <tr><th rowspan="8">Recurring and<br>partial dates</th>
<td><a href="http://www.w3.org/TR/xmlschema11-2/#gYear"><code>xsd:gYear</code></a></td><td>Gregorian calendar year</td></tr>
<tr><td><a href="http://www.w3.org/TR/xmlschema11-2/#gMonth"><code>xsd:gMonth</code></a></td><td>Gregorian calendar month</td></tr>
<tr><td><a href="http://www.w3.org/TR/xmlschema11-2/#gDay"><code>xsd:gDay</code></a></td><td>Gregorian calendar day of the month</td></tr>
@@ -902,7 +1274,7 @@
<tr><td><a href="http://www.w3.org/TR/xmlschema11-2/#yearMonthDuration"><code>xsd:yearMonthDuration</code></a></td><td>Duration of time (months and years only)</td></tr>
<tr><td><a href="http://www.w3.org/TR/xmlschema11-2/#dayTimeDuration"><code>xsd:dayTimeDuration</code></a></td><td>Duration of time (days, hours, minutes, seconds only)</td></tr>
- <tr><th rowspan="12">Limited-range<br />integer numbers</th>
+ <tr><th rowspan="12">Limited-range<br>integer numbers</th>
<td><a href="http://www.w3.org/TR/xmlschema11-2/#byte"><code>xsd:byte</code></a></td><td>-128…+127 (8 bit)</td></tr>
<tr><td><a href="http://www.w3.org/TR/xmlschema11-2/#short"><code>xsd:short</code></a></td><td>-32768…+32767 (16 bit)</td></tr>
<tr><td><a href="http://www.w3.org/TR/xmlschema11-2/#int"><code>xsd:int</code></a></td><td>-2147483648…+2147483647 (32 bit)</td></tr>
@@ -922,18 +1294,18 @@
<td><a href="http://www.w3.org/TR/xmlschema11-2/#hexBinary"><code>xsd:hexBinary</code></a></td><td>Hex-encoded binary data</td></tr>
<tr><td><a href="http://www.w3.org/TR/xmlschema11-2/#base64Binary"><code>xsd:base64Binary</code></a></td><td>Base64-encoded binary data</td></tr>
- <tr><th rowspan="7">Miscellaneous<br />XSD types</th>
+ <tr><th rowspan="7">Miscellaneous<br>XSD types</th>
<td><a href="http://www.w3.org/TR/xmlschema11-2/#anyURI"><code>xsd:anyURI</code></a></td><td>Absolute or relative URIs and IRIs</td></tr>
- <tr><td><a href="http://www.w3.org/TR/xmlschema11-2/#language"><code>xsd:language</code></a></td><td>Language tags per [[BCP47]]</td></tr>
+ <tr><td><a href="http://www.w3.org/TR/xmlschema11-2/#language"><code>xsd:language</code></a></td><td>Language tags per [<cite><a class="bibref" rel="biblioentry" href="#bib-BCP47">BCP47</a></cite>]</td></tr>
<tr><td><a href="http://www.w3.org/TR/xmlschema11-2/#normalizedString"><code>xsd:normalizedString</code></a></td><td>Whitespace-normalized strings</td></tr>
<tr><td><a href="http://www.w3.org/TR/xmlschema11-2/#token"><code>xsd:token</code></a></td><td>Tokenized strings</td></tr>
<tr><td><a href="http://www.w3.org/TR/xmlschema11-2/#NMTOKEN"><code>xsd:NMTOKEN</code></a></td><td>XML NMTOKENs</td></tr>
<tr><td><a href="http://www.w3.org/TR/xmlschema11-2/#Name"><code>xsd:Name</code></a></td><td>XML Names</td></tr>
<tr><td><a href="http://www.w3.org/TR/xmlschema11-2/#NCName"><code>xsd:NCName</code></a></td><td>XML NCNames</td></tr>
- </table>
+ </tbody></table>
<p>The other built-in XML Schema datatypes are unsuitable
- for various reasons, and SHOULD NOT be used.</p>
+ for various reasons, and <em class="rfc2119" title="should not">should not</em> be used.</p>
<div class="note">
<ul>
@@ -951,21 +1323,21 @@
<a href="http://www.w3.org/TR/xmlschema11-2/#ENTITIES"><code>xsd:ENTITIES</code></a>
and
<a href="http://www.w3.org/TR/xmlschema11-2/#NMTOKENS"><code>xsd:NMTOKENS</code></a>
- are sequence-valued datatypes which do not fit the RDF <a>datatype</a>
+ are sequence-valued datatypes which do not fit the RDF <a href="#dfn-datatype" class="internalDFN">datatype</a>
model.</li>
</ul>
</div>
-</section>
+</div>
-<section id="section-html">
- <h3>The <code>rdf:HTML</code> Datatype</h3>
+<div id="section-html" typeof="bibo:Chapter" about="#section-html" class="section">
+ <h3><span class="secno">5.2 </span>The <code>rdf:HTML</code> Datatype</h3>
- <p>RDF provides for HTML content as a possible <a>literal value</a>.
+ <p>RDF provides for HTML content as a possible <a href="#dfn-literal-value" class="internalDFN">literal value</a>.
This allows markup in literal values. Such content is indicated
- in an <a>RDF graph</a> using a <a>literal</a> whose <a>datatype</a>
- is a special built-in datatype <code><dfn>rdf:HTML</dfn></code>.
+ in an <a href="#dfn-rdf-graph" class="internalDFN">RDF graph</a> using a <a href="#dfn-literal" class="internalDFN">literal</a> whose <a href="#dfn-datatype" class="internalDFN">datatype</a>
+ is a special built-in datatype <code><dfn id="dfn-rdf-html">rdf:HTML</dfn></code>.
This datatype is defined as follows:</p>
<dl>
@@ -973,29 +1345,29 @@
<dd>is <code>http://www.w3.org/1999/02/22-rdf-syntax-ns#HTML</code>.</dd>
<dt>The lexical space</dt>
- <dd>is the set of Unicode [[UNICODE]] strings.</dd>
+ <dd>is the set of Unicode [<cite><a class="bibref" rel="biblioentry" href="#bib-UNICODE">UNICODE</a></cite>] strings.</dd>
<dt>The value space</dt>
<dd>is a set of DOM
<a href="http://www.w3.org/TR/dom/#interface-documentfragment"><code>DocumentFragment</code></a>
- nodes [[!DOM4]]. Two
+ nodes [<cite><a class="bibref" rel="biblioentry" href="#bib-DOM4">DOM4</a></cite>]. Two
<a href="http://www.w3.org/TR/dom/#interface-documentfragment"><code>DocumentFragment</code></a>
nodes <em>A</em> and <em>B</em> are considered equal if and only if
the DOM method
<code><em>A</em>.<a href="http://www.w3.org/TR/dom/#dom-node-isequalnode">isEqualNode</a>(<em>B</em>)</code>
- [[!DOM4]] returns <code>true</code>.</dd>
+ [<cite><a class="bibref" rel="biblioentry" href="#bib-DOM4">DOM4</a></cite>] returns <code>true</code>.</dd>
<dt>The lexical-to-value mapping</dt>
<dd>
<ul>
<li>Let <code>domnodes</code> be the list of
- <a href="http://www.w3.org/TR/dom/#node">DOM nodes</a> [[!DOM4]]
+ <a href="http://www.w3.org/TR/dom/#node">DOM nodes</a> [<cite><a class="bibref" rel="biblioentry" href="#bib-DOM4">DOM4</a></cite>]
that result from applying the
- <a href="http://www.w3.org/TR/html5/the-end.html#parsing-html-fragments">HTML fragment parsing algorithm</a> [[!HTML5]]
- to the literal's <a>lexical form</a>, without a context element.</li>
+ <a href="http://www.w3.org/TR/html5/the-end.html#parsing-html-fragments">HTML fragment parsing algorithm</a> [<cite><a class="bibref" rel="biblioentry" href="#bib-HTML5">HTML5</a></cite>]
+ to the literal's <a href="#dfn-lexical-form" class="internalDFN">lexical form</a>, without a context element.</li>
<li>Let <code>domfrag</code> be a DOM
<a href="http://www.w3.org/TR/dom/#interface-documentfragment"><code>DocumentFragment</code></a>
- [[!DOM4]] whose <code>childNodes</code> attribute is equal to
+ [<cite><a class="bibref" rel="biblioentry" href="#bib-DOM4">DOM4</a></cite>] whose <code>childNodes</code> attribute is equal to
<code>domnodes</code></li>
<li>Return <code>domfrag.<a href="http://www.w3.org/TR/dom/#dom-node-normalize">normalize</a>()</code></li>
</ul>
@@ -1014,15 +1386,15 @@
<code>rdf:HTML</code> literal corresponding to a single text node
of the same string.</p>
-</section>
+</div>
-<section id="section-XMLLiteral">
- <h3>The <code>rdf:XMLLiteral</code> Datatype</h3>
+<div id="section-XMLLiteral" typeof="bibo:Chapter" about="#section-XMLLiteral" class="section">
+ <h3><span class="secno">5.3 </span>The <code>rdf:XMLLiteral</code> Datatype</h3>
- <p>RDF provides for XML content as a possible <a>literal value</a>.
- Such content is indicated in an <a>RDF graph</a> using a <a>literal</a>
- whose <a>datatype</a> is a special built-in datatype
- <code><dfn>rdf:XMLLiteral</dfn></code>, which is defined as follows:</p>
+ <p>RDF provides for XML content as a possible <a href="#dfn-literal-value" class="internalDFN">literal value</a>.
+ Such content is indicated in an <a href="#dfn-rdf-graph" class="internalDFN">RDF graph</a> using a <a href="#dfn-literal" class="internalDFN">literal</a>
+ whose <a href="#dfn-datatype" class="internalDFN">datatype</a> is a special built-in datatype
+ <code><dfn id="dfn-rdf-xmlliteral">rdf:XMLLiteral</dfn></code>, which is defined as follows:</p>
<dl>
<dt><a name="XMLLiteral-uri" id="XMLLiteral-uri">An IRI denoting
@@ -1035,16 +1407,16 @@
<dd>is the set of all strings which are well-balanced, self-contained
<a href="http://www.w3.org/TR/2000/REC-xml-20001006#NT-content">XML content</a>
- [[!XML10]]; and for which embedding between an arbitrary
+ [<cite><a class="bibref" rel="biblioentry" href="#bib-XML10">XML10</a></cite>]; and for which embedding between an arbitrary
XML start tag and an end tag yields a document conforming to
<a href="http://www.w3.org/TR/1999/REC-xml-names-19990114/">XML Namespaces</a>
- [[!XML-NAMES]].</dd>
+ [<cite><a class="bibref" rel="biblioentry" href="#bib-XML-NAMES">XML-NAMES</a></cite>].</dd>
<dt><a name="XMLLiteral-value-space" id="XMLLiteral-value-space">The value space</a></dt>
<dd>is a set of DOM
<a href="http://www.w3.org/TR/dom/#interface-documentfragment"><code>DocumentFragment</code></a>
- nodes [[!DOM4]]. Two
+ nodes [<cite><a class="bibref" rel="biblioentry" href="#bib-DOM4">DOM4</a></cite>]. Two
<a href="http://www.w3.org/TR/dom/#interface-documentfragment"><code>DocumentFragment</code></a>
nodes <em>A</em> and <em>B</em> are considered equal
if and only if the DOM method
@@ -1056,22 +1428,22 @@
<dd><ul>
<li>Let <code>domfrag</code> be a DOM
<a href="http://www.w3.org/TR/dom/#interface-documentfragment"><code>DocumentFragment</code></a>
- node [[!DOM4]] corresponding to the literal's
- <a>lexical form</a></li>
+ node [<cite><a class="bibref" rel="biblioentry" href="#bib-DOM4">DOM4</a></cite>] corresponding to the literal's
+ <a href="#dfn-lexical-form" class="internalDFN">lexical form</a></li>
<li>Return <code>domfrag.<a href="http://www.w3.org/TR/dom/#dom-node-normalize">normalize</a>()</code></li>
</ul></dd>
<dt><a name="XMLLiteral-canonical" id="XMLLiteral-canonical">The canonical mapping</a></dt>
<dd>defines a
<a href="http://www.w3.org/TR/xmlschema11-2/#dt-canonical-mapping">canonical lexical form</a>
- [[!XMLSCHEMA11-2]] for each member of the value space.
+ [<cite><a class="bibref" rel="biblioentry" href="#bib-XMLSCHEMA11-2">XMLSCHEMA11-2</a></cite>] for each member of the value space.
The <code>rdf:XMLLiteral</code> canonical mapping is the
<a href="http://www.w3.org/TR/2002/REC-xml-exc-c14n-20020718/#def-exclusive-XML-canonicalization-method">exclusive
XML canonicalization method</a> (<em>with comments, with empty
<a href="http://www.w3.org/TR/2002/REC-xml-exc-c14n-20020718/#def-InclusiveNamespaces-PrefixList">
- InclusiveNamespaces PrefixList</a></em>) [[!XML-EXC-C14N]].
+ InclusiveNamespaces PrefixList</a></em>) [<cite><a class="bibref" rel="biblioentry" href="#bib-XML-EXC-C14N">XML-EXC-C14N</a></cite>].
- </dl>
+ </dd></dl>
<p class="note">Any XML namespace declarations (<code>xmlns</code>),
language annotation (<code>xml:lang</code>) or base URI
@@ -1080,92 +1452,92 @@
Note that some concrete RDF syntaxes may define mechanisms
for inheriting them from the context
(e.g., <a href="http://www.w3.org/TR/rdf-syntax-grammar/#parseTypeLiteralPropertyElt"><code>@parseType="literal"</code></a>
- in RDF/XML [[RDF-SYNTAX-GRAMMAR]]).</p>
+ in RDF/XML [<cite><a class="bibref" rel="biblioentry" href="#bib-RDF-SYNTAX-GRAMMAR">RDF-SYNTAX-GRAMMAR</a></cite>]).</p>
<p class="note">Not all values of this datatype are compliant
- with XML 1.1 [[XML11]]. If compliance
+ with XML 1.1 [<cite><a class="bibref" rel="biblioentry" href="#bib-XML11">XML11</a></cite>]. If compliance
with XML 1.1 is desired, then only those values that are
<a href="http://www.w3.org/TR/xml11/#dt-fullnorm">fully
normalized</a> according to XML 1.1 should be used.</p>
-</section>
+</div>
-<section id="datatype-maps">
- <h3>Datatype Maps</h3>
+<div id="datatype-maps" typeof="bibo:Chapter" about="#datatype-maps" class="section">
+ <h3><span class="secno">5.4 </span>Datatype Maps</h3>
- <p>A <dfn>datatype map</dfn> is an implementation-defined set of
- <<a>IRI</a>, <a>datatype</a>> pairs such that no
+ <p>A <dfn id="dfn-datatype-map">datatype map</dfn> is an implementation-defined set of
+ <<a href="#dfn-iri" class="internalDFN">IRI</a>, <a href="#dfn-datatype" class="internalDFN">datatype</a>> pairs such that no
IRI appears twice in the set and the IRI denotes the datatype.
It can be seen as a function from IRIs
to datatypes.</p>
- <p>If a <a>datatype map</a> contains the IRI
+ <p>If a <a href="#dfn-datatype-map" class="internalDFN">datatype map</a> contains the IRI
<code>http://www.w3.org/1999/02/22-rdf-syntax-ns#XMLLiteral</code>,
- then it MUST be paired with the datatype
- <code><a>rdf:XMLLiteral</a></code>.</p>
+ then it <em class="rfc2119" title="must">must</em> be paired with the datatype
+ <code><a href="#dfn-rdf-xmlliteral" class="internalDFN">rdf:XMLLiteral</a></code>.</p>
- <p>If a <a>datatype map</a> contains an IRI of the form
+ <p>If a <a href="#dfn-datatype-map" class="internalDFN">datatype map</a> contains an IRI of the form
<code>http://www.w3.org/2001/XMLSchema#<em>xxx</em></code>,
- then it MUST be paired with the
- <a title="RDF-compatible XSD types">RDF-compatible XSD type</a>
- named <code>xsd:<em>xxx</em></code>.<p>
+ then it <em class="rfc2119" title="must">must</em> be paired with the
+ <a title="RDF-compatible XSD types" href="#dfn-rdf-compatible-xsd-types" class="internalDFN">RDF-compatible XSD type</a>
+ named <code>xsd:<em>xxx</em></code>.</p><p>
-</section>
+</p></div>
-<section id="section-Literal-Value">
- <h3>The Value Corresponding to a Literal</h3>
+<div id="section-Literal-Value" typeof="bibo:Chapter" about="#section-Literal-Value" class="section">
+ <h3><span class="secno">5.5 </span>The Value Corresponding to a Literal</h3>
- <p>The <dfn>literal value</dfn> associated with a <a>literal</a> is:</p>
+ <p>The <dfn id="dfn-literal-value">literal value</dfn> associated with a <a href="#dfn-literal" class="internalDFN">literal</a> is:</p>
<ol>
- <li><strong>If the literal is a <a>language-tagged string</a>,</strong>
- then the literal value is a pair consisting of its <a>lexical form</a>
- and its <a>language tag</a>, in that order.</li>
- <li><strong>If the literal's <a>datatype IRI</a> is not in the
- implementation-defined <a>datatype map</a>,</strong> then the literal value
+ <li><strong>If the literal is a <a href="#dfn-language-tagged-string" class="internalDFN">language-tagged string</a>,</strong>
+ then the literal value is a pair consisting of its <a href="#dfn-lexical-form" class="internalDFN">lexical form</a>
+ and its <a href="#dfn-language-tag" class="internalDFN">language tag</a>, in that order.</li>
+ <li><strong>If the literal's <a href="#dfn-datatype-iri" class="internalDFN">datatype IRI</a> is not in the
+ implementation-defined <a href="#dfn-datatype-map" class="internalDFN">datatype map</a>,</strong> then the literal value
is not defined by this specification.</li>
- <li>Let <em>d</em> be the <a>datatype</a> associated with the
+ <li>Let <em>d</em> be the <a href="#dfn-datatype" class="internalDFN">datatype</a> associated with the
datatype IRI in the implementation-defined datatype map.</li>
- <li><strong>If the literal's <a>lexical form</a> is in the
- <a>lexical space</a> of <em>d</em>,</strong> then the literal value
- is the result of applying the <a>lexical-to-value mapping</a>
- of <em>d</em> to the <a>lexical form</a>.</li>
+ <li><strong>If the literal's <a href="#dfn-lexical-form" class="internalDFN">lexical form</a> is in the
+ <a href="#dfn-lexical-space" class="internalDFN">lexical space</a> of <em>d</em>,</strong> then the literal value
+ is the result of applying the <a href="#dfn-lexical-to-value-mapping" class="internalDFN">lexical-to-value mapping</a>
+ of <em>d</em> to the <a href="#dfn-lexical-form" class="internalDFN">lexical form</a>.</li>
<li><strong>Otherwise,</strong> the literal is
- <dfn>ill-typed</dfn>, and no literal value can be
+ <dfn id="dfn-ill-typed">ill-typed</dfn>, and no literal value can be
associated with the literal. Such a case, while in error, is not
<em>syntactically</em> ill-formed.</li>
</ol>
<p class="note">In application contexts, comparing the
- <a title="literal value">values of literals</a> is usually
+ <a title="literal value" href="#dfn-literal-value" class="internalDFN">values of literals</a> is usually
more helpful than comparing their syntactic forms
- (<a>literal equality</a>).
- Similarly, for comparing <a title="RDF graph">RDF graphs</a>,
- semantic notions of <a>entailment</a> are usually more helpful
- than syntactic <a>graph isomorphism</a>.</p>
+ (<a href="#dfn-literal-equality" class="internalDFN">literal equality</a>).
+ Similarly, for comparing <a title="RDF graph" href="#dfn-rdf-graph" class="internalDFN">RDF graphs</a>,
+ semantic notions of <a href="#dfn-entailment" class="internalDFN">entailment</a> are usually more helpful
+ than syntactic <a href="#dfn-graph-isomorphism" class="internalDFN">graph isomorphism</a>.</p>
-</section>
+</div>
-</section>
+</div>
-<section id="section-fragID" class="informative">
- <h2>Fragment Identifiers</h2>
+<div id="section-fragID" class="informative section" typeof="bibo:Chapter" about="#section-fragID">
+ <h2><span class="secno">6 </span>Fragment Identifiers</h2><p><em>This section is non-normative.</em></p>
- <p>RDF uses <a title="IRI">IRIs</a>, which may include
- <dfn>fragment identifiers</dfn>, as resource identifiers.
+ <p>RDF uses <a title="IRI" href="#dfn-iri" class="internalDFN">IRIs</a>, which may include
+ <dfn id="dfn-fragment-identifiers">fragment identifiers</dfn>, as resource identifiers.
The semantics of fragment identifiers are
<a href="http://tools.ietf.org/html/rfc3986#section-3.5">defined in
- RFC 3986</a> [[URI]]: They identify a secondary resource
+ RFC 3986</a> [<cite><a class="bibref" rel="biblioentry" href="#bib-URI">URI</a></cite>]: They identify a secondary resource
that is usually a part of, view of, defined in, or described in
the primary resource, and the precise semantics depend on the set
of representations that might result from a retrieval action
on the primary resource.</p>
<p>This section discusses the handling of fragment identifiers
- in representations that encode <a title="RDF graph">RDF graphs</a>.</p>
+ in representations that encode <a title="RDF graph" href="#dfn-rdf-graph" class="internalDFN">RDF graphs</a>.</p>
<p>In RDF-bearing representations of a resource <code><foo></code>,
the secondary resource identified by a fragment <code>#bar</code>
@@ -1189,7 +1561,7 @@
representations of the same primary resource.</p>
<p>Likewise, RDF graphs embedded in non-RDF representations
- with mechanism such as RDFa [[RDFA-PRIMER]]
+ with mechanism such as RDFa [<cite><a class="bibref" rel="biblioentry" href="#bib-RDFA-PRIMER">RDFA-PRIMER</a></cite>]
should use fragment identifiers consistently with the semantics
imposed by the host language.
For example, if the fragment <code>#chapter1</code> identifies
@@ -1199,11 +1571,11 @@
to denote that same section in any RDFa-encoded statements
in the document.
</p>
-</section>
+</div>
-<section id="section-Acknowledgments" class="informative">
- <h2>Acknowledgments</h2>
+<div id="section-Acknowledgments" class="informative section" typeof="bibo:Chapter" about="#section-Acknowledgments">
+ <h2><span class="secno">7 </span>Acknowledgments</h2><p><em>This section is non-normative.</em></p>
<p class="issue">This section does not yet acknowledge
contributions to the RDF 1.1 version.</p>
@@ -1222,15 +1594,15 @@
<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 Schema Working Group</a>.</p>
-</section>
+</div>
-<section class="appendix informative" id="changes">
- <h2>Changes from RDF 2004</h2>
+<div class="appendix informative section" id="changes" typeof="bibo:Chapter" about="#changes">
+ <h2><span class="secno">A </span>Changes from RDF 2004</h2><p><em>This section is non-normative.</em></p>
-<section class="appendix" id="changes-wd2">
- <h3>Changes from FPWD to this version</h3>
+<div class="appendix section" id="changes-wd2" typeof="bibo:Chapter" about="#changes-wd2">
+ <h3><span class="secno">A.1 </span>Changes from FPWD to this version</h3>
<p>This section lists changes from the
<a href="http://www.w3.org/TR/2011/WD-rdf11-concepts-20110830/">First Public Working Draft (FPWD)</a>
@@ -1239,32 +1611,32 @@
<ul>
<li>2012-05-24: Moved the multigraph section to an earlier position and renamed it to “<a href="#section-dataset">RDF Datasets</a>”</li>
- <li>2012-05-17: Changed normative reference for DOM in <code><a>rdf:XMLLiteral</a></code> from [DOM3CORE] to [DOM4] as we need DOM4 anyways for <code><a>rdf:HTML</a></code></li>
- <li>2012-05-17: Added <code><a>rdf:HTML</a></code> datatype (<a href="http://www.w3.org/2011/rdf-wg/track/issues/63">ISSUE-63</a>)</li>
- <li>2012-05-17: Added <a href="http://www.w3.org/TR/xmlschema11-2/#duration"><code>xsd:duration</code></a> to list of <a>RDF-compatible XSD types</a> (<a href="http://www.w3.org/2011/rdf-wg/track/issues/88">ISSUE-88</a>)</li>
+ <li>2012-05-17: Changed normative reference for DOM in <code><a href="#dfn-rdf-xmlliteral" class="internalDFN">rdf:XMLLiteral</a></code> from [DOM3CORE] to [DOM4] as we need DOM4 anyways for <code><a href="#dfn-rdf-html" class="internalDFN">rdf:HTML</a></code></li>
+ <li>2012-05-17: Added <code><a href="#dfn-rdf-html" class="internalDFN">rdf:HTML</a></code> datatype (<a href="http://www.w3.org/2011/rdf-wg/track/issues/63">ISSUE-63</a>)</li>
+ <li>2012-05-17: Added <a href="http://www.w3.org/TR/xmlschema11-2/#duration"><code>xsd:duration</code></a> to list of <a href="#dfn-rdf-compatible-xsd-types" class="internalDFN">RDF-compatible XSD types</a> (<a href="http://www.w3.org/2011/rdf-wg/track/issues/88">ISSUE-88</a>)</li>
<li>2012-05-14: Replaced the example graph diagram in <a href="#data-model">Section 1.1</a> with a re-drawn SVG version, with support from Dominik Tomaszuk</li>
<li>2012-05-10: New <a href="#conformance">Conformance section</a> to explain that this specification is not implemented directly, but through other specifications that use our definitions</li>
- <li>2012-05-10: Simplified <code><a>rdf:XMLLiteral</a></code>'s new value space slightly after feedback from Ivan Herman and Arnaud Le Hors.</li>
+ <li>2012-05-10: Simplified <code><a href="#dfn-rdf-xmlliteral" class="internalDFN">rdf:XMLLiteral</a></code>'s new value space slightly after feedback from Ivan Herman and Arnaud Le Hors.</li>
<li>2012-05-10: Added an informative subsection on <a href="#vocabularies">RDF vocabularies and namespace IRIs</a>.</li>
<li>2012-05-09: Removed an example from the conformance section that didn't make sense any more with the modified <code>rdf:XMLLiteral</code>. Added some new issue boxes.</li>
- <li>2012-05-09: <code><a>rdf:XMLLiteral</a></code> no longer requires lexical forms to be canonicalized, and the value space is now defined in terms of [[DOM-LEVEL-3-CORE]] (<a href="https://www.w3.org/2011/rdf-wg/track/issues/13">ISSUE-13</a>)</li>
+ <li>2012-05-09: <code><a href="#dfn-rdf-xmlliteral" class="internalDFN">rdf:XMLLiteral</a></code> no longer requires lexical forms to be canonicalized, and the value space is now defined in terms of [<cite><a class="bibref" rel="biblioentry" href="#bib-DOM-LEVEL-3-CORE">DOM-LEVEL-3-CORE</a></cite>] (<a href="https://www.w3.org/2011/rdf-wg/track/issues/13">ISSUE-13</a>)</li>
<li>2012-05-09: Removed Section 3 <em>RDF Vocabulary IRI and Namespace</em>; its contents will be folded into the RDF Schema document</li>
- <li>2012-05-02: Renamed “graph equivalence” to “<a>graph isomorphism</a>” (<a href="https://www.w3.org/2011/rdf-wg/track/issues/86">ISSUE-86</a>)</li>
- <li>2012-05-02: Updated [[XMLSCHEMA11-1]] and [[XMLSCHEMA11-2]] references to the new REC versions</li>
- <li>2012-05-02: Added the new XSD 1.1 datatypes <a href="http://www.w3.org/TR/xmlschema11-2/#dayTimeDuration">xsd:dayTimeDuration</a>, <a href="http://www.w3.org/TR/xmlschema11-2/#yearMonthDuration">xsd:yearMonthDuration</a> and <a href="http://www.w3.org/TR/xmlschema11-2/#dateTimeStamp">xsd:dateTimeStamp</a> to the list of <a>RDF-compatible XSD types</a> (<a href="https://www.w3.org/2011/rdf-wg/track/issues/66">ISSUE-66</a>)</li>
+ <li>2012-05-02: Renamed “graph equivalence” to “<a href="#dfn-graph-isomorphism" class="internalDFN">graph isomorphism</a>” (<a href="https://www.w3.org/2011/rdf-wg/track/issues/86">ISSUE-86</a>)</li>
+ <li>2012-05-02: Updated [<cite><a class="bibref" rel="biblioentry" href="#bib-XMLSCHEMA11-1">XMLSCHEMA11-1</a></cite>] and [<cite><a class="bibref" rel="biblioentry" href="#bib-XMLSCHEMA11-2">XMLSCHEMA11-2</a></cite>] references to the new REC versions</li>
+ <li>2012-05-02: Added the new XSD 1.1 datatypes <a href="http://www.w3.org/TR/xmlschema11-2/#dayTimeDuration">xsd:dayTimeDuration</a>, <a href="http://www.w3.org/TR/xmlschema11-2/#yearMonthDuration">xsd:yearMonthDuration</a> and <a href="http://www.w3.org/TR/xmlschema11-2/#dateTimeStamp">xsd:dateTimeStamp</a> to the list of <a href="#dfn-rdf-compatible-xsd-types" class="internalDFN">RDF-compatible XSD types</a> (<a href="https://www.w3.org/2011/rdf-wg/track/issues/66">ISSUE-66</a>)</li>
<li>2012-04-26: Remove normative definition of “property” as it disagreed with RDF Semantics; small editorial changes.</li>
<li>2011-11-21: Updated XHTML 1.0 reference to XHTML 1.1</li>
- <li>2011-11-20: Added table of <a>RDF-compatible XSD types</a>, and definition of <a>datatype map</a>, both adapted from previous content in [[RDF-MT]]
- <li>2011-11-18: Replaced informative <em>Introduction</em> and <em>RDF Concepts</em> sections with a new extended introduction. Folded some content from <em>RDF Concepts</em> into the later normative sections, mostly as examples and notes.</li>
+ <li>2011-11-20: Added table of <a href="#dfn-rdf-compatible-xsd-types" class="internalDFN">RDF-compatible XSD types</a>, and definition of <a href="#dfn-datatype-map" class="internalDFN">datatype map</a>, both adapted from previous content in [<cite><a class="bibref" rel="biblioentry" href="#bib-RDF-MT">RDF-MT</a></cite>]
+ </li><li>2011-11-18: Replaced informative <em>Introduction</em> and <em>RDF Concepts</em> sections with a new extended introduction. Folded some content from <em>RDF Concepts</em> into the later normative sections, mostly as examples and notes.</li>
<li>2011-11-10: Changed XSD references to version 1.1</li>
<li>2011-11-10: Replaced the <a href="#section-fragID">section on fragment identifiers</a> with an updated account that follows RFC 3986</li>
<li>2011-11-09: Updated the two sections on literals to reflect the <a href="http://www.w3.org/2011/rdf-wg/track/issues/71">ISSUE-71</a> resolution that literals with language tag now have the datatype IRI <code>rdf:langString</code>. Formally introduced the term “language-tagged string”.</li>
<li>2011-11-09: Add a note that explains that #x0-#x1F are no longer allowed in simple literals
- </ul>
-</section>
+ </li></ul>
+</div>
-<section class="appendix" id="changes-fpwd">
- <h3>Changes from RDF 2004 to FPWD</h3>
+<div class="appendix section" id="changes-fpwd" typeof="bibo:Chapter" about="#changes-fpwd">
+ <h3><span class="secno">A.2 </span>Changes from RDF 2004 to FPWD</h3>
<p>This section lists changes from the
<a href="http://www.w3.org/TR/2004/REC-rdf-concepts-20040210/">2004 Recommendation of
@@ -1289,14 +1661,44 @@
<li>2011-05-25: Updated all W3C references to latest editions, and Unicode from v3 to v4</li>
<li>2011-05-24: Converted to ReSpec, changed metadata to reflect RDF 1.1</li>
</ul>
-</section>
+</div>
-</section>
+</div>
-<section id="references">
-</section>
- </body>
-</html>
+
+
+
+<div id="references" class="appendix section" typeof="bibo:Chapter" about="#references"><h2><span class="secno">B </span>References</h2>
+<div id="normative-references" typeof="bibo:Chapter" about="#normative-references" class="section"><h3><span class="secno">B.1 </span>Normative references</h3><dl class="bibliography" about=""><dt id="bib-BCP47">[BCP47]</dt><dd rel="dcterms:requires">A. Phillips; M. Davis. <a href="http://tools.ietf.org/html/bcp47"><cite>Tags for Identifying Languages</cite></a> September 2009. IETF Best Current Practice. URL: <a href="http://tools.ietf.org/html/bcp47">http://tools.ietf.org/html/bcp47</a>
+</dd><dt id="bib-DOM4">[DOM4]</dt><dd rel="dcterms:requires">Anne van Kesteren; Aryeh Gregor; Ms2ger. <a href="http://www.w3.org/TR/2012/WD-dom-20120105/"><cite>DOM4.</cite></a> 5 January 2012. W3C Working Draft. (Work in progress.) URL: <a href="http://www.w3.org/TR/2012/WD-dom-20120105/">http://www.w3.org/TR/2012/WD-dom-20120105/</a>
+</dd><dt id="bib-HTML5">[HTML5]</dt><dd rel="dcterms:requires">Ian Hickson; David Hyatt. <a href="http://www.w3.org/TR/html5"><cite>HTML5.</cite></a> 25 May 2011. W3C Working Draft. (Work in progress.) URL: <a href="http://www.w3.org/TR/html5">http://www.w3.org/TR/html5</a>
+</dd><dt id="bib-IRI">[IRI]</dt><dd rel="dcterms:requires">M. Duerst, M. Suignard. <a href="http://www.ietf.org/rfc/rfc3987.txt"><cite>Internationalized Resource Identifiers (IRI).</cite></a> January 2005. Internet RFC 3987. URL: <a href="http://www.ietf.org/rfc/rfc3986.txt">http://www.ietf.org/rfc/rfc3987.txt</a>
+</dd><dt id="bib-NFC">[NFC]</dt><dd rel="dcterms:requires">M. Davis, Ken Whistler. <a href="http://www.unicode.org/reports/tr15/"><cite>TR15, Unicode Normalization Forms.</cite></a>. 17 September 2010, URL: <a href="http://www.unicode.org/reports/tr15/">http://www.unicode.org/reports/tr15/</a>
+</dd><dt id="bib-RFC2119">[RFC2119]</dt><dd rel="dcterms:requires">S. Bradner. <a href="http://www.ietf.org/rfc/rfc2119.txt"><cite>Key words for use in RFCs to Indicate Requirement Levels.</cite></a> March 1997. Internet RFC 2119. URL: <a href="http://www.ietf.org/rfc/rfc2119.txt">http://www.ietf.org/rfc/rfc2119.txt</a>
+</dd><dt id="bib-UNICODE">[UNICODE]</dt><dd rel="dcterms:requires">The Unicode Consortium. <a href="http://www.unicode.org/unicode/standard/versions/enumeratedversions.html"><cite>The Unicode Standard.</cite></a> 2003. Defined by: The Unicode Standard, Version 4.0 (Boston, MA, Addison-Wesley, ISBN 0-321-18578-1), as updated from time to time by the publication of new versions URL: <a href="http://www.unicode.org/unicode/standard/versions/enumeratedversions.html">http://www.unicode.org/unicode/standard/versions/enumeratedversions.html</a>
+</dd><dt id="bib-XML-EXC-C14N">[XML-EXC-C14N]</dt><dd rel="dcterms:requires">Donald E. Eastlake 3rd; Joseph Reagle; John Boyer. <a href="http://www.w3.org/TR/2002/REC-xml-exc-c14n-20020718/"><cite>Exclusive XML Canonicalization Version 1.0.</cite></a> 18 July 2002. W3C Recommendation. URL: <a href="http://www.w3.org/TR/2002/REC-xml-exc-c14n-20020718/">http://www.w3.org/TR/2002/REC-xml-exc-c14n-20020718/</a>
+</dd><dt id="bib-XML-NAMES">[XML-NAMES]</dt><dd rel="dcterms:requires">Richard Tobin; et al. <a href="http://www.w3.org/TR/2009/REC-xml-names-20091208/"><cite>Namespaces in XML 1.0 (Third Edition).</cite></a> 8 December 2009. W3C Recommendation. URL: <a href="http://www.w3.org/TR/2009/REC-xml-names-20091208/">http://www.w3.org/TR/2009/REC-xml-names-20091208/</a>
+</dd><dt id="bib-XML10">[XML10]</dt><dd rel="dcterms:requires">C. M. Sperberg-McQueen; et al. <a href="http://www.w3.org/TR/2008/REC-xml-20081126/"><cite>Extensible Markup Language (XML) 1.0 (Fifth Edition).</cite></a> 26 November 2008. W3C Recommendation. URL: <a href="http://www.w3.org/TR/2008/REC-xml-20081126/">http://www.w3.org/TR/2008/REC-xml-20081126/</a>
+</dd><dt id="bib-XMLSCHEMA11-2">[XMLSCHEMA11-2]</dt><dd rel="dcterms:requires">Henry S. Thompson; et al. <a href="http://www.w3.org/TR/2012/REC-xmlschema11-2-20120405/"><cite>W3C XML Schema Definition Language (XSD) 1.1 Part 2: Datatypes.</cite></a> 5 April 2012. W3C Recommendation URL: <a href="http://www.w3.org/TR/2012/REC-xmlschema11-2-20120405/">http://www.w3.org/TR/2012/REC-xmlschema11-2-20120405/</a>
+</dd></dl></div><div id="informative-references" typeof="bibo:Chapter" about="#informative-references" class="section"><h3><span class="secno">B.2 </span>Informative references</h3><dl class="bibliography" about=""><dt id="bib-CHARMOD">[CHARMOD]</dt><dd rel="dcterms:references">Martin J. Dürst; et al. <a href="http://www.w3.org/TR/2005/REC-charmod-20050215"><cite>Character Model for the World Wide Web 1.0: Fundamentals.</cite></a> 15 February 2005. W3C Recommendation. URL: <a href="http://www.w3.org/TR/2005/REC-charmod-20050215">http://www.w3.org/TR/2005/REC-charmod-20050215</a>
+</dd><dt id="bib-COOLURIS">[COOLURIS]</dt><dd rel="dcterms:references">Richard Cyganiak; Leo Sauermann. <a href="http://www.w3.org/TR/2008/NOTE-cooluris-20081203"><cite>Cool URIs for the Semantic Web.</cite></a> 3 December 2008. W3C Note. URL: <a href="http://www.w3.org/TR/2008/NOTE-cooluris-20081203">http://www.w3.org/TR/2008/NOTE-cooluris-20081203</a>
+</dd><dt id="bib-DOM-LEVEL-3-CORE">[DOM-LEVEL-3-CORE]</dt><dd rel="dcterms:references">Gavin Nicol; et al. <a href="http://www.w3.org/TR/2004/REC-DOM-Level-3-Core-20040407"><cite>Document Object Model (DOM) Level 3 Core Specification.</cite></a> 7 April 2004. W3C Recommendation. URL: <a href="http://www.w3.org/TR/2004/REC-DOM-Level-3-Core-20040407">http://www.w3.org/TR/2004/REC-DOM-Level-3-Core-20040407</a>
+</dd><dt id="bib-N-TRIPLES">[N-TRIPLES]</dt><dd rel="dcterms:references">Jan Grant; Dave Beckett. <a href="http://www.w3.org/TR/rdf-testcases/#ntriples"><cite>N-Triples</cite></a> 10 February 2004. W3C Recommendation. URL: <a href="http://www.w3.org/TR/rdf-testcases/#ntriples">http://www.w3.org/TR/rdf-testcases/#ntriples</a>
+</dd><dt id="bib-RDF-MT">[RDF-MT]</dt><dd rel="dcterms:references">Patrick Hayes. <a href="http://www.w3.org/TR/2004/REC-rdf-mt-20040210"><cite>RDF Semantics.</cite></a> 10 February 2004. W3C Recommendation. URL: <a href="http://www.w3.org/TR/2004/REC-rdf-mt-20040210">http://www.w3.org/TR/2004/REC-rdf-mt-20040210</a>
+</dd><dt id="bib-RDF-PRIMER">[RDF-PRIMER]</dt><dd rel="dcterms:references">Frank Manola; Eric Miller. <a href="http://www.w3.org/TR/2004/REC-rdf-primer-20040210/"><cite>RDF Primer.</cite></a> 10 February 2004. W3C Recommendation. URL: <a href="http://www.w3.org/TR/2004/REC-rdf-primer-20040210/">http://www.w3.org/TR/2004/REC-rdf-primer-20040210/</a>
+</dd><dt id="bib-RDF-SCHEMA">[RDF-SCHEMA]</dt><dd rel="dcterms:references">Dan Brickley; Ramanathan V. Guha. <a href="http://www.w3.org/TR/2004/REC-rdf-schema-20040210"><cite>RDF Vocabulary Description Language 1.0: RDF Schema.</cite></a> 10 February 2004. W3C Recommendation. URL: <a href="http://www.w3.org/TR/2004/REC-rdf-schema-20040210">http://www.w3.org/TR/2004/REC-rdf-schema-20040210</a>
+</dd><dt id="bib-RDF-SPARQL-QUERY">[RDF-SPARQL-QUERY]</dt><dd rel="dcterms:references">Andy Seaborne; Eric Prud'hommeaux. <a href="http://www.w3.org/TR/2008/REC-rdf-sparql-query-20080115"><cite>SPARQL Query Language for RDF.</cite></a> 15 January 2008. W3C Recommendation. URL: <a href="http://www.w3.org/TR/2008/REC-rdf-sparql-query-20080115">http://www.w3.org/TR/2008/REC-rdf-sparql-query-20080115</a>
+</dd><dt id="bib-RDF-SYNTAX-GRAMMAR">[RDF-SYNTAX-GRAMMAR]</dt><dd rel="dcterms:references">Dave Beckett. <a href="http://www.w3.org/TR/2004/REC-rdf-syntax-grammar-20040210"><cite>RDF/XML Syntax Specification (Revised).</cite></a> 10 February 2004. W3C Recommendation. URL: <a href="http://www.w3.org/TR/2004/REC-rdf-syntax-grammar-20040210">http://www.w3.org/TR/2004/REC-rdf-syntax-grammar-20040210</a>
+</dd><dt id="bib-RDF-TESTCASES">[RDF-TESTCASES]</dt><dd rel="dcterms:references">Jan Grant; Dave Beckett. <a href="http://www.w3.org/TR/2004/REC-rdf-testcases-20040210"><cite>RDF Test Cases.</cite></a> 10 February 2004. W3C Recommendation. URL: <a href="http://www.w3.org/TR/2004/REC-rdf-testcases-20040210">http://www.w3.org/TR/2004/REC-rdf-testcases-20040210</a>
+</dd><dt id="bib-RDFA-PRIMER">[RDFA-PRIMER]</dt><dd rel="dcterms:references">Ben Adida, Ivan Herman, Manu Sporny. <a href="http://www.w3.org/TR/2012/WD-rdfa-primer-20120508/"><cite>RDFa 1.1 Primer.</cite></a> 08 May 2012. W3C Working Draft. URL: <a href="http://www.w3.org/TR/2012/WD-rdfa-primer-20120508/">http://www.w3.org/TR/2012/WD-rdfa-primer-20120508/</a>
+</dd><dt id="bib-SWBP-N-ARYRELATIONS">[SWBP-N-ARYRELATIONS]</dt><dd rel="dcterms:references">Natasha Noy; Alan Rector. <a href="http://www.w3.org/TR/2006/NOTE-swbp-n-aryRelations-20060412"><cite>Defining N-ary Relations on the Semantic Web.</cite></a> 12 April 2006. W3C Note. URL: <a href="http://www.w3.org/TR/2006/NOTE-swbp-n-aryRelations-20060412">http://www.w3.org/TR/2006/NOTE-swbp-n-aryRelations-20060412</a>
+</dd><dt id="bib-TURTLE-TR">[TURTLE-TR]</dt><dd rel="dcterms:references">Eric Prud'hommeaux, Gavin Carothers. <a href="http://www.w3.org/TR/2011/WD-turtle-20110809/"><cite>Turtle: Terse RDF Triple Language.</cite></a> 09 August 2011. W3C Working Draft. URL: <a href="http://www.w3.org/TR/2011/WD-turtle-20110809/">http://www.w3.org/TR/2011/WD-turtle-20110809/</a>
+</dd><dt id="bib-URI">[URI]</dt><dd rel="dcterms:references">T. Berners-Lee; R. Fielding; L. Masinter. <a href="http://www.ietf.org/rfc/rfc3986.txt"><cite>Uniform Resource Identifiers (URI): generic syntax.</cite></a> January 2005. Internet RFC 3986. URL: <a href="http://www.ietf.org/rfc/rfc3986.txt">http://www.ietf.org/rfc/rfc3986.txt</a>
+</dd><dt id="bib-WEBARCH">[WEBARCH]</dt><dd rel="dcterms:references">Norman Walsh; Ian Jacobs. <a href="http://www.w3.org/TR/2004/REC-webarch-20041215/"><cite>Architecture of the World Wide Web, Volume One.</cite></a> 15 December 2004. W3C Recommendation. URL: <a href="http://www.w3.org/TR/2004/REC-webarch-20041215/">http://www.w3.org/TR/2004/REC-webarch-20041215/</a>
+</dd><dt id="bib-WELL-KNOWN">[WELL-KNOWN]</dt><dd rel="dcterms:references">M. Nottingham; E. Hammer-Lahav. <a href="http://tools.ietf.org/html/rfc5785"><cite>Defining Well-Known Uniform Resource Identifiers (URIs).</cite></a> April 2010. Internet RFC 5785. URL: <a href="http://tools.ietf.org/html/rfc5785">http://tools.ietf.org/html/rfc5785</a>
+</dd><dt id="bib-XML11">[XML11]</dt><dd rel="dcterms:references">Eve Maler; et al. <a href="http://www.w3.org/TR/2006/REC-xml11-20060816"><cite>Extensible Markup Language (XML) 1.1 (Second Edition).</cite></a> 16 August 2006. W3C Recommendation. URL: <a href="http://www.w3.org/TR/2006/REC-xml11-20060816">http://www.w3.org/TR/2006/REC-xml11-20060816</a>
+</dd><dt id="bib-XMLSCHEMA11-1">[XMLSCHEMA11-1]</dt><dd rel="dcterms:references">C. M. Sperberg-McQueen; Henry S. Thompson; Shudi Gao. <a href="http://www.w3.org/TR/2012/REC-xmlschema11-1-20120405/"><cite>W3C XML Schema Definition Language (XSD) 1.1 Part 1: Structures.</cite></a> 5 April 2012. W3C Recommendation URL: <a href="http://www.w3.org/TR/2012/REC-xmlschema11-1-20120405/">http://www.w3.org/TR/2012/REC-xmlschema11-1-20120405/</a>
+</dd></dl></div></div></body></html>