moved to xhtml
authorYves Lafon <ylafon@w3.org>
Thu, 24 Jan 2013 23:00:11 +0100
changeset 45 eb4c45eb9bd2
parent 44 ae2c3bbfadeb
child 46 a56c74d03222
moved to xhtml
TR/ldp-ucr.html
--- a/TR/ldp-ucr.html	Thu Jan 24 22:51:44 2013 +0100
+++ b/TR/ldp-ucr.html	Thu Jan 24 23:00:11 2013 +0100
@@ -1,13 +1,16 @@
-<!DOCTYPE html>
-<html lang="en" dir="ltr" prefix="bibo: http://purl.org/ontology/bibo/" typeof="bibo:Document">
+<?xml version='1.0' encoding='UTF-8'?>
+<!DOCTYPE html PUBLIC '-//W3C//DTD XHTML+RDFa 1.1//EN' 'http://www.w3.org/MarkUp/DTD/xhtml-rdfa-2.dtd'>
+<html dir="ltr" xmlns="http://www.w3.org/1999/xhtml" prefix='bibo: http://purl.org/ontology/bibo/' typeof="bibo:Document">
 <head>
     <title>Linked Data Platform Use Cases and Requirements</title>
-    <meta http-equiv="Content-Type" content="text/html;charset=utf-8">
-    <!-- 
+    <meta content="text/html;charset=utf-8" http-equiv="Content-Type" />
+    
+<!-- 
       === NOTA BENE ===
       For the three scripts below, if your spec resides on dev.w3 you can check them
       out in the same tree and use relative links so that they'll work offline,
      -->
+
      
     
     <style type="text/css">
@@ -175,14 +178,16 @@
 aside.example div.example div.example-title {
     color: #999;
 }
-</style><link href="http://www.w3.org/StyleSheets/TR/W3C-WD" rel="stylesheet"><!--[if lt IE 9]><script src='http://www.w3.org/2008/site/js/html5shiv.js'></script><![endif]--></head>
+</style><link rel="stylesheet" href="http://www.w3.org/StyleSheets/TR/W3C-WD" />
+<!--[if lt IE 9]><script src='http://www.w3.org/2008/site/js/html5shiv.js'></script><![endif]-->
+</head>
 <body><div class="head">
   <p>
     
-      <a href="http://www.w3.org/"><img src="http://www.w3.org/Icons/w3c_home" alt="W3C" height="48" width="72"></a>
+      <a href="http://www.w3.org/"><img width="72" height="48" alt="W3C" src="http://www.w3.org/Icons/w3c_home" /></a>
     
   </p>
-  <h1 class="title" id="title">Linked Data Platform Use Cases and Requirements</h1>
+  <h1 id="title" class="title">Linked Data Platform Use Cases and Requirements</h1>
   
   <h2 id="w3c-working-draft-29-january-2013"><abbr title="World Wide Web Consortium">W3C</abbr> Working Draft 29 January 2013</h2>
   <dl>
@@ -205,9 +210,9 @@
     
     
     <dt>Editors:</dt>
-    <dd rel="bibo:editor" inlist=""><span typeof="foaf:Person"><a rel="foaf:homepage" property="foaf:name" content="Steve Battle" href="http://stevebattle.me">Steve Battle</a>, <a rel="foaf:workplaceHomepage" href="http://www.sysemia.com">Sysemia Limited</a></span>
+    <dd inlist="" rel="bibo:editor"><span typeof="foaf:Person"><a href="http://stevebattle.me" content="Steve Battle" property="foaf:name" rel="foaf:homepage">Steve Battle</a>, <a href="http://www.sysemia.com" rel="foaf:workplaceHomepage">Sysemia Limited</a></span>
 </dd>
-<dd rel="bibo:editor" inlist=""><span typeof="foaf:Person"><a rel="foaf:homepage" property="foaf:name" content="Steve Speicher" href="http://stevespeicher.me">Steve Speicher</a>, <a rel="foaf:workplaceHomepage" href="http://ibm.com/">IBM Corporation</a></span>
+<dd inlist="" rel="bibo:editor"><span typeof="foaf:Person"><a href="http://stevespeicher.me" content="Steve Speicher" property="foaf:name" rel="foaf:homepage">Steve Speicher</a>, <a href="http://ibm.com/" rel="foaf:workplaceHomepage">IBM Corporation</a></span>
 </dd>
 
     
@@ -231,13 +236,13 @@
       </p>
     
   
-  <hr>
+  <hr />
 </div>
-<section rel="bibo:chapter" resource="#abstract" typeof="bibo:Chapter" datatype="" property="dcterms:abstract" class="introductory" id="abstract"><h2>Abstract</h2><p>
+<section id="abstract" class="introductory" property="dcterms:abstract" datatype="" typeof="bibo:Chapter" resource="#abstract" rel="bibo:chapter"><h2>Abstract</h2><p>
 A set of user stories, use cases, scenarios and requirements that motivate a simple 
 read-write Linked Data architecture, based on HTTP access to web 
 resources that describe their state using RDF.
-</p></section><section rel="bibo:chapter" resource="#sotd" typeof="bibo:Chapter" id="sotd" class="introductory"><h2>Status of This Document</h2>
+</p></section><section class="introductory" id="sotd" typeof="bibo:Chapter" resource="#sotd" rel="bibo:chapter"><h2>Status of This Document</h2>
   
     
       
@@ -251,17 +256,11 @@
         <p>
           This document was published by the <a href="http://www.w3.org/2012/ldp">Linked Data Platform Working Group</a> as a <a href="http://www.w3.org/2005/10/Process-20051014/tr.html#first-wd">First Public Working Draft</a>.
           
-            This document is intended to become a <abbr title="World Wide Web Consortium">W3C</abbr> Recommendation.
-          
-          
           If you wish to make comments regarding this document, please send them to 
           <a href="mailto:[email protected]">[email protected]</a> 
           (<a href="mailto:[email protected]?subject=subscribe">subscribe</a>,
           <a href="http://lists.w3.org/Archives/Public/public-ldp-wg/">archives</a>).
           
-          
-          
-          
         All comments are welcome.
         
         
@@ -271,7 +270,6 @@
             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 
@@ -280,7 +278,7 @@
           
           
             
-              <abbr title="World Wide Web Consortium">W3C</abbr> maintains a <a href="http://www.w3.org/2004/01/pp-impl/55082/status" rel="disclosure">public list of any patent disclosures</a> 
+              <abbr title="World Wide Web Consortium">W3C</abbr> maintains a <a rel="disclosure" href="http://www.w3.org/2004/01/pp-impl/55082/status">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
@@ -294,35 +292,37 @@
       
     
   
-</section><section id="toc"><h2 class="introductory">Table of Contents</h2><ul class="toc"><li class="tocline"><a class="tocxref" href="#scope-and-motivation"><span class="secno">1. </span>Scope and Motivation</a></li><li class="tocline"><a class="tocxref" href="#organization-of-this-document"><span class="secno">2. </span>Organization of this Document</a></li><li class="tocline"><a class="tocxref" href="#user-stories"><span class="secno">3. </span>User Stories</a><ul class="toc"><li class="tocline"><a class="tocxref" href="#maintaining-social-contact-information"><span class="secno">3.1 </span>Maintaining Social Contact Information</a></li><li class="tocline"><a class="tocxref" href="#keeping-track-of-personal-and-business-relationships"><span class="secno">3.2 </span>Keeping Track of Personal and
-			Business Relationships</a></li><li class="tocline"><a class="tocxref" href="#system-and-software-development-tool-integration"><span class="secno">3.3 </span>System and Software Development
-			Tool Integration</a></li><li class="tocline"><a class="tocxref" href="#library-linked-data"><span class="secno">3.4 </span>Library Linked Data</a></li><li class="tocline"><a class="tocxref" href="#municipality-operational-monitoring"><span class="secno">3.5 </span>Municipality Operational
-			Monitoring</a></li><li class="tocline"><a class="tocxref" href="#healthcare"><span class="secno">3.6 </span>Healthcare</a></li><li class="tocline"><a class="tocxref" href="#metadata-enrichment-in-broadcasting"><span class="secno">3.7 </span>Metadata Enrichment in Broadcasting</a></li><li class="tocline"><a class="tocxref" href="#aggregation-and-mashups-of-infrastructure-data"><span class="secno">3.8 </span>Aggregation and Mashups of Infrastructure Data</a></li><li class="tocline"><a class="tocxref" href="#sharing-payload-of-rdf-data-among-low-end-devices"><span class="secno">3.9 </span>Sharing payload of RDF data among low-end devices</a></li><li class="tocline"><a class="tocxref" href="#sharing-binary-resources-and-metadata"><span class="secno">3.10 </span>Sharing Binary Resources and Metadata</a></li><li class="tocline"><a class="tocxref" href="#data-catalogs"><span class="secno">3.11 </span>Data Catalogs</a></li><li class="tocline"><a class="tocxref" href="#constrained-devices-and-networks"><span class="secno">3.12 </span>Constrained Devices and Networks</a></li><li class="tocline"><a class="tocxref" href="#services-supporting-the-process-of-science"><span class="secno">3.13 </span>Services Supporting the Process
-			of Science</a></li><li class="tocline"><a class="tocxref" href="#project-membership-information-information-evolution"><span class="secno">3.14 </span>Project Membership Information: Information Evolution</a></li><li class="tocline"><a class="tocxref" href="#cloud-infrastructure-management"><span class="secno">3.15 </span>Cloud Infrastructure Management</a></li></ul></li><li class="tocline"><a class="tocxref" href="#use-cases"><span class="secno">4. </span>Use Cases</a><ul class="toc"><li class="tocline"><a class="tocxref" href="#use-case-manage-containers"><span class="secno">4.1 </span>Use Case: Manage containers</a><ul class="toc"><li class="tocline"><a class="tocxref" href="#primary-scenario-create-container"><span class="secno">4.1.1 </span>Primary scenario: create
-			container</a></li><li class="tocline"><a class="tocxref" href="#alternative-scenario-create-a-nested-container"><span class="secno">4.1.2 </span>Alternative scenario: create a
-			nested container</a></li></ul></li><li class="tocline"><a class="tocxref" href="#use-case-manage-resources"><span class="secno">4.2 </span>Use Case: Manage resources</a><ul class="toc"><li class="tocline"><a class="tocxref" href="#primary-scenario-create-resource"><span class="secno">4.2.1 </span>Primary scenario: create resource</a></li><li class="tocline"><a class="tocxref" href="#alternative-scenario-delete-resource"><span class="secno">4.2.2 </span>Alternative scenario: delete
-			resource</a></li><li class="tocline"><a class="tocxref" href="#alternative-scenario-moving-contained-resources"><span class="secno">4.2.3 </span>Alternative scenario: moving
-			contained resources</a></li></ul></li><li class="tocline"><a class="tocxref" href="#use-case-retrieve-resource-description"><span class="secno">4.3 </span>Use Case: Retrieve resource
-			description</a><ul class="toc"><li class="tocline"><a class="tocxref" href="#primary-scenario"><span class="secno">4.3.1 </span>Primary scenario</a></li><li class="tocline"><a class="tocxref" href="#alternative-scenario-retrieve-description-of-a-non-document-resource"><span class="secno">4.3.2 </span>Alternative scenario: retrieve
-			description of a non-document resource</a></li></ul></li><li class="tocline"><a class="tocxref" href="#use-case-update-existing-resource"><span class="secno">4.4 </span>Use Case: Update existing resource</a><ul class="toc"><li class="tocline"><a class="tocxref" href="#primary-scenario-enrichment"><span class="secno">4.4.1 </span>Primary scenario: enrichment</a></li><li class="tocline"><a class="tocxref" href="#alternative-scenario-selective-update-of-a-resource"><span class="secno">4.4.2 </span>Alternative scenario: selective
-			update of a resource</a></li></ul></li><li class="tocline"><a class="tocxref" href="#use-case-determine-if-a-resource-has-changed"><span class="secno">4.5 </span>Use Case: Determine if a resource has
-			changed</a><ul class="toc"><li class="tocline"><a class="tocxref" href="#primary-scenario-1"><span class="secno">4.5.1 </span>Primary scenario</a></li></ul></li><li class="tocline"><a class="tocxref" href="#use-case-aggregate-resources"><span class="secno">4.6 </span>Use Case: Aggregate resources</a><ul class="toc"><li class="tocline"><a class="tocxref" href="#primary-scenario-add-a-resource-to-a-collection"><span class="secno">4.6.1 </span>Primary scenario: add a resource
-			to a collection</a></li><li class="tocline"><a class="tocxref" href="#alternative-scenario-add-a-resource-to-multiple-collections"><span class="secno">4.6.2 </span>Alternative scenario: add a
-			resource to multiple collections</a></li></ul></li><li class="tocline"><a class="tocxref" href="#use-case-filter-resource-description"><span class="secno">4.7 </span>Use Case: Filter resource description</a><ul class="toc"><li class="tocline"><a class="tocxref" href="#primary-scenario-retrieve-collection-level-description"><span class="secno">4.7.1 </span>Primary scenario: retrieve
-			collection-level description</a></li><li class="tocline"><a class="tocxref" href="#alternative-scenario-retrieve-item-level-description-of-a-collection"><span class="secno">4.7.2 </span>Alternative scenario: retrieve
-			item-level description of a collection</a></li></ul></li><li class="tocline"><a class="tocxref" href="#use-case-manage-media-resources"><span class="secno">4.8 </span>Use Case: Manage media resources</a><ul class="toc"><li class="tocline"><a class="tocxref" href="#primary-scenario-access-media-resources"><span class="secno">4.8.1 </span>Primary scenario: access media
-			resources</a></li><li class="tocline"><a class="tocxref" href="#alternative-scenario-media-resource-attachments"><span class="secno">4.8.2 </span>Alternative scenario:
-			media-resource attachments</a></li></ul></li></ul></li><li class="tocline"><a class="tocxref" href="#requirements"><span class="secno">5. </span>Requirements</a><ul class="toc"><li class="tocline"><a class="tocxref" href="#functional-requirements"><span class="secno">5.1 </span>Functional Requirements</a></li><li class="tocline"><a class="tocxref" href="#non-functional-requirements"><span class="secno">5.2 </span>Non-Functional Requirements</a></li></ul></li><li class="tocline"><a class="tocxref" href="#acknowledgements"><span class="secno">A. </span>Acknowledgements</a></li><li class="tocline"><a class="tocxref" href="#history"><span class="secno">B. </span>Change History</a></li><li class="tocline"><a class="tocxref" href="#references"><span class="secno">C. </span>References</a><ul class="toc"><li class="tocline"><a class="tocxref" href="#informative-references"><span class="secno">C.1 </span>Informative references</a></li></ul></li></ul></section>
+</section><section id="toc"><h2 class="introductory">Table of Contents</h2><ul class="toc"><li class="tocline"><a href="#scope-and-motivation" class="tocxref"><span class="secno">1. </span>Scope and Motivation</a></li><li class="tocline"><a href="#organization-of-this-document" class="tocxref"><span class="secno">2. </span>Organization of this Document</a></li><li class="tocline"><a href="#user-stories" class="tocxref"><span class="secno">3. </span>User Stories</a><ul class="toc"><li class="tocline"><a href="#maintaining-social-contact-information" class="tocxref"><span class="secno">3.1 </span>Maintaining Social Contact Information</a></li><li class="tocline"><a href="#keeping-track-of-personal-and-business-relationships" class="tocxref"><span class="secno">3.2 </span>Keeping Track of Personal and
+			Business Relationships</a></li><li class="tocline"><a href="#system-and-software-development-tool-integration" class="tocxref"><span class="secno">3.3 </span>System and Software Development
+			Tool Integration</a></li><li class="tocline"><a href="#library-linked-data" class="tocxref"><span class="secno">3.4 </span>Library Linked Data</a></li><li class="tocline"><a href="#municipality-operational-monitoring" class="tocxref"><span class="secno">3.5 </span>Municipality Operational
+			Monitoring</a></li><li class="tocline"><a href="#healthcare" class="tocxref"><span class="secno">3.6 </span>Healthcare</a></li><li class="tocline"><a href="#metadata-enrichment-in-broadcasting" class="tocxref"><span class="secno">3.7 </span>Metadata Enrichment in Broadcasting</a></li><li class="tocline"><a href="#aggregation-and-mashups-of-infrastructure-data" class="tocxref"><span class="secno">3.8 </span>Aggregation and Mashups of Infrastructure Data</a></li><li class="tocline"><a href="#sharing-payload-of-rdf-data-among-low-end-devices" class="tocxref"><span class="secno">3.9 </span>Sharing payload of RDF data among low-end devices</a></li><li class="tocline"><a href="#sharing-binary-resources-and-metadata" class="tocxref"><span class="secno">3.10 </span>Sharing Binary Resources and Metadata</a></li><li class="tocline"><a href="#data-catalogs" class="tocxref"><span class="secno">3.11 </span>Data Catalogs</a></li><li class="tocline"><a href="#constrained-devices-and-networks" class="tocxref"><span class="secno">3.12 </span>Constrained Devices and Networks</a></li><li class="tocline"><a href="#services-supporting-the-process-of-science" class="tocxref"><span class="secno">3.13 </span>Services Supporting the Process
+			of Science</a></li><li class="tocline"><a href="#project-membership-information-information-evolution" class="tocxref"><span class="secno">3.14 </span>Project Membership Information: Information Evolution</a></li><li class="tocline"><a href="#cloud-infrastructure-management" class="tocxref"><span class="secno">3.15 </span>Cloud Infrastructure Management</a></li></ul></li><li class="tocline"><a href="#use-cases" class="tocxref"><span class="secno">4. </span>Use Cases</a><ul class="toc"><li class="tocline"><a href="#use-case-manage-containers" class="tocxref"><span class="secno">4.1 </span>Use Case: Manage containers</a><ul class="toc"><li class="tocline"><a href="#primary-scenario-create-container" class="tocxref"><span class="secno">4.1.1 </span>Primary scenario: create
+			container</a></li><li class="tocline"><a href="#alternative-scenario-create-a-nested-container" class="tocxref"><span class="secno">4.1.2 </span>Alternative scenario: create a
+			nested container</a></li></ul></li><li class="tocline"><a href="#use-case-manage-resources" class="tocxref"><span class="secno">4.2 </span>Use Case: Manage resources</a><ul class="toc"><li class="tocline"><a href="#primary-scenario-create-resource" class="tocxref"><span class="secno">4.2.1 </span>Primary scenario: create resource</a></li><li class="tocline"><a href="#alternative-scenario-delete-resource" class="tocxref"><span class="secno">4.2.2 </span>Alternative scenario: delete
+			resource</a></li><li class="tocline"><a href="#alternative-scenario-moving-contained-resources" class="tocxref"><span class="secno">4.2.3 </span>Alternative scenario: moving
+			contained resources</a></li></ul></li><li class="tocline"><a href="#use-case-retrieve-resource-description" class="tocxref"><span class="secno">4.3 </span>Use Case: Retrieve resource
+			description</a><ul class="toc"><li class="tocline"><a href="#primary-scenario" class="tocxref"><span class="secno">4.3.1 </span>Primary scenario</a></li><li class="tocline"><a href="#alternative-scenario-retrieve-description-of-a-non-document-resource" class="tocxref"><span class="secno">4.3.2 </span>Alternative scenario: retrieve
+			description of a non-document resource</a></li></ul></li><li class="tocline"><a href="#use-case-update-existing-resource" class="tocxref"><span class="secno">4.4 </span>Use Case: Update existing resource</a><ul class="toc"><li class="tocline"><a href="#primary-scenario-enrichment" class="tocxref"><span class="secno">4.4.1 </span>Primary scenario: enrichment</a></li><li class="tocline"><a href="#alternative-scenario-selective-update-of-a-resource" class="tocxref"><span class="secno">4.4.2 </span>Alternative scenario: selective
+			update of a resource</a></li></ul></li><li class="tocline"><a href="#use-case-determine-if-a-resource-has-changed" class="tocxref"><span class="secno">4.5 </span>Use Case: Determine if a resource has
+			changed</a><ul class="toc"><li class="tocline"><a href="#primary-scenario-1" class="tocxref"><span class="secno">4.5.1 </span>Primary scenario</a></li></ul></li><li class="tocline"><a href="#use-case-aggregate-resources" class="tocxref"><span class="secno">4.6 </span>Use Case: Aggregate resources</a><ul class="toc"><li class="tocline"><a href="#primary-scenario-add-a-resource-to-a-collection" class="tocxref"><span class="secno">4.6.1 </span>Primary scenario: add a resource
+			to a collection</a></li><li class="tocline"><a href="#alternative-scenario-add-a-resource-to-multiple-collections" class="tocxref"><span class="secno">4.6.2 </span>Alternative scenario: add a
+			resource to multiple collections</a></li></ul></li><li class="tocline"><a href="#use-case-filter-resource-description" class="tocxref"><span class="secno">4.7 </span>Use Case: Filter resource description</a><ul class="toc"><li class="tocline"><a href="#primary-scenario-retrieve-collection-level-description" class="tocxref"><span class="secno">4.7.1 </span>Primary scenario: retrieve
+			collection-level description</a></li><li class="tocline"><a href="#alternative-scenario-retrieve-item-level-description-of-a-collection" class="tocxref"><span class="secno">4.7.2 </span>Alternative scenario: retrieve
+			item-level description of a collection</a></li></ul></li><li class="tocline"><a href="#use-case-manage-media-resources" class="tocxref"><span class="secno">4.8 </span>Use Case: Manage media resources</a><ul class="toc"><li class="tocline"><a href="#primary-scenario-access-media-resources" class="tocxref"><span class="secno">4.8.1 </span>Primary scenario: access media
+			resources</a></li><li class="tocline"><a href="#alternative-scenario-media-resource-attachments" class="tocxref"><span class="secno">4.8.2 </span>Alternative scenario:
+			media-resource attachments</a></li></ul></li></ul></li><li class="tocline"><a href="#requirements" class="tocxref"><span class="secno">5. </span>Requirements</a><ul class="toc"><li class="tocline"><a href="#functional-requirements" class="tocxref"><span class="secno">5.1 </span>Functional Requirements</a></li><li class="tocline"><a href="#non-functional-requirements" class="tocxref"><span class="secno">5.2 </span>Non-Functional Requirements</a></li></ul></li><li class="tocline"><a href="#acknowledgements" class="tocxref"><span class="secno">A. </span>Acknowledgements</a></li><li class="tocline"><a href="#history" class="tocxref"><span class="secno">B. </span>Change History</a></li><li class="tocline"><a href="#references" class="tocxref"><span class="secno">C. </span>References</a><ul class="toc"><li class="tocline"><a href="#informative-references" class="tocxref"><span class="secno">C.1 </span>Informative references</a></li></ul></li></ul></section>
 
-<section rel="bibo:chapter" resource="#status" typeof="bibo:Chapter" id="status">
+<section id="status" typeof="bibo:Chapter" resource="#status" rel="bibo:chapter">
 
 </section>
  
-<section id="scope-and-motivation" rel="bibo:chapter" resource="#scope" typeof="bibo:Chapter">
-<!--OddPage--><h2 id="scope"><span class="secno">1. </span>Scope and Motivation</h2>
+<section typeof="bibo:Chapter" resource="#scope" rel="bibo:chapter" id="scope-and-motivation">
+
+<!--OddPage-->
+<h2 id="scope"><span class="secno">1. </span>Scope and Motivation</h2>
 	<p>
 		Linked Data was defined by Tim Berners-Lee with the following
-		guidelines [<cite><a href="#bib-LINKED-DATA" class="bibref">LINKED-DATA</a></cite>]:
+		guidelines [<cite><a class="bibref" href="#bib-LINKED-DATA">LINKED-DATA</a></cite>]:
 	</p>
 	<ol>
 		<li>Use URIs as names for things</li>
@@ -376,7 +376,7 @@
 		of fundamental new technologies, but rather for a series of
 		additional rules and patterns that guide and constrain the use of
 		existing technologies in the construction of a 
-		[<cite><a href="#bib-LINKED-DATA-PLATFORM" class="bibref">LINKED-DATA-PLATFORM</a></cite>] to achieve interoperability.</p>
+		[<cite><a class="bibref" href="#bib-LINKED-DATA-PLATFORM">LINKED-DATA-PLATFORM</a></cite>] to achieve interoperability.</p>
 	<p>The following list illustrates a few of the issues that
 		require additional rules and patterns:</p>
 	<ul>
@@ -391,7 +391,7 @@
 		<li>What standard vocabularies should I use?</li>
 		<li>What primitive data types should I use?</li>
 	</ul>
-	<p>A good goal for the [<cite><a href="#bib-LINKED-DATA-PLATFORM" class="bibref">LINKED-DATA-PLATFORM</a></cite>] would be
+	<p>A good goal for the [<cite><a class="bibref" href="#bib-LINKED-DATA-PLATFORM">LINKED-DATA-PLATFORM</a></cite>] would be
 		to define a specification required to allow the definition of a
 		writable Linked Data API equivalent to the simple application APIs
 		that are often written on the web today using the Atom Publishing
@@ -402,8 +402,10 @@
 
 </section>
 
-<section id="organization-of-this-document" rel="bibo:chapter" resource="#org" typeof="bibo:Chapter">
-<!--OddPage--><h2 id="org"><span class="secno">2. </span>Organization of this Document</h2>
+<section typeof="bibo:Chapter" resource="#org" rel="bibo:chapter" id="organization-of-this-document">
+
+<!--OddPage-->
+<h2 id="org"><span class="secno">2. </span>Organization of this Document</h2>
 
 <p>
  Use-cases are captured in a narrative style that describes a
@@ -414,28 +416,28 @@
 </p>
 	<p>This document is organized as follows:</p>
 	<ul>
-		<li><b><a href="#userstories" title="User Stories">User Stories</a></b>
+		<li><b><a title="User Stories" href="#userstories">User Stories</a></b>
 			capture statements about system requirements written from a user
 			or application perspective. They are typically lightweight and
 			informal and can run from one line to a paragraph or two
-			(sometimes described as an 'epic') <a href="http://www.agilemodeling.com/artifacts/userStory.htm" class="external autonumber" title="http://www.agilemodeling.com/artifacts/userStory.htm" rel="nofollow">[2]</a>. Analysis of each user story will reveal a
+			(sometimes described as an 'epic') <a rel="nofollow" title="http://www.agilemodeling.com/artifacts/userStory.htm" class="external autonumber" href="http://www.agilemodeling.com/artifacts/userStory.htm">[2]</a>. Analysis of each user story will reveal a
 			number of (functional) use-cases and other non-functional
 			requirements. See Device
-				API Access Control Use Cases and Requirements [<cite><a href="#bib-DAP-REQS" class="bibref">DAP-REQS</a></cite>] for a good example
+				API Access Control Use Cases and Requirements [<cite><a class="bibref" href="#bib-DAP-REQS">DAP-REQS</a></cite>] for a good example
 			of user stories and their analysis.</li>
 	</ul>
 	<ul>
-		<li><b><a href="#use-cases" title="Use Cases">Use Cases</a></b> are
+		<li><b><a title="Use Cases" href="#use-cases">Use Cases</a></b> are
 			used to capture and model functional requirements. Use cases
-			describe the system’s behavior under various conditions <a href="http://alistair.cockburn.us/get/2465" class="external autonumber" title="http://alistair.cockburn.us/get/2465" rel="nofollow">[3]</a>,
+			describe the system’s behavior under various conditions <a rel="nofollow" title="http://alistair.cockburn.us/get/2465" class="external autonumber" href="http://alistair.cockburn.us/get/2465">[3]</a>,
 			cataloging who does what with the system, for what purpose, but
-			without concern for system design or implementation <a href="http://www.bredemeyer.com/pdf_files/functreq.pdf" class="external autonumber" title="http://www.bredemeyer.com/pdf_files/functreq.pdf" rel="nofollow">[4]</a>. Each use case is identified by a
+			without concern for system design or implementation <a rel="nofollow" title="http://www.bredemeyer.com/pdf_files/functreq.pdf" class="external autonumber" href="http://www.bredemeyer.com/pdf_files/functreq.pdf">[4]</a>. Each use case is identified by a
 			reference number to aid cross-reference from other documentation;
 			use-case indexing in this document is based on rdb2rdf
-			use-cases [<cite><a href="#bib-RDB2RDF-UC" class="bibref">RDB2RDF-UC</a></cite>]. A variety of styles may be used to capture use-cases,
+			use-cases [<cite><a class="bibref" href="#bib-RDB2RDF-UC">RDB2RDF-UC</a></cite>]. A variety of styles may be used to capture use-cases,
 			from a simple narrative to a structured description with actors,
 			pre/post conditions, and step-by-step behaviors as in POWDER:
-			Use Cases and Requirements [<cite><a href="#bib-POWDER-USE-CASES" class="bibref">POWDER-USE-CASES</a></cite>], and non-functional requirements
+			Use Cases and Requirements [<cite><a class="bibref" href="#bib-POWDER-USE-CASES">POWDER-USE-CASES</a></cite>], and non-functional requirements
 			raised by the use-case. Use cases act like the hub of a wheel,
 			with spokes supporting requirements analysis, scenario-based
 			evaluation, testing, and integration with non-functional, or
@@ -445,25 +447,27 @@
 		<li><b>Scenarios</b> are more focused still, representing a
 			single instance of a use case in action. Scenarios may range from
 			lightweight narratives as seen in Use
-			cases and requirements for Media Fragments [<cite><a href="#bib-MEDIA-FRAGMENTS-REQS" class="bibref">MEDIA-FRAGMENTS-REQS</a></cite>], to being formally
+			cases and requirements for Media Fragments [<cite><a class="bibref" href="#bib-MEDIA-FRAGMENTS-REQS">MEDIA-FRAGMENTS-REQS</a></cite>], to being formally
 			modeled as interaction diagrams. Each use-case should include at
 			least a primary scenario, and possibly other alternative
 			scenarios.</li>
 	</ul>
 	<ul>
-		<li><b><a href="#reqs" title="Requirements">Requirements</a></b>
+		<li><b><a title="Requirements" href="#reqs">Requirements</a></b>
 			lists non-functional or quality requirements, and the use cases
 			they may be derived from. This approach is exemplified in the Use Cases and Requirements for the Data
-			Catalog Vocabulary [<cite><a href="#bib-DCAT-UCR" class="bibref">DCAT-UCR</a></cite>]. It also lists functional requirements that
+			Catalog Vocabulary [<cite><a class="bibref" href="#bib-DCAT-UCR">DCAT-UCR</a></cite>]. It also lists functional requirements that
 			stem from use-cases. It is also possible at this stage to
 			explicitly identify some use-cases as non-requirements.</li>
 	</ul>
 </section>
 	
-<section id="user-stories" rel="bibo:chapter" resource="#userstories" typeof="bibo:Chapter">
-<!--OddPage--><h2 id="userstories"><span class="secno">3. </span>User Stories</h2>
+<section typeof="bibo:Chapter" resource="#userstories" rel="bibo:chapter" id="user-stories">
 
-	<section id="maintaining-social-contact-information" rel="bibo:chapter" resource="#story-social" typeof="bibo:Chapter">
+<!--OddPage-->
+<h2 id="userstories"><span class="secno">3. </span>User Stories</h2>
+
+	<section typeof="bibo:Chapter" resource="#story-social" rel="bibo:chapter" id="maintaining-social-contact-information">
 	<h3 id="story-social"><span class="secno">3.1 </span>Maintaining Social Contact Information</h3>
 	<p>Many of us have multiple email accounts that include
 		information about the people and organizations we interact with –
@@ -488,10 +492,10 @@
 		What would work in either case is a common understanding of the
 		resource, a few formats needed, and access guidance for these
 		resources. This would support how to acquire a link to a contact,
-		and how to use those links to interact with a contact (including <a href="#uc-retrieve_resource_description" title="">reading</a>,
-		<a href="#uc-update_existing" title="">updating</a>,
-		and <a href="#scen-delete_resource" title="">deleting</a>
-		it), as well as how to easily <a href="#scen-create_resource" title="">create a
+		and how to use those links to interact with a contact (including <a title="" href="#uc-retrieve_resource_description">reading</a>,
+		<a title="" href="#uc-update_existing">updating</a>,
+		and <a title="" href="#scen-delete_resource">deleting</a>
+		it), as well as how to easily <a title="" href="#scen-create_resource">create a
 			new contact</a>, add it to my contacts, and when deleting a
 		contact, how it would be removed from my list of contacts. It
 		would also be good to be able to add some application-specific
@@ -507,7 +511,7 @@
 	</p>
 	</section>
 	
-	<section id="keeping-track-of-personal-and-business-relationships" rel="bibo:chapter" resource="#story-tracking_relationships" typeof="bibo:Chapter">
+	<section typeof="bibo:Chapter" resource="#story-tracking_relationships" rel="bibo:chapter" id="keeping-track-of-personal-and-business-relationships">
 	<h3 id="story-tracking_relationships"><span class="secno">3.2 </span>Keeping Track of Personal and
 			Business Relationships</h3>
 	<p>In our daily lives, we deal with many different
@@ -529,24 +533,24 @@
 		maintaining various identifiers in different formats and instead
 		of having to manually supply those identifiers to each one’s
 		corresponding custom application, we could essentially build a set
-		of bookmarks to it all? When we want to <a href="#uc-retrieve_resource_description" title="">examine</a>
-		or <a href="#uc-update_existing" title="">change</a>
+		of bookmarks to it all? When we want to <a title="" href="#uc-retrieve_resource_description">examine</a>
+		or <a title="" href="#uc-update_existing">change</a>
 		their contents, would it not be simpler if there were a single
 		consistent application interface that they all supported? Of
 		course it would.
 	</p>
 	<p>
-		Our set of links would probably be a <a href="#uc-aggregate_resources" title="">simple collection</a>.
+		Our set of links would probably be a <a title="" href="#uc-aggregate_resources">simple collection</a>.
 		The information held by any single organization might be a mix of
-		simple data and <a href="#uc-aggregate_resources" title="">collections
+		simple data and <a title="" href="#uc-aggregate_resources">collections
 			of other data</a>, for example, a bank account balance and a
 		collection of historical transactions. Our bank might easily have
-		<a href="#scen-create_a_nested_container" title="">a collection of accounts for each member of its collection
+		<a title="" href="#scen-create_a_nested_container">a collection of accounts for each member of its collection
 			of customers</a>.
 	</p>
 	</section>
 	
-	<section id="system-and-software-development-tool-integration" rel="bibo:chapter" resource="#story-oslc" typeof="bibo:Chapter">
+	<section typeof="bibo:Chapter" resource="#story-oslc" rel="bibo:chapter" id="system-and-software-development-tool-integration">
 	<h3 id="story-oslc"><span class="secno">3.3 </span>System and Software Development
 			Tool Integration</h3>
 	<p>System and software development tools typically come from a
@@ -587,15 +591,15 @@
 		It is fair to say that although each of those approaches has its
 		adherents and can point to some successes, none of them is wholly
 		satisfactory. The use of Linked Data as an application integration
-		technology has a strong appeal <a href="http://open-services.net/" class="external text" title="http://open-services.net/" rel="nofollow">OSLC</a>.
+		technology has a strong appeal <a rel="nofollow" title="http://open-services.net/" class="external text" href="http://open-services.net/">OSLC</a>.
 	</p>
 	</section>
 	
-	<section id="library-linked-data" rel="bibo:chapter" resource="#story-lld" typeof="bibo:Chapter">
+	<section typeof="bibo:Chapter" resource="#story-lld" rel="bibo:chapter" id="library-linked-data">
 	<h3 id="story-lld"><span class="secno">3.4 </span>Library Linked Data</h3>
 	<p>
 		The <abbr title="World Wide Web Consortium">W3C</abbr> Library Linked Data working group has a number of use
-		cases cited in their Use Case Report [<cite><a href="#bib-LLD-UC" class="bibref">LLD-UC</a></cite>]. These referenced use cases focus on the
+		cases cited in their Use Case Report [<cite><a class="bibref" href="#bib-LLD-UC">LLD-UC</a></cite>]. These referenced use cases focus on the
 		need to extract and correlate library data from disparate sources.
 		Variants of these use cases that can provide consistent formats,
 		as well as ways to improve or update the data, would enable
@@ -606,42 +610,42 @@
 	<p>The 'Digital Objects Cluster' contains a number of relevant
 		use-cases:</p>
 	<ul>
-		<li>Grouping: This should "Allow the end-users to define <a href="#uc-aggregate_resources" title="">groups of resources</a>
+		<li>Grouping: This should &quot;Allow the end-users to define <a title="" href="#uc-aggregate_resources">groups of resources</a>
 			on the web that for some reason belong together. The relationship
 			that exists between the resources is often left unspecified. Some
 			of the resources in a group may not be under control of the
-			institution that defines the groups."
+			institution that defines the groups.&quot;
 		</li>
 	</ul>
 	<ul>
-		<li>Enrichment: "Enable end-users to <a href="#uc-update_existing" title="">link resources
-				together</a>."
+		<li>Enrichment: &quot;Enable end-users to <a title="" href="#uc-update_existing">link resources
+				together</a>.&quot;
 		</li>
 	</ul>
 	<ul>
-		<li>Browsing: "<a href="#uc-Filter_resource_description" title="">Support end-user browsing through groups</a> and
-			resources that belong to the groups."
+		<li>Browsing: &quot;<a title="" href="#uc-Filter_resource_description">Support end-user browsing through groups</a> and
+			resources that belong to the groups.&quot;
 		</li>
 	</ul>
 	<ul>
-		<li>Re-use: "Users should have the capability to re-use all
+		<li>Re-use: &quot;Users should have the capability to re-use all
 			or parts of a collection, with all or part of its metadata,
-			elsewhere on the linked Web."</li>
+			elsewhere on the linked Web.&quot;</li>
 	</ul>
 	<p>The 'Collections' cluster also contains a number of relevant
 		use-cases:</p>
 	<ul>
-		<li>Collection-level description: "Provide <a href="#uc-filter_resource_description" title="">metadata
+		<li>Collection-level description: &quot;Provide <a title="" href="#uc-filter_resource_description">metadata
 				pertaining to a collection as a whole</a>, in contrast to item-level
-			description."
+			description.&quot;
 		</li>
 	</ul>
 	<ul>
-		<li>Collections discovery: "Enable innovative collection
+		<li>Collections discovery: &quot;Enable innovative collection
 			discovery such as identification of nearest location of a
 			physical collection where a specific information resource is
 			found or mobile device applications ... based on collection-level
-			descriptions."</li>
+			descriptions.&quot;</li>
 	</ul>
 	<ul>
 		<li>Community information services: Identify and classify
@@ -649,7 +653,7 @@
 	</ul>
 	</section>
 	
-	<section id="municipality-operational-monitoring" rel="bibo:chapter" resource="#story-meter_monitoring" typeof="bibo:Chapter">
+	<section typeof="bibo:Chapter" resource="#story-meter_monitoring" rel="bibo:chapter" id="municipality-operational-monitoring">
 	<h3 id="story-meter_monitoring"><span class="secno">3.5 </span>Municipality Operational
 			Monitoring</h3>
 	<p>
@@ -660,7 +664,7 @@
 		predict problems, and handle logistics. In order to effectively
 		and efficiently collect, produce, and analyze all this data, a
 		fundamental set of loosely coupled standard data sources are
-		needed. A simple, low-cost way to <a href="#uc-retrieve_resource_description" title="">expose
+		needed. A simple, low-cost way to <a title="" href="#uc-retrieve_resource_description">expose
 			data</a> from the diverse set of monitored services is needed, one
 		that can easily integrate into the municipalities of other systems
 		that inspect and analyze the data. All these services have links
@@ -669,7 +673,7 @@
 	</p>
 	</section>
 	
-	<section id="healthcare" rel="bibo:chapter" resource="#story-healthcare" typeof="bibo:Chapter">
+	<section typeof="bibo:Chapter" resource="#story-healthcare" rel="bibo:chapter" id="healthcare">
 	<h3 id="story-healthcare"><span class="secno">3.6 </span>Healthcare</h3>
 	<p>For physicians to analyze, diagnose, and propose treatment
 		for patients requires a vast amount of complex, changing and
@@ -695,11 +699,11 @@
 		treatment for future incidents.</p>
 	</section>	
 	
-	<section id="metadata-enrichment-in-broadcasting" rel="bibo:chapter" resource="#story-media" typeof="bibo:Chapter">
+	<section typeof="bibo:Chapter" resource="#story-media" rel="bibo:chapter" id="metadata-enrichment-in-broadcasting">
 	<h3 id="story-media"><span class="secno">3.7 </span>Metadata Enrichment in Broadcasting</h3>
 	<p>
 		There are many different use cases when broadcasters show interest
-		in metadata <a href="#uc-pdate_existing" title="">
+		in metadata <a title="" href="#uc-pdate_existing">
 			enrichment</a>:
 	</p>
 	<ul>
@@ -721,13 +725,13 @@
 		linked data, its persistence, and usage rights.</p>
 	</section>
 		
-	<section id="aggregation-and-mashups-of-infrastructure-data" rel="bibo:chapter" resource="#story-mashup" typeof="bibo:Chapter">
+	<section typeof="bibo:Chapter" resource="#story-mashup" rel="bibo:chapter" id="aggregation-and-mashups-of-infrastructure-data">
 	<h3 id="story-mashup"><span class="secno">3.8 </span>Aggregation and Mashups of Infrastructure Data</h3>
 	<p>
 		For infrastructure management (such as storage systems, virtual
 		machine environments, and similar IaaS and PaaS concepts), it is
 		important to provide an environment in which information from
-		different sources can be <a href="#uc-aggregate_resources" title="">aggregated</a>, <a href="#uc-filter_resource_description" title="">filtered</a>,
+		different sources can be <a title="" href="#uc-aggregate_resources">aggregated</a>, <a title="" href="#uc-filter_resource_description">filtered</a>,
 		and visualized effectively. Specifically, the following use cases
 		need to be taken into account:
 	</p>
@@ -745,7 +749,7 @@
 			possible to move to a push-based interaction model, where data
 			sources push notifications to subscribers, and data sources
 			provide different services that consumers can subscribe to (such
-			as "informational messages" or "critical alerts only").</li>
+			as &quot;informational messages&quot; or &quot;critical alerts only&quot;).</li>
 	</ul>
 	<p>In this scenario, the important factors are to have
 		abstractions that allow easy aggregation and filtering, are
@@ -754,10 +758,10 @@
 		well as for push-based interactions.</p>
 	</section>
 	
-	<section id="sharing-payload-of-rdf-data-among-low-end-devices" rel="bibo:chapter" resource="#story-low-end_devices" typeof="bibo:Chapter">
+	<section typeof="bibo:Chapter" resource="#story-low-end_devices" rel="bibo:chapter" id="sharing-payload-of-rdf-data-among-low-end-devices">
 	<h3 id="story-low-end_devices"><span class="secno">3.9 </span>Sharing payload of RDF data among low-end devices</h3>
 	<p>
-		Several projects around the idea of <a href="http://worldwidesemanticweb.wordpress.com/" title="http://worldwidesemanticweb.wordpress.com/" rel="nofollow">downscaling
+		Several projects around the idea of <a rel="nofollow" title="http://worldwidesemanticweb.wordpress.com/" href="http://worldwidesemanticweb.wordpress.com/">downscaling
 			the Semantic Web</a> need to be able to ship payloads of RDF across
 		the nodes member of a given network. The transfers are done in a
 		constrained context in terms of bandwidth, scope of the local
@@ -770,7 +774,7 @@
 	<p>The transfer of an arbitrary payload of RDF data could be
 		implemented through the container mechanism, adding and removing
 		sets of RDF triples to it. Currently, the 
-		"SemanticXO" project uses named graphs and the graph store protocol to
+		&quot;SemanticXO&quot; project uses named graphs and the graph store protocol to
 		create/delete/copy graphs across the nodes but this (almost)
 		imposes the usage of a triple store. Unfortunately, triple stores
 		are rather demanding pieces of software that are not always usable
@@ -778,7 +782,7 @@
 		with a lightweight column store would be better approach.</p>
 	</section>
 	
-	<section id="sharing-binary-resources-and-metadata" rel="bibo:chapter" resource="#story-binary_and_metadata" typeof="bibo:Chapter">
+	<section typeof="bibo:Chapter" resource="#story-binary_and_metadata" rel="bibo:chapter" id="sharing-binary-resources-and-metadata">
 	<h3 id="story-binary_and_metadata"><span class="secno">3.10 </span>Sharing Binary Resources and Metadata</h3>
 	<p>When publishing datasets about stars one may want to publish
 		links to the pictures in which those stars appear, and this may
@@ -803,15 +807,15 @@
 		platform's point-of-view.</p>
 	</section>
 	
-	<section id="data-catalogs" rel="bibo:chapter" resource="#story-data_catalogs" typeof="bibo:Chapter">
+	<section typeof="bibo:Chapter" resource="#story-data_catalogs" rel="bibo:chapter" id="data-catalogs">
 	<h3 id="story-data_catalogs"><span class="secno">3.11 </span>Data Catalogs</h3>
 	<p>
-		The Asset Description Metadata Schema (<a href="http://joinup.ec.europa.eu/asset/adms/home" title="http://joinup.ec.europa.eu/asset/adms/home" rel="nofollow">ADMS</a>)
+		The Asset Description Metadata Schema (<a rel="nofollow" title="http://joinup.ec.europa.eu/asset/adms/home" href="http://joinup.ec.europa.eu/asset/adms/home">ADMS</a>)
 		provides the data model to describe semantic asset repository
 		contents, but this leaves many open challenges when building a
 		federation of these repositories to serve the need of asset
 		reuse. These include accessing and querying individual
-		repositories and efficiently retrieving <a href="#uc-has_resource_changed" title="">
+		repositories and efficiently retrieving <a title="" href="#uc-has_resource_changed">
 			updated content</a> without having to retrieve the whole content.
 		Hence, we chose to build the integration solution capitalizing on
 		the Data Warehousing integration approach. This allows us to cope
@@ -833,15 +837,15 @@
 		enable meaningful exchange of data. However, this leaves the
 		challenge of efficient access to the data not fully addressed.</p>
 	<p>
-		Related: <a href="http://spec.datacatalogs.org/" title="http://spec.datacatalogs.org/" rel="nofollow">Data Catalog Schema and Protocol</a>
+		Related: <a rel="nofollow" title="http://spec.datacatalogs.org/" href="http://spec.datacatalogs.org/">Data Catalog Schema and Protocol</a>
 	</p>
 	</section>
 	
-	<section id="constrained-devices-and-networks" rel="bibo:chapter" resource="#story-constrained_devices" typeof="bibo:Chapter">
+	<section typeof="bibo:Chapter" resource="#story-constrained_devices" rel="bibo:chapter" id="constrained-devices-and-networks">
 	<h3 id="story-constrained_devices"><span class="secno">3.12 </span>Constrained Devices and Networks</h3>
 	<p>
 		Information coming from resource constrained devices in the Web of
-		Things (<a href="http://en.wikipedia.org/wiki/Web_of_Things" title="http://en.wikipedia.org/wiki/Web_of_Things" rel="nofollow">WoT</a>)
+		Things (<a rel="nofollow" title="http://en.wikipedia.org/wiki/Web_of_Things" href="http://en.wikipedia.org/wiki/Web_of_Things">WoT</a>)
 		has been identified as a major driver in many domains, from smart
 		cities to environmental monitoring to real-time tracking. The
 		amount of information produced by these devices is growing
@@ -850,9 +854,9 @@
 		standards as on the Web, integration with applications will be
 		simplified and higher-level interactions among resource
 		constrained devices, abstracting away heterogeneities, will become
-		possible. Up-coming IoT/WoT standards such as <a href="http://datatracker.ietf.org/wg/6lowpan/" title="http://datatracker.ietf.org/wg/6lowpan/" rel="nofollow">6LowPAN</a>
+		possible. Up-coming IoT/WoT standards such as <a rel="nofollow" title="http://datatracker.ietf.org/wg/6lowpan/" href="http://datatracker.ietf.org/wg/6lowpan/">6LowPAN</a>
 		- IPv6 for resource constrained devices - and the Constrained
-		Application Protocol (<a href="http://tools.ietf.org/html/draft-ietf-core-coap" title="http://tools.ietf.org/html/draft-ietf-core-coap" rel="nofollow">CoAP</a>), which provides a downscaled version of
+		Application Protocol (<a rel="nofollow" title="http://tools.ietf.org/html/draft-ietf-core-coap" href="http://tools.ietf.org/html/draft-ietf-core-coap">CoAP</a>), which provides a downscaled version of
 		HTTP on top of UDP for the use on constrained devices, are already
 		at a mature stage. The next step now is to support RESTful
 		interfaces also on resource constrained devices, adhering to the
@@ -860,13 +864,13 @@
 		both on the device and in the network (such as bandwidth, energy,
 		memory) a solution based on SPARQL Update is at the current point
 		in time considered not to be useful and/or feasible. An approach
-		based on the <a href="http://tools.ietf.org/html/draft-castellani-core-http-mapping" title="http://tools.ietf.org/html/draft-castellani-core-http-mapping" rel="nofollow">HTTP-CoAP Mapping</a> would enable constrained
+		based on the <a rel="nofollow" title="http://tools.ietf.org/html/draft-castellani-core-http-mapping" href="http://tools.ietf.org/html/draft-castellani-core-http-mapping">HTTP-CoAP Mapping</a> would enable constrained
 		devices to directly participate in a Linked Data-based
 		environment.
 	</p>
 	</section>
 	
-	<section id="services-supporting-the-process-of-science" rel="bibo:chapter" resource="#story-process_of_science" typeof="bibo:Chapter">
+	<section typeof="bibo:Chapter" resource="#story-process_of_science" rel="bibo:chapter" id="services-supporting-the-process-of-science">
 	<h3 id="story-process_of_science"><span class="secno">3.13 </span>Services Supporting the Process
 			of Science</h3>
 	<p>Many fields of science now include branches with in silico
@@ -875,15 +879,15 @@
 		provided by scientific workflow systems to capture, assist, and
 		preserve the complete lifecycle from record of the experiment,
 		through local trusted sharing, analysis, dissemination (including
-		publishing of experimental data "beyond the PDF"), and re-use.</p>
+		publishing of experimental data &quot;beyond the PDF&quot;), and re-use.</p>
 	<ul>
-		<li><a href="#uc-aggregate_resources" title="">Aggregations</a>,
+		<li><a title="" href="#uc-aggregate_resources">Aggregations</a>,
 			specifically <i>Research Objects (ROs)</i> that are exchanged
 			between services and clients bringing together workflows, data
 			sets, annotations, and provenance. We use an RDF model for this.
 			While some aggregated contents are encoded using RDF and an
 			increasing number are linked data sources, others are not; while
-			some are stored locally "within" the RO, others are remote (in
+			some are stored locally &quot;within&quot; the RO, others are remote (in
 			both cases this is often due to size of the resources or access
 			policies).</li>
 		<li>Services that are distributed and linked. Some may be
@@ -904,11 +908,11 @@
 		</li>
 	</ul>
 	<p>
-		seeAlso: <a href="http://www.wf4ever-project.org/" title="http://www.wf4ever-project.org/" rel="nofollow">Wf4Ever</a>
+		seeAlso: <a rel="nofollow" title="http://www.wf4ever-project.org/" href="http://www.wf4ever-project.org/">Wf4Ever</a>
 	</p>
 	</section>
 	
-	<section id="project-membership-information-information-evolution" rel="bibo:chapter" resource="#story-project_data" typeof="bibo:Chapter">
+	<section typeof="bibo:Chapter" resource="#story-project_data" rel="bibo:chapter" id="project-membership-information-information-evolution">
 	<h3 id="story-project_data"><span class="secno">3.14 </span>Project Membership Information: Information Evolution</h3>
 	<p>Information about people and projects changes as roles
 		change, as organisations change and as contact details change.
@@ -929,17 +933,17 @@
 	<p>To retain the history of the project, the old version of a
 		resources, including container resources, should be retained so
 		there is a need to address both specific items and also have a
-		notion of "current".</p>
+		notion of &quot;current&quot;.</p>
 	<p>Access to information has two aspects:</p>
 	<ul>
-		<li>Access to the "current" state, regardless of the version
+		<li>Access to the &quot;current&quot; state, regardless of the version
 			of the resource description</li>
 		<li>Access to historical state, via access to a specific
 			version of the resource description</li>
 	</ul>
 	</section>
 	
-	<section id="cloud-infrastructure-management" rel="bibo:chapter" resource="#story-cloud" typeof="bibo:Chapter">
+	<section typeof="bibo:Chapter" resource="#story-cloud" rel="bibo:chapter" id="cloud-infrastructure-management">
 	<h3 id="story-cloud"><span class="secno">3.15 </span>Cloud Infrastructure Management</h3>
 	<p>Cloud operators offer API support to provide customers with
 		remote access for the management of Cloud infrastructure (IaaS).
@@ -972,8 +976,10 @@
 
 </section>
 
-<section id="use-cases" rel="bibo:chapter" resource="#usecases" typeof="bibo:Chapter">
-<!--OddPage--><h2 id="usecases"><span class="secno">4. </span>Use Cases</h2>
+<section typeof="bibo:Chapter" resource="#usecases" rel="bibo:chapter" id="use-cases">
+
+<!--OddPage-->
+<h2 id="usecases"><span class="secno">4. </span>Use Cases</h2>
 
 	<p>The following use-cases are each derived from one or more of
 		the user-stories above. These use-cases are explored in detail
@@ -982,7 +988,7 @@
 		contain are included purely for illustrative purposes, and should
 		not be interpreted normatively.</p>
 		
-	<section id="use-case-manage-containers" rel="bibo:chapter" resource="#uc-manage_containers" typeof="bibo:Chapter">
+	<section typeof="bibo:Chapter" resource="#uc-manage_containers" rel="bibo:chapter" id="use-case-manage-containers">
 	<h3 id="uc-manage_containers"><span class="secno">4.1 </span>Use Case: Manage containers</h3>
 	<p>
 		A number of user-stories introduce the idea of a <i>container</i>
@@ -997,22 +1003,22 @@
 		invoked by exchanging RDF documents.
 	</p>
 	<ul>
-		<li>Provide "access guidance for ... resources" (affordances)
-			(from user-story, <a href="#story-social" title="Social Contacts">Maintaining
+		<li>Provide &quot;access guidance for ... resources&quot; (affordances)
+			(from user-story, <a title="Social Contacts" href="#story-social">Maintaining
 				Social Contact Information</a>).
 		</li>
 	</ul>
 	
-	<section id="primary-scenario-create-container" rel="bibo:chapter" resource="#scen-create_container" typeof="bibo:Chapter">
+	<section typeof="bibo:Chapter" resource="#scen-create_container" rel="bibo:chapter" id="primary-scenario-create-container">
 	<h4 id="scen-create_container"><span class="secno">4.1.1 </span>Primary scenario: create
 			container</h4>
 	<p>
-		Create a new container resource within the <abbr title="Linked Data Platform">LDP</abbr> server. In <a href="#story-process_of_science" title="">Services
-			supporting the process of science</a>, <a href="http://wf4ever.github.com/ro-primer/" title="http://wf4ever.github.com/ro-primer/" rel="nofollow">Research
+		Create a new container resource within the <abbr title="Linked Data Platform">LDP</abbr> server. In <a title="" href="#story-process_of_science">Services
+			supporting the process of science</a>, <a rel="nofollow" title="http://wf4ever.github.com/ro-primer/" href="http://wf4ever.github.com/ro-primer/">Research
 			Objects</a> are semantically rich aggregations of resources that
 		bring together data, methods and people in scientific
 		investigations. A basic workflow research object will be created
-		to aggegate <a href="http://ceur-ws.org/Vol-903/paper-01.pdf" title="http://ceur-ws.org/Vol-903/paper-01.pdf" rel="nofollow">scientific
+		to aggegate <a rel="nofollow" title="http://ceur-ws.org/Vol-903/paper-01.pdf" href="http://ceur-ws.org/Vol-903/paper-01.pdf">scientific
 			workflows</a> and the artefacts that result from this workflow. The
 		research object begins life as an empty container into which
 		workflows, datasets, results and other data will be added
@@ -1023,14 +1029,14 @@
 @prefix ore:    http://www.openarchives.org/ore/
 
 &lt;&gt; a ro:ResearchObject, ore:Aggregation ;
-    dct:created "2012-12-01"^^xsd:dateTime .</pre></div>
+    dct:created &quot;2012-12-01&quot;^^xsd:dateTime .</pre></div>
 	</section>
 	
-	<section id="alternative-scenario-create-a-nested-container" rel="bibo:chapter" resource="#scen-create_a_nested_container" typeof="bibo:Chapter">
+	<section typeof="bibo:Chapter" resource="#scen-create_a_nested_container" rel="bibo:chapter" id="alternative-scenario-create-a-nested-container">
 	<h4 id="scen-create_a_nested_container"><span class="secno">4.1.2 </span>Alternative scenario: create a
 			nested container</h4>
 	<p>
-		The motivation for nested containers comes from the <a href="#story-oslc" title="Story Tool Integration">
+		The motivation for nested containers comes from the <a title="Story Tool Integration" href="#story-oslc">
 			System and Software Development Tool Integration</a> user-story. The
 		OSLC Change Management vocabulary allows bug reports to have
 		attachments referenced by the membership predicate
@@ -1045,20 +1051,20 @@
 :top-level-container rdfs:member :issue1234 .
 
 :issue1234 a oslc_cm:ChangeRequest;
-      dcterms:identifier "1234";
-      dcterms:type "a bug";
+      dcterms:identifier &quot;1234&quot;;
+      dcterms:type &quot;a bug&quot;;
       dcterms:related :issue1235 ;
       oslc_cm:attachments :attachments123.
 
 :issue1235 a oslc_cm:ChangeRequest;
-      dcterms:title "a related bug".
+      dcterms:title &quot;a related bug&quot;.
 
 :attachments a oslc_cm:AttachmentList;
       oslc_cm:attachment :attachment324, :attachment251.</pre></div>
 	</section>
 	</section>
 	
-	<section id="use-case-manage-resources" rel="bibo:chapter" resource="#uc-manage_resources" typeof="bibo:Chapter">
+	<section typeof="bibo:Chapter" resource="#uc-manage_resources" rel="bibo:chapter" id="use-case-manage-resources">
 	<h3 id="uc-manage_resources"><span class="secno">4.2 </span>Use Case: Manage resources</h3>
 	<p>
 		This use-case addresses the managed lifecycle of a resource and is
@@ -1083,47 +1089,47 @@
 		naming, perhaps to provide a more human-readable URI. An <abbr title="Linked Data Platform">LDP</abbr>
 		server could support something like the Atom
 			Publishing Protocol slug header to convey a user defined naming
-		'hint' [<cite><a href="#bib-RFC5023" class="bibref">RFC5023</a></cite>].
+		'hint' [<cite><a class="bibref" href="#bib-RFC5023">RFC5023</a></cite>].
 	</p>
 	<ul>
-		<li>Non-duplication of resources: "Eliminate multiple
-			copies", representing resources in a single place (from <a href="#story-social" title="Story Social Informatinon">#Maintaining
+		<li>Non-duplication of resources: &quot;Eliminate multiple
+			copies&quot;, representing resources in a single place (from <a title="Story Social Informatinon" href="#story-social">#Maintaining
 				Social Contact Information</a>).
 		</li>
-		<li>Distribution of resources: Linked data "may be stored on
-			separate servers" (from <a href="#story-social" title="Story Social Informatinon">#Maintaining
+		<li>Distribution of resources: Linked data &quot;may be stored on
+			separate servers&quot; (from <a title="Story Social Informatinon" href="#story-social">#Maintaining
 				Social Contact Information</a>).
 		</li>
-		<li>Consistent, global naming: Resources should be "linked to
+		<li>Consistent, global naming: Resources should be &quot;linked to
 			consistently, ... instead of maintaining various identifiers in
-			different formats" (from <a href="#story-tracking_relationships" title="Story Tracking Relationships">#Keeping Track of Personal and Business
+			different formats&quot; (from <a title="Story Tracking Relationships" href="#story-tracking_relationships">#Keeping Track of Personal and Business
 				Relationships</a>).
 		</li>
 	</ul>
 	
-	<section id="primary-scenario-create-resource" rel="bibo:chapter" resource="#scen-create_resource" typeof="bibo:Chapter">
+	<section typeof="bibo:Chapter" resource="#scen-create_resource" rel="bibo:chapter" id="primary-scenario-create-resource">
 	<h4 id="scen-create_resource"><span class="secno">4.2.1 </span>Primary scenario: create resource</h4>
 	<p>
 		Resources begin life by being created within a container. From
-		user-story, <a href="#story-social" title="Story Social Informatinon">
+		user-story, <a title="Story Social Informatinon" href="#story-social">
 		Maintaining Social Contact Information</a>, It should be
-		possible to "easily create a new contact and add it to my
-		contacts." This suggests that resource creation is closely linked
+		possible to &quot;easily create a new contact and add it to my
+		contacts.&quot; This suggests that resource creation is closely linked
 		to the application context. The new resource is created in a
-		container representing "my contacts." The lifecycle of the
+		container representing &quot;my contacts.&quot; The lifecycle of the
 		resource is linked to the lifecycle of it's container. So, for
-		example, if "my contacts" is deleted then a user would also
+		example, if &quot;my contacts&quot; is deleted then a user would also
 		reasonably expect that all contacts within it would also be
 		deleted.
 	</p>
 	<p>
 		Contact details are captured as an RDF description and it's
-		properties, including "names, email addresses, telephone numbers,
-		instant messenger identities and so on." The description may
-		include non-standard RDF; "data about my contacts that the
-		original design didn’t consider." The following RDF could be used
+		properties, including &quot;names, email addresses, telephone numbers,
+		instant messenger identities and so on.&quot; The description may
+		include non-standard RDF; &quot;data about my contacts that the
+		original design didn’t consider.&quot; The following RDF could be used
 		to describe contact information using the FOAF
-		vocabulary [<cite><a href="#bib-FOAF" class="bibref">FOAF</a></cite>]. A contact is represented here by a
+		vocabulary [<cite><a class="bibref" href="#bib-FOAF">FOAF</a></cite>]. A contact is represented here by a
 		foaf:PersonalProfileDocument defining a resource that can be
 		created and updated as a single-unit, even though it may describe
 		ancillary resources, such as a foaf:Person, below.
@@ -1133,11 +1139,11 @@
 &lt;&gt; a foaf:PersonalProfileDocument;
 	foaf:PrimaryTopic [ 
 		a foaf:Person;
-		foaf:name "Timothy Berners-Lee";
-		foaf:title "Sir";
-		foaf:firstName "Timothy";
-		foaf:surname "Berners-Lee";
-		foaf:nick "TimBL", "timbl";
+		foaf:name &quot;Timothy Berners-Lee&quot;;
+		foaf:title &quot;Sir&quot;;
+		foaf:firstName &quot;Timothy&quot;;
+		foaf:surname &quot;Berners-Lee&quot;;
+		foaf:nick &quot;TimBL&quot;, &quot;timbl&quot;;
 		foaf:homepage &lt;http://www.w3.org/People/Berners-Lee/&gt;;
 		foaf:weblog &lt;http://dig.csail.mit.edu/breadcrumbs/blog/4&gt;;
 		foaf:mbox &lt;mailto:[email protected]&gt;;
@@ -1145,7 +1151,7 @@
 	]</pre></div>
 	</section>
 	
-	<section id="alternative-scenario-delete-resource" rel="bibo:chapter" resource="#scen-delete_resource" typeof="bibo:Chapter">
+	<section typeof="bibo:Chapter" resource="#scen-delete_resource" rel="bibo:chapter" id="alternative-scenario-delete-resource">
 	<h4 id="scen-delete_resource"><span class="secno">4.2.2 </span>Alternative scenario: delete
 			resource</h4>
 	<p>
@@ -1156,12 +1162,12 @@
 		server may also delete any or all contained resources. In normal
 		practice, a deleted resource cannot be reinstated. There are
 		however, edge-cases where limited undelete may be desirable. Best
-		practice states that "Cool URIs don't change" [<cite><a href="#bib-COOLURIS" class="bibref">COOLURIS</a></cite>], which implies that
+		practice states that &quot;Cool URIs don't change&quot; [<cite><a class="bibref" href="#bib-COOLURIS">COOLURIS</a></cite>], which implies that
 		deleted URIs shouldn't be recycled.
 	</p>
 	</section>
 	
-	<section id="alternative-scenario-moving-contained-resources" rel="bibo:chapter" resource="#scen-moving_contained_resources" typeof="bibo:Chapter">
+	<section typeof="bibo:Chapter" resource="#scen-moving_contained_resources" rel="bibo:chapter" id="alternative-scenario-moving-contained-resources">
 	<h4 id="scen-moving_contained_resources"><span class="secno">4.2.3 </span>Alternative scenario: moving
 			contained resources</h4>
 	<p>
@@ -1173,13 +1179,13 @@
 		resource, which may be referenced as many places as necessary. A
 		change of ownership may - or may not - imply a change of URI,
 		depending upon the specific server naming policy. While assigning a
-		new URI to a resource is discouraged [<cite><a href="#bib-WEBARCH" class="bibref">WEBARCH</a></cite>], it is possible to indicate that a
+		new URI to a resource is discouraged [<cite><a class="bibref" href="#bib-WEBARCH">WEBARCH</a></cite>], it is possible to indicate that a
 		resource has moved with an appropriate HTTP response.
 	</p>
 	</section>
 	</section>
 	
-	<section id="use-case-retrieve-resource-description" rel="bibo:chapter" resource="#uc-retrieve_resource_description" typeof="bibo:Chapter">
+	<section typeof="bibo:Chapter" resource="#uc-retrieve_resource_description" rel="bibo:chapter" id="use-case-retrieve-resource-description">
 	<h3 id="uc-retrieve_resource_description"><span class="secno">4.3 </span>Use Case: Retrieve resource
 			description</h3>
 	<p>Access the current description of a resource, containing
@@ -1193,24 +1199,24 @@
 		they are being applied to the correct version.</p>
 	<ul>
 		<li>Use standard vocabularies as appropriate to enable a
-			"common understanding of the resource" (from <a href="#story-social" title="">Maintaining
+			&quot;common understanding of the resource&quot; (from <a title="" href="#story-social">Maintaining
 				Social Contact Information</a>).
 		</li>
-		<li>A "scalable linking model is key" (from <a href="#story-meter_monitoring" title="">#Municipality
+		<li>A &quot;scalable linking model is key&quot; (from <a title="" href="#story-meter_monitoring">#Municipality
 				Operational Monitoring</a>).
 		</li>
 	</ul>
 	
-	<section id="primary-scenario" rel="bibo:chapter" resource="#scen-fetch" typeof="bibo:Chapter">
+	<section typeof="bibo:Chapter" resource="#scen-fetch" rel="bibo:chapter" id="primary-scenario">
 	<h4 id="scen-fetch"><span class="secno">4.3.1 </span>Primary scenario</h4>
 	<p>
-		The user-story <a href="#story-project_data" title=""> Project Membership Information</a> discusses the
+		The user-story <a title="" href="#story-project_data"> Project Membership Information</a> discusses the
 		representation of information about people and projects. It calls
-		for "Resource descriptions for each person and project" allowing
+		for &quot;Resource descriptions for each person and project&quot; allowing
 		project teams to review information held about these resources.
 		The example below illustrates the kinds of information that might
-		be held about organizational structures based on the <a href="http://www.epimorphics.com" title="http://www.epimorphics.com" rel="nofollow">Epimorphics</a>
-		<a href="http://www.epimorphics.com/public/vocabulary/org.html" title="http://www.epimorphics.com/public/vocabulary/org.html" rel="nofollow">organizational ontology</a>.
+		be held about organizational structures based on the <a rel="nofollow" title="http://www.epimorphics.com" href="http://www.epimorphics.com">Epimorphics</a>
+		<a rel="nofollow" title="http://www.epimorphics.com/public/vocabulary/org.html" href="http://www.epimorphics.com/public/vocabulary/org.html">organizational ontology</a>.
 	</p>
 	<p>Note that the example below defines two resources (shown as
 		separate sections below) that will be hosted on an <abbr title="Linked Data Platform">LDP</abbr> server based at
@@ -1228,20 +1234,20 @@
 	org:organization http://www.w3.org/&gt; ;
 	org:role &lt;director&gt; ;
 	org:memberDuring [a owltime:Interval; owltime:hasBeginning [
-		owltime:inXSDDateTime "1994-10-01T00:00:00Z"^^xsd:dateTime]] .
+		owltime:inXSDDateTime &quot;1994-10-01T00:00:00Z&quot;^^xsd:dateTime]] .
 
 &lt;http://www.w3.org/&gt; a org:FormalOrganization ;
-	skos:prefLabel "The World Wide Web Consortium"@en ;
-	skos:altLabel "W3C" .</pre></div>
+	skos:prefLabel &quot;The World Wide Web Consortium&quot;@en ;
+	skos:altLabel &quot;W3C&quot; .</pre></div>
 <div class="example"><div class="example-title"><span>Example 5</span></div><pre class="example">@prefix org: &lt;http://www.w3.org/ns/org#&gt; .
 @prefix rdfs: &lt;http://www.w3.org/2000/01/rdf-schema#&gt; .
 @base &lt;http://example.com/&gt; .
 
 &lt;director&gt; a org:Role ;
-	rdfs:label "Director" .</pre></div>
+	rdfs:label &quot;Director&quot; .</pre></div>
 	</section>
 	
-	<section id="alternative-scenario-retrieve-description-of-a-non-document-resource" rel="bibo:chapter" resource="#scen-alt_non-document_resource" typeof="bibo:Chapter">
+	<section typeof="bibo:Chapter" resource="#scen-alt_non-document_resource" rel="bibo:chapter" id="alternative-scenario-retrieve-description-of-a-non-document-resource">
 	<h4 id="scen-alt_non-document_resource"><span class="secno">4.3.2 </span>Alternative scenario: retrieve
 			description of a non-document resource</h4>
 	<p>In many cases, the things that are of interest are not
@@ -1258,13 +1264,13 @@
 @prefix dc: &lt;http://purl.org/dc/elements/1.1/&gt;.
 
 &lt;&gt; a foaf:PersonalProfileDocument ;
-	dc:title "Tim Berners-Lee's FOAF file" ;
+	dc:title &quot;Tim Berners-Lee's FOAF file&quot; ;
 	foaf:homepage &lt;http://www.w3.org/People/Berners-Lee/&gt; ;
 	foaf:primaryTopic &lt;#i&gt; .</pre></div>
 	</section>
 	</section>
 	
-	<section id="use-case-update-existing-resource" rel="bibo:chapter" resource="#uc-update_existing" typeof="bibo:Chapter">
+	<section typeof="bibo:Chapter" resource="#uc-update_existing" rel="bibo:chapter" id="use-case-update-existing-resource">
 	<h3 id="uc-update_existing"><span class="secno">4.4 </span>Use Case: Update existing resource</h3>
 	<p>
 		Change the RDF description of a <abbr title="Linked Data Platform">LDP</abbr> resource, potentially removing
@@ -1273,17 +1279,17 @@
 		other resources.
 	</p>
 	<ul>
-		<li>Unrestricted vocabulary: It should be possible be "able
-			to add ... application-specific data" to resources (from <a href="#story-social" title="">#Maintaining
+		<li>Unrestricted vocabulary: It should be possible be &quot;able
+			to add ... application-specific data&quot; to resources (from <a title="" href="#story-social">#Maintaining
 				Social Contact Information</a>).
 		</li>
 	</ul>
 	
-	<section id="primary-scenario-enrichment" rel="bibo:chapter" resource="#scen-update_enrichment" typeof="bibo:Chapter">
+	<section typeof="bibo:Chapter" resource="#scen-update_enrichment" rel="bibo:chapter" id="primary-scenario-enrichment">
 	<h4 id="scen-update_enrichment"><span class="secno">4.4.1 </span>Primary scenario: enrichment</h4>
 	<p>
-		This relates to user-story <a href="#story-media" title="">
-			Metadata Enrichment in Broadcasting</a> and is based on the <a href="http://www.bbc.co.uk/ontologies/sport/" title="http://www.bbc.co.uk/ontologies/sport/" rel="nofollow">BBC
+		This relates to user-story <a title="" href="#story-media">
+			Metadata Enrichment in Broadcasting</a> and is based on the <a rel="nofollow" title="http://www.bbc.co.uk/ontologies/sport/" href="http://www.bbc.co.uk/ontologies/sport/">BBC
 			Sports Ontology</a>. The <i>resource-centric</i> view of linked-data
 		provides a natural granularity for substituting, or overwriting a
 		resource and its data. The simplest kind of update would simply
@@ -1297,7 +1303,7 @@
 @prefix rdfs: &lt;http://www.w3.org/2000/01/rdf-schema#&gt; .
  
  :mens_sprint a sport:MultiStageCompetition;
-    rdfs:label "Men's Sprint";
+    rdfs:label &quot;Men's Sprint&quot;;
     sport:award &lt;#gold_medal&gt; .
 
 &lt;#gold_medal&gt; a sport:Award .</pre></div>
@@ -1309,21 +1315,21 @@
 @prefix foaf: &lt;http://xmlns.com/foaf/0.1/&gt; .
  
  :mens_sprint a sport:MultiStageCompetition;
-    rdfs:label "Men's Sprint";
+    rdfs:label &quot;Men's Sprint&quot;;
     sport:award &lt;#gold_medal&gt; .
 &lt;#gold_medal&gt; a sport:Award; 
     sport:awarded_to [
         a foaf:Agent ;
-        foaf:name "Chris Hoy" .
+        foaf:name &quot;Chris Hoy&quot; .
     ] .</pre></div>
 	</section>
 	
-	<section id="alternative-scenario-selective-update-of-a-resource" rel="bibo:chapter" resource="#scen-alt_selective_update" typeof="bibo:Chapter">
+	<section typeof="bibo:Chapter" resource="#scen-alt_selective_update" rel="bibo:chapter" id="alternative-scenario-selective-update-of-a-resource">
 	<h4 id="scen-alt_selective_update"><span class="secno">4.4.2 </span>Alternative scenario: selective
 			update of a resource</h4>
 	<p>
-		This relates to user-story <a href="#story-data_catalogs" title="">Data
-			Catalogs</a>, based on the <a href="http://vocab.deri.ie/dcat" title="http://vocab.deri.ie/dcat" rel="nofollow">Data Catalog Vocabulary</a>. A catalogue is
+		This relates to user-story <a title="" href="#story-data_catalogs">Data
+			Catalogs</a>, based on the <a rel="nofollow" title="http://vocab.deri.ie/dcat" href="http://vocab.deri.ie/dcat">Data Catalog Vocabulary</a>. A catalogue is
 		described by the following RDF model.
 	</p>
 	<div class="example"><div class="example-title"><span>Example 9</span></div><pre class="example">@prefix dcat: &lt;http://www.w3.org/ns/dcat#&gt;	.
@@ -1331,11 +1337,11 @@
    
  :catalog a dcat:Catalog ;
     dcat:dataset :dataset/001;
-    dcterms:issued "2012-12-11"^^xsd:date.</pre></div>
+    dcterms:issued &quot;2012-12-11&quot;^^xsd:date.</pre></div>
 	<p>
 		A catalog may contain multiple datasets, so when linking to new
 		datasets it would be simpler and preferable to selectively add
-		just the new dataset links. A <a href="http://docs.api.talis.com/getting-started/changesets" title="http://docs.api.talis.com/getting-started/changesets" rel="nofollow">Talis changeset</a> could be used to add a new dc:title to the
+		just the new dataset links. A <a rel="nofollow" title="http://docs.api.talis.com/getting-started/changesets" href="http://docs.api.talis.com/getting-started/changesets">Talis changeset</a> could be used to add a new dc:title to the
 		dataset. The following update would be directed to the catalogue
 		to add an additional dataset.
 	</p>
@@ -1347,8 +1353,8 @@
 &lt;change1&gt;
   a cs:ChangeSet ;
   cs:subjectOfChange :catalog ;
-  cs:createdDate "2012-01-01T00:00:00Z" ;
-  cs:changeReason "Update catalog datasets" ;
+  cs:createdDate &quot;2012-01-01T00:00:00Z&quot; ;
+  cs:changeReason &quot;Update catalog datasets&quot; ;
   cs:addition [
     a rdf:Statement ;
     rdf:subject :catalog ;
@@ -1358,7 +1364,7 @@
 	</section>
 	</section>
 	
-	<section id="use-case-determine-if-a-resource-has-changed" rel="bibo:chapter" resource="#uc-has_resource_changed" typeof="bibo:Chapter">
+	<section typeof="bibo:Chapter" resource="#uc-has_resource_changed" rel="bibo:chapter" id="use-case-determine-if-a-resource-has-changed">
 	<h3 id="uc-has_resource_changed"><span class="secno">4.5 </span>Use Case: Determine if a resource has
 			changed</h3>
 	<p>
@@ -1372,12 +1378,12 @@
 		unchanged.
 	</p>
 	
-	<section id="primary-scenario-1" rel="bibo:chapter" resource="#scen-primary_has_changed" typeof="bibo:Chapter">
+	<section typeof="bibo:Chapter" resource="#scen-primary_has_changed" rel="bibo:chapter" id="primary-scenario-1">
 	<h4 id="scen-primary_has_changed"><span class="secno">4.5.1 </span>Primary scenario</h4>
 	<p>
-		Based on the user-story, <a href="#story-constrained_devices" title="">
+		Based on the user-story, <a title="" href="#story-constrained_devices">
 			Constrained Devices and Networks</a>, an <abbr title="Linked Data Platform">LDP</abbr> server could be configured to
-		act as a proxy for a CoAP [<cite><a href="#bib-COAP" class="bibref">COAP</a></cite>] based <a href="http://en.wikipedia.org/wiki/Web_of_Things" title="http://en.wikipedia.org/wiki/Web_of_Things" rel="nofollow">Web
+		act as a proxy for a CoAP [<cite><a class="bibref" href="#bib-COAP">COAP</a></cite>] based <a rel="nofollow" title="http://en.wikipedia.org/wiki/Web_of_Things" href="http://en.wikipedia.org/wiki/Web_of_Things">Web
 			of Things</a>. As an observer of CoAP resources, the <abbr title="Linked Data Platform">LDP</abbr> server registers
 		its interest so that it will be notified whenever the sensor
 		reading changes. Clients of the <abbr title="Linked Data Platform">LDP</abbr> can interrogate the server to
@@ -1386,13 +1392,13 @@
 	<p>
 		In this example, the information about a sensor and corresponding
 		sensor readings can be represented as RDF resources. The first
-		resource below, represents a sensor described using the <a href="http://www.w3.org/2005/Incubator/ssn/" title="http://www.w3.org/2005/Incubator/ssn/" rel="nofollow">Semantic
+		resource below, represents a sensor described using the <a rel="nofollow" title="http://www.w3.org/2005/Incubator/ssn/" href="http://www.w3.org/2005/Incubator/ssn/">Semantic
 			Sensor Network</a> ontology.
 	</p>
 	<div class="example"><div class="example-title"><span>Example 11</span></div><pre class="example">@prefix : &lt;http://example.com/energy-management/&gt;.
 
 &lt;&gt; a :MainsFrequencySensor;
-  rdfs:comment "Sense grid load based on mains frequency";
+  rdfs:comment &quot;Sense grid load based on mains frequency&quot;;
   ssn:hasMeasurementCapability [
 	a :FrequencyMeasurementCapability;
 	ssn:hasMeasurementProperty &lt;#property_1&gt; .
@@ -1409,11 +1415,11 @@
 
 &lt;http://example.com/energy-management#property_1&gt; :hasMeasurementPropertyValue &lt;&gt; .
 &lt;&gt; a :FrequencyValue;
-	:hasQuantityValue "50"^^xsd:float.</pre></div>
+	:hasQuantityValue &quot;50&quot;^^xsd:float.</pre></div>
 	</section>
 	</section>
 	
-	<section id="use-case-aggregate-resources" rel="bibo:chapter" resource="#uc-aggregate_resources" typeof="bibo:Chapter">
+	<section typeof="bibo:Chapter" resource="#uc-aggregate_resources" rel="bibo:chapter" id="use-case-aggregate-resources">
 	<h3 id="uc-aggregate_resources"><span class="secno">4.6 </span>Use Case: Aggregate resources</h3>
 	<p>
 		There is a requirement to be able to manage <i>collections</i> of
@@ -1428,23 +1434,23 @@
 		may belong to multiple collections, or to none.
 	</p>
 	<ul>
-		<li>Resource descriptions are a "mix of simple data and
-			collections" (from <a href="#story-tracking_relationships" title="">#Keeping Track of Personal and Business
+		<li>Resource descriptions are a &quot;mix of simple data and
+			collections&quot; (from <a title="" href="#story-tracking_relationships">#Keeping Track of Personal and Business
 				Relationships</a>).
 		</li>
-		<li>Relative URIs: It should be possible to "ship payloads of
-			RDF" for a collection as a whole without breaking internal links
-			(from <a href="#story-constrained_devices" title="">Constrained
+		<li>Relative URIs: It should be possible to &quot;ship payloads of
+			RDF&quot; for a collection as a whole without breaking internal links
+			(from <a title="" href="#story-constrained_devices">Constrained
 				Devices and Networks</a>).
 		</li>
 	</ul>
 	
-	<section id="primary-scenario-add-a-resource-to-a-collection" rel="bibo:chapter" resource="#scen-add_a_resource_to_a_collection" typeof="bibo:Chapter">
+	<section typeof="bibo:Chapter" resource="#scen-add_a_resource_to_a_collection" rel="bibo:chapter" id="primary-scenario-add-a-resource-to-a-collection">
 	<h4 id="scen-add_a_resource_to_a_collection"><span class="secno">4.6.1 </span>Primary scenario: add a resource
 			to a collection</h4>
 	<p>
-		This example is from <a href="#story-lld" title="">Library
-			Linked Data</a> and LLD-UC [<cite><a href="#bib-LLD-UC" class="bibref">LLD-UC</a></cite>], specifically <a href="http://www.w3.org/2005/Incubator/lld/wiki/Use_Case_Subject_Search" title="http://www.w3.org/2005/Incubator/lld/wiki/Use_Case_Subject_Search" rel="nofollow">Subject Search</a>.
+		This example is from <a title="" href="#story-lld">Library
+			Linked Data</a> and LLD-UC [<cite><a class="bibref" href="#bib-LLD-UC">LLD-UC</a></cite>], specifically <a rel="nofollow" title="http://www.w3.org/2005/Incubator/lld/wiki/Use_Case_Subject_Search" href="http://www.w3.org/2005/Incubator/lld/wiki/Use_Case_Subject_Search">Subject Search</a>.
 	</p>
 	<p>There is an existing collection at
 		&lt;http://example.com/concept-scheme/subject-heading&gt; that
@@ -1452,7 +1458,7 @@
 		defined as a skos:ConceptScheme and the client wishes to insert a
 		new concept into the scheme. which will be related to the
 		collection via a skos:inScheme link. The new subject-heading,
-		"outer space exploration", is not necessarily owned by a
+		&quot;outer space exploration&quot;, is not necessarily owned by a
 		container. The following RDF would be added to the (item-level)
 		description of the collection.</p>
 	<div class="example"><div class="example-title"><span>Example 13</span></div><pre class="example">@prefix scheme : &lt;http://example.com/concept-scheme/&gt;.
@@ -1463,7 +1469,7 @@
 concept:Outer+space+Exploration skos:inScheme scheme:subject-heading.</pre></div>
 	</section>
 	
-	<section id="alternative-scenario-add-a-resource-to-multiple-collections" rel="bibo:chapter" resource="#scen-add_a_resource_to_multiple_collections" typeof="bibo:Chapter">
+	<section typeof="bibo:Chapter" resource="#scen-add_a_resource_to_multiple_collections" rel="bibo:chapter" id="alternative-scenario-add-a-resource-to-multiple-collections">
 	<h4 id="scen-add_a_resource_to_multiple_collections"><span class="secno">4.6.2 </span>Alternative scenario: add a
 			resource to multiple collections</h4>
 	<p>
@@ -1475,8 +1481,8 @@
 		collections.
 	</p>
 	<p>
-		As a machine-readable collection of medical terms, the <a href="http://www.ihtsdo.org|" title="http://www.ihtsdo.org|" rel="nofollow">SNOMED</a> ontology
-		is of key importance in <a href="#Healthcare" title="">
+		As a machine-readable collection of medical terms, the <a rel="nofollow" title="http://www.ihtsdo.org|" href="http://www.ihtsdo.org|">SNOMED</a> ontology
+		is of key importance in <a title="" href="#Healthcare">
 			healthcare</a>. SNOMED CT allows concepts with more than one parent
 		that don't fall into a lattice. In the example below, the same
 		concept may fall under two different parent concepts. The example
@@ -1485,19 +1491,19 @@
 	<div class="example"><div class="example-title"><span>Example 14</span></div><pre class="example">@prefix : &lt;http://example.com/snomed/&gt;.
 
 :_119376003 a skos:Concept ;
-	skos:prefLabel "Tissue specimen"
+	skos:prefLabel &quot;Tissue specimen&quot;
 	skos:narrowerTransitive :TissueSpecimenFromHeart.
    
 :_127462005 a skos:Concept ;
-	skos:prefLabel "Specimen from heart"
+	skos:prefLabel &quot;Specimen from heart&quot;
    skos:narrowerTransitive :TissueSpecimenFromHeart.
 
 :_128166000 a skos:Concept;
-	rdfs:label "Tissue specimen from heart".</pre></div>
+	rdfs:label &quot;Tissue specimen from heart&quot;.</pre></div>
 	</section>
 	</section>
 	
-	<section id="use-case-filter-resource-description" rel="bibo:chapter" resource="#uc-filter_resource_description" typeof="bibo:Chapter">
+	<section typeof="bibo:Chapter" resource="#uc-filter_resource_description" rel="bibo:chapter" id="use-case-filter-resource-description">
 	<h3 id="uc-filter_resource_description"><span class="secno">4.7 </span>Use Case: Filter resource description</h3>
 	<p>This use-case extends the normal behaviour of retrieving an
 		RDF description of a resource, by dynamically excluding specific
@@ -1505,19 +1511,19 @@
 		be able to read a collection, or item-level description that
 		excludes the container membership.</p>
 		
-	<section id="primary-scenario-retrieve-collection-level-description" rel="bibo:chapter" resource="#scen-retrieve_collection-level_description" typeof="bibo:Chapter">
+	<section typeof="bibo:Chapter" resource="#scen-retrieve_collection-level_description" rel="bibo:chapter" id="primary-scenario-retrieve-collection-level-description">
 	<h4 id="scen-retrieve_collection-level_description"><span class="secno">4.7.1 </span>Primary scenario: retrieve
 			collection-level description</h4>
 	<p>
-		This scenario, based on <a href="#Library_Linked_Data" title="">
-			Library Linked Data</a>, uses the Dublin Core Metadata Initiative <a href="http://dublincore.org/groups/collections/collection-application-profile/|" title="http://dublincore.org/groups/collections/collection-application-profile/|" rel="nofollow">Collection-Level</a> description. A collection can
+		This scenario, based on <a title="" href="#Library_Linked_Data">
+			Library Linked Data</a>, uses the Dublin Core Metadata Initiative <a rel="nofollow" title="http://dublincore.org/groups/collections/collection-application-profile/|" href="http://dublincore.org/groups/collections/collection-application-profile/|">Collection-Level</a> description. A collection can
 		refer to any aggregation of physical or digital items. This
 		scenario covers the case whereby a client can request a
 		collection-level description as typified by the example below,
 		without necessarily having to download a full listing of the items
 		within the collection.
 	</p>
-	<div class="example"><div class="example-title"><span>Example 15</span></div><pre class="example">@prefix rdf: &lt;rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"&gt;.
+	<div class="example"><div class="example-title"><span>Example 15</span></div><pre class="example">@prefix rdf: &lt;rdf=&quot;http://www.w3.org/1999/02/22-rdf-syntax-ns#&quot;&gt;.
 @prefix dc: &lt;http://purl.org/dc/elements/1.1/&gt;.
 @prefix : &lt;http://example.org/bookshelf/&gt;.
 @prefix dcmitype: &lt;http://purl.org/dc/dcmitype/&gt;.
@@ -1525,17 +1531,17 @@
 @prefix dcterms: &lt;http://purl.org/dc/terms/&gt;.
  
 &lt;&gt; dc:type dcmitype:Collection ;
-	dc:title "Directory of organizations working with Linked Data" ;
-	dcterms:abstract "This is a directory of organisations specializing in Linked Data."
+	dc:title &quot;Directory of organizations working with Linked Data&quot; ;
+	dcterms:abstract &quot;This is a directory of organisations specializing in Linked Data.&quot;
 	cld:isLocatedAt &lt;http://dir.w3.org&gt;
 	cld:isAccessedVia &lt;http://dir.w3.org/rdf/2012/directory/directory-list.xhtml?construct&gt;</pre></div>
 	</section>
 	
-	<section id="alternative-scenario-retrieve-item-level-description-of-a-collection" rel="bibo:chapter" resource="#scen-retrieve_item-level_description_of_a_collection" typeof="bibo:Chapter">
+	<section typeof="bibo:Chapter" resource="#scen-retrieve_item-level_description_of_a_collection" rel="bibo:chapter" id="alternative-scenario-retrieve-item-level-description-of-a-collection">
 	<h4 id="scen-retrieve_item-level_description_of_a_collection"><span class="secno">4.7.2 </span>Alternative scenario: retrieve
 			item-level description of a collection</h4>
 	<p>
-		This use-case scenario, also based on <a href="#story-lld" title=""> Library Linked Data</a>,
+		This use-case scenario, also based on <a title="" href="#story-lld"> Library Linked Data</a>,
 		focuses on obtaining an item-level description of the resources
 		aggregated by a collection. The simplest scenario is where the
 		members of a collection are returned within a single
@@ -1545,19 +1551,19 @@
 		rdfs:member, but many different membership predicates are in
 		common use, including RDF Lists. Item-level descriptions can be
 		captured using the Functional Requirements for Bibliographic
-		Records (<a href="http://www.ifla.org/publications/functional-requirements-for-bibliographic-records" title="http://www.ifla.org/publications/functional-requirements-for-bibliographic-records" rel="nofollow">FRBR</a>) <a href="http://vocab.org/frbr/core.html" class="external text" title="http://vocab.org/frbr/core.html" rel="nofollow">ontology</a>.
+		Records (<a rel="nofollow" title="http://www.ifla.org/publications/functional-requirements-for-bibliographic-records" href="http://www.ifla.org/publications/functional-requirements-for-bibliographic-records">FRBR</a>) <a rel="nofollow" title="http://vocab.org/frbr/core.html" class="external text" href="http://vocab.org/frbr/core.html">ontology</a>.
 	</p>
 	<div class="example"><div class="example-title"><span>Example 16</span></div><pre class="example">@prefix frbr: &lt;http://purl.org/vocab/frbr/core#&gt;.
 
 &lt;&gt; rdfs:member &lt;#ebooks97&gt;, &lt;#ebooks21279&gt;.
 
 &lt;#work97&gt; a frbr:LiteraryWork;
-   dc:title "Flatland: a romance of many dimensions" ;
+   dc:title &quot;Flatland: a romance of many dimensions&quot; ;
 	frbr:creator &lt;#Abbott_Edwin&gt;;
 	frbr:manifestation &lt;ebook97&gt;.
  
 &lt;#work21279&gt; a frbr:LiteraryWork;
-	dc:title "2 B R 0 2 B" ;
+	dc:title &quot;2 B R 0 2 B&quot; ;
 	frbr:creator &lt;#Vonnegut_Kurt&gt;;
 	frbr:manifestation &lt;ebook21279&gt;.</pre></div>
 	<p>Collections are potentially very large, so some means may be
@@ -1566,17 +1572,17 @@
 	</section>
 	</section>
 	
-	<section id="use-case-manage-media-resources" rel="bibo:chapter" resource="#uc-manage_media_resources" typeof="bibo:Chapter">
+	<section typeof="bibo:Chapter" resource="#uc-manage_media_resources" rel="bibo:chapter" id="use-case-manage-media-resources">
 	<h3 id="uc-manage_media_resources"><span class="secno">4.8 </span>Use Case: Manage media resources</h3>
 	<p>It should be possible to easily add non-RDF media resources
 		to containers that accept them. Media resources may be updated and
 		removed during the lifecycle of the container.</p>
 		
-	<section id="primary-scenario-access-media-resources" rel="bibo:chapter" resource="#scen-access_media_resources" typeof="bibo:Chapter">
+	<section typeof="bibo:Chapter" resource="#scen-access_media_resources" rel="bibo:chapter" id="primary-scenario-access-media-resources">
 	<h4 id="scen-access_media_resources"><span class="secno">4.8.1 </span>Primary scenario: access media
 			resources</h4>
 	<p>
-		From the User Story <a href="#Sharing_Binary_Resources_and_Metadata" title="">
+		From the User Story <a title="" href="#Sharing_Binary_Resources_and_Metadata">
 			Sharing Binary Resources and Metadata</a> it should be possible to
 		easily add non-RDF resources to containers that accept them.
 		Clients submit a non-RDF representation to a container in a media
@@ -1590,7 +1596,7 @@
 	<p>
 		This example uses the Ontology
 			for Media Resources to describe a media resource added to a
-		collection [<cite><a href="#bib-MEDIAONT" class="bibref">MEDIAONT</a></cite>].
+		collection [<cite><a class="bibref" href="#bib-MEDIAONT">MEDIAONT</a></cite>].
 	</p>
 	<div class="example"><div class="example-title"><span>Example 17</span></div><pre class="example">@prefix ma: &lt;http://www.w3.org/ns/ma-ont#&gt; .
 
@@ -1598,10 +1604,10 @@
 	:hasMember &lt;dataset/image1.jpg&gt;
 
 &lt;dataset/image1.jpg&gt; a ma:MediaResource ;
-	ma:hasFormat "image/jpeg" .</pre></div>
+	ma:hasFormat &quot;image/jpeg&quot; .</pre></div>
 	</section>
 	
-	<section id="alternative-scenario-media-resource-attachments" rel="bibo:chapter" resource="#scen-media_attachments" typeof="bibo:Chapter">
+	<section typeof="bibo:Chapter" resource="#scen-media_attachments" rel="bibo:chapter" id="alternative-scenario-media-resource-attachments">
 	<h4 id="scen-media_attachments"><span class="secno">4.8.2 </span>Alternative scenario:
 			media-resource attachments</h4>
 	<p>
@@ -1623,86 +1629,88 @@
 	</section>
 </section>
 
-<section id="requirements" rel="bibo:chapter" resource="#reqs" typeof="bibo:Chapter">
-<!--OddPage--><h2 id="reqs"><span class="secno">5. </span>Requirements</h2>
+<section typeof="bibo:Chapter" resource="#reqs" rel="bibo:chapter" id="requirements">
 
-<section id="functional-requirements" rel="bibo:chapter" resource="#reqs-functional" typeof="bibo:Chapter">
+<!--OddPage-->
+<h2 id="reqs"><span class="secno">5. </span>Requirements</h2>
+
+<section typeof="bibo:Chapter" resource="#reqs-functional" rel="bibo:chapter" id="functional-requirements">
 	<h3 id="reqs-functional"><span class="secno">5.1 </span>Functional Requirements</h3>
 	<ol>
-		<li>Create Containers, from <a href="#uc-manage_containers" title="">Use Case: Manage containers</a>
+		<li>Create Containers, from <a title="" href="#uc-manage_containers">Use Case: Manage containers</a>
 		</li>
-		<li>Creation of nested containers, from <a href="#uc-manage_containers" title="">Use Case: Manage
+		<li>Creation of nested containers, from <a title="" href="#uc-manage_containers">Use Case: Manage
 				containers</a>
 		</li>
-		<li>Creation of resources (within a container), from <a href="#uc-manage_resources" title="">Use Case: Manage resources</a>
+		<li>Creation of resources (within a container), from <a title="" href="#uc-manage_resources">Use Case: Manage resources</a>
 		</li>
-		<li>Deletion of resources, from <a href="#uc-amnage_resources" title="">Use Case: Manage resources</a>
+		<li>Deletion of resources, from <a title="" href="#uc-amnage_resources">Use Case: Manage resources</a>
 		</li>
-		<li>Moving contained resources, from <a href="#uc-manage_resources" title="">Use Case: Manage resources</a>
+		<li>Moving contained resources, from <a title="" href="#uc-manage_resources">Use Case: Manage resources</a>
 		</li>
-		<li>Retrieve resource description, from <a href="#uc-retrieve_resource_description" title="">Use Case:
+		<li>Retrieve resource description, from <a title="" href="#uc-retrieve_resource_description">Use Case:
 				Retrieve resource description</a>
 		</li>
-		<li>Retrieve description of a non-document resource, from <a href="#uc-retrieve_resource_description" title="">Use Case:
+		<li>Retrieve description of a non-document resource, from <a title="" href="#uc-retrieve_resource_description">Use Case:
 				Retrieve resource description</a>
 		</li>
 		<li>Enrichment (substituting update of existing resource),
-			from <a href="#uc-update_existing" title="">Use Case:
+			from <a title="" href="#uc-update_existing">Use Case:
 				Update existing resource</a>
 		</li>
-		<li>Selective update of a resource, from <a href="#uc-update_existing" title="">Use Case: Update
+		<li>Selective update of a resource, from <a title="" href="#uc-update_existing">Use Case: Update
 				existing resource</a>
 		</li>
-		<li>Determine if a resource has changed, from <a href="#uc-has_resource_changed" title="">Use Case:
+		<li>Determine if a resource has changed, from <a title="" href="#uc-has_resource_changed">Use Case:
 				Determine if a resource has changed</a>
 		</li>
-		<li>Add a resource to a collection, from <a href="#uc-aggregate_resources" title="">Use Case: Aggregate
+		<li>Add a resource to a collection, from <a title="" href="#uc-aggregate_resources">Use Case: Aggregate
 				resources</a>
 		</li>
-		<li>Add a resource to multiple collections, from <a href="#uc-aggregate_resources" title="">Use Case: Aggregate
+		<li>Add a resource to multiple collections, from <a title="" href="#uc-aggregate_resources">Use Case: Aggregate
 				resources</a>
 		</li>
-		<li>Retrieve collection-level description, from <a href="#uc-filter_resource_description" title="">Use Case:
+		<li>Retrieve collection-level description, from <a title="" href="#uc-filter_resource_description">Use Case:
 				Filter resource description</a>
 		</li>
-		<li>Retrieve item-level description of a collection, from <a href="#uc-filter_resource_description" title="">Use Case:
+		<li>Retrieve item-level description of a collection, from <a title="" href="#uc-filter_resource_description">Use Case:
 				Filter resource description</a>
 		</li>
-		<li>Access media resources, from <a href="#uc-manage_media_resources" title="">Use Case: Manage
+		<li>Access media resources, from <a title="" href="#uc-manage_media_resources">Use Case: Manage
 				media resources</a>
 		</li>
-		<li>Media-resource attachments, from <a href="#uc-manage_media_resources" title="">Use Case: Manage
+		<li>Media-resource attachments, from <a title="" href="#uc-manage_media_resources">Use Case: Manage
 				media resources</a>
 		</li>
 	</ol>
 	</section>
 	
-	<section id="non-functional-requirements" rel="bibo:chapter" resource="#reqs-non-functional" typeof="bibo:Chapter">
+	<section typeof="bibo:Chapter" resource="#reqs-non-functional" rel="bibo:chapter" id="non-functional-requirements">
 	<h3 id="reqs-non-functional"><span class="secno">5.2 </span>Non-Functional Requirements</h3>
 	<ol>
-		<li>Provide access guidance to resources, from <a href="#uc-manage_containers" title="">Use Case: Manage
+		<li>Provide access guidance to resources, from <a title="" href="#uc-manage_containers">Use Case: Manage
 				containers</a>
 		</li>
-		<li>Non-duplication of resources, from <a href="#uc-manage_resources" title="">Use Case: Manage resources</a>
+		<li>Non-duplication of resources, from <a title="" href="#uc-manage_resources">Use Case: Manage resources</a>
 		</li>
-		<li>Distribution of resources, from <a href="#uc-manage_resources" title="">Use Case: Manage resources</a>
+		<li>Distribution of resources, from <a title="" href="#uc-manage_resources">Use Case: Manage resources</a>
 		</li>
-		<li>Consistent, global naming, from <a href="#uc-manage_resources" title="">Use Case: Manage resources</a>
+		<li>Consistent, global naming, from <a title="" href="#uc-manage_resources">Use Case: Manage resources</a>
 		</li>
-		<li>Use standard vocabularies as appropriate, from <a href="#uc-retrieve_resource_description" title="">Use Case:
+		<li>Use standard vocabularies as appropriate, from <a title="" href="#uc-retrieve_resource_description">Use Case:
 				Retrieve resource description</a>
 		</li>
-		<li>Scalable linking model, from <a href="#uc-retrieve_resource_description" title="">Use Case:
+		<li>Scalable linking model, from <a title="" href="#uc-retrieve_resource_description">Use Case:
 				Retrieve resource description</a>
 		</li>
-		<li>Unrestricted vocabulary, from <a href="#uc-update_existing" title="">Use Case: Update
+		<li>Unrestricted vocabulary, from <a title="" href="#uc-update_existing">Use Case: Update
 				existing resource</a>
 		</li>
-		<li>Resource descriptions are a "mix of simple data and
-			collections", from <a href="#uc-aggregate_resources" title="">Use Case:
+		<li>Resource descriptions are a &quot;mix of simple data and
+			collections&quot;, from <a title="" href="#uc-aggregate_resources">Use Case:
 				Aggregate resources</a>
 		</li>
-		<li>Relative URIs enabling sharing of collections, from <a href="#uc-aggregate_resources" title="">Use Case: Aggregate
+		<li>Relative URIs enabling sharing of collections, from <a title="" href="#uc-aggregate_resources">Use Case: Aggregate
 				resources</a>
 		</li>
 	</ol>
@@ -1710,14 +1718,18 @@
 </section>
 
 
-<section id="acknowledgements" class="appendix informative">
-<!--OddPage--><h2><span class="secno">A. </span>Acknowledgements</h2><p><em>This section is non-normative.</em></p>
+<section class="appendix informative" id="acknowledgements">
+
+<!--OddPage-->
+<h2><span class="secno">A. </span>Acknowledgements</h2><p><em>This section is non-normative.</em></p>
 <p>We would like to acknowledge the contributions of user-story authors: Christophe Guéret,
 Roger Menday, Eric Prud'hommeaux, Steve Speicher, John Arwe, Kevin Page.</p>
 </section>
     
-<section rel="bibo:chapter" resource="#history" typeof="bibo:Chapter" class="appendix informative" id="history">
-<!--OddPage--><h2><span class="secno">B. </span>Change History</h2><p><em>This section is non-normative.</em></p>
+<section id="history" class="appendix informative" typeof="bibo:Chapter" resource="#history" rel="bibo:chapter">
+
+<!--OddPage-->
+<h2><span class="secno">B. </span>Change History</h2><p><em>This section is non-normative.</em></p>
 <ul>
 	<li>2012-12-14 - Initial ReSpec'ing framework for <a href="http://www.w3.org/2012/ldp/wiki/Use_Cases_And_Requirements">Workgroup working wiki document</a> (SS)</li>
 	<li>2012-12-16 - Pulled in and ReSpec'd content from <a href="http://www.w3.org/2012/ldp/wiki/Use_Cases_And_Requirements">Workgroup working wiki document</a> (SS)</li>
@@ -1726,7 +1738,9 @@
     
   
 
-<section rel="bibo:chapter" resource="#references" typeof="bibo:Chapter" class="appendix" id="references"><!--OddPage--><h2><span class="secno">C. </span>References</h2><section rel="bibo:chapter" resource="#informative-references" typeof="bibo:Chapter" id="informative-references"><h3><span class="secno">C.1 </span>Informative references</h3><dl about="" class="bibliography"><dt id="bib-COAP">[COAP]</dt><dd rel="dcterms:references">E Shelby; et al. <a href="http://tools.ietf.org/html/draft-ietf-core-coap"><cite>Constrained Application Protocol (CoAP)</cite></a>. IETF Internet Draft, December 2012. URL: <a href="http://tools.ietf.org/html/draft-ietf-core-coap">http://tools.ietf.org/html/draft-ietf-core-coap</a>
+<section id="references" class="appendix" typeof="bibo:Chapter" resource="#references" rel="bibo:chapter">
+<!--OddPage-->
+<h2><span class="secno">C. </span>References</h2><section id="informative-references" typeof="bibo:Chapter" resource="#informative-references" rel="bibo:chapter"><h3><span class="secno">C.1 </span>Informative references</h3><dl class="bibliography" about=""><dt id="bib-COAP">[COAP]</dt><dd rel="dcterms:references">E Shelby; et al. <a href="http://tools.ietf.org/html/draft-ietf-core-coap"><cite>Constrained Application Protocol (CoAP)</cite></a>. IETF Internet Draft, December 2012. URL: <a href="http://tools.ietf.org/html/draft-ietf-core-coap">http://tools.ietf.org/html/draft-ietf-core-coap</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-DAP-REQS">[DAP-REQS]</dt><dd rel="dcterms:references">Robin Berjon et al. <a href="http://www.w3.org/TR/2009/NOTE-dap-api-reqs-20091015/"><cite>Device API Requirementsml</cite></a> 15 October 2009. Working Group Note. URL: <a href="http://www.w3.org/TR/2009/NOTE-dap-api-reqs-20091015/">http://www.w3.org/TR/2009/NOTE-dap-api-reqs-20091015/</a>
 </dd><dt id="bib-DCAT-UCR">[DCAT-UCR]</dt><dd rel="dcterms:references">R. Cyganiak; F. Maali. <a href="http://dvcs.w3.org/hg/gld/raw-file/default/dcat-ucr/index.html"><cite>Use Cases and Requirements for the Data Catalog Vocabulary</cite></a> 16 December 2012. W3C Editor's Draft. URL: <a href="http://dvcs.w3.org/hg/gld/raw-file/default/dcat-ucr/index.html">http://dvcs.w3.org/hg/gld/raw-file/default/dcat-ucr/index.html</a>.