why respec output <section> here?
authorYves Lafon <ylafon@w3.org>
Mon, 28 Jan 2013 16:49:03 +0100
changeset 47 a4349bff5f64
parent 46 a56c74d03222
child 48 ed18dfa6c561
child 52 6252c6802ae2
child 53 eff1638769ae
why respec output <section> here?
TR/ldp-ucr.html
--- a/TR/ldp-ucr.html	Mon Jan 28 16:29:03 2013 +0100
+++ b/TR/ldp-ucr.html	Mon Jan 28 16:49:03 2013 +0100
@@ -31,7 +31,7 @@
             min-width: 7.5em;
     	}
     </style>
-  <style>/*****************************************************************
+  <style type="text/css">/*****************************************************************
  * ReSpec 3 CSS
  * Robin Berjon - http://berjon.com/
  *****************************************************************/
@@ -146,7 +146,7 @@
 .section dl.attrs dd, .section dl.eldef dd {
     margin-bottom:  0;
 }
-</style><style>/* --- EXAMPLES --- */
+</style><style type="text/css">/* --- EXAMPLES --- */
 div.example-title {
     min-width: 7.5em;
     color: #b9ab2d;
@@ -238,11 +238,11 @@
   
   <hr />
 </div>
-<section id="abstract" class="introductory" property="dcterms:abstract" datatype="" typeof="bibo:Chapter" resource="#abstract" rel="bibo:chapter"><h2>Abstract</h2><p>
+<div 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 class="introductory" id="sotd" typeof="bibo:Chapter" resource="#sotd" rel="bibo:chapter"><h2>Status of This Document</h2>
+</p></div><div class="introductory" id="sotd" typeof="bibo:Chapter" resource="#sotd" rel="bibo:chapter"><h2>Status of This Document</h2>
   
     
       
@@ -257,9 +257,9 @@
           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>.
           
           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>).
+          <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/">archives</a>).
           
         All comments are welcome.
         
@@ -292,7 +292,7 @@
       
     
   
-</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
+</div><div 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
@@ -310,13 +310,13 @@
 			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>
+			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></div>
 
-<section id="status" typeof="bibo:Chapter" resource="#status" rel="bibo:chapter">
+<div id="status" typeof="bibo:Chapter" resource="#status" rel="bibo:chapter">
 
-</section>
+</div>
  
-<section typeof="bibo:Chapter" resource="#scope" rel="bibo:chapter" id="scope-and-motivation">
+<div 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>
@@ -400,9 +400,9 @@
 		Data relies on a flexible data model with RDF, which allows for
 		multiple representations.</p>
 
-</section>
+</div>
 
-<section typeof="bibo:Chapter" resource="#org" rel="bibo:chapter" id="organization-of-this-document">
+<div 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>
@@ -460,14 +460,14 @@
 			stem from use-cases. It is also possible at this stage to
 			explicitly identify some use-cases as non-requirements.</li>
 	</ul>
-</section>
+</div>
 	
-<section typeof="bibo:Chapter" resource="#userstories" rel="bibo:chapter" id="user-stories">
+<div typeof="bibo:Chapter" resource="#userstories" rel="bibo:chapter" id="user-stories">
 
 <!--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">
+	<div 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 –
@@ -509,9 +509,9 @@
 		at an email provider), it would be nice if they all worked pretty
 		much the same way.
 	</p>
-	</section>
+	</div>
 	
-	<section typeof="bibo:Chapter" resource="#story-tracking_relationships" rel="bibo:chapter" id="keeping-track-of-personal-and-business-relationships">
+	<div 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
@@ -548,9 +548,9 @@
 		<a title="" href="#scen-create_a_nested_container">a collection of accounts for each member of its collection
 			of customers</a>.
 	</p>
-	</section>
+	</div>
 	
-	<section typeof="bibo:Chapter" resource="#story-oslc" rel="bibo:chapter" id="system-and-software-development-tool-integration">
+	<div 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
@@ -593,9 +593,9 @@
 		satisfactory. The use of Linked Data as an application integration
 		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>
+	</div>
 	
-	<section typeof="bibo:Chapter" resource="#story-lld" rel="bibo:chapter" id="library-linked-data">
+	<div 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
@@ -651,9 +651,9 @@
 		<li>Community information services: Identify and classify
 			collections of special interest to the community.</li>
 	</ul>
-	</section>
+	</div>
 	
-	<section typeof="bibo:Chapter" resource="#story-meter_monitoring" rel="bibo:chapter" id="municipality-operational-monitoring">
+	<div 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>
@@ -671,9 +671,9 @@
 		and dependencies on other data and services, so having a simple
 		and scalable linking model is key.
 	</p>
-	</section>
+	</div>
 	
-	<section typeof="bibo:Chapter" resource="#story-healthcare" rel="bibo:chapter" id="healthcare">
+	<div 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
@@ -697,9 +697,9 @@
 		occurrences of an outbreak, including additional details of
 		symptoms and causes, is critical in producing the most effective
 		treatment for future incidents.</p>
-	</section>	
+	</div>	
 	
-	<section typeof="bibo:Chapter" resource="#story-media" rel="bibo:chapter" id="metadata-enrichment-in-broadcasting">
+	<div 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
@@ -723,9 +723,9 @@
 		discovery, automation, disambiguation, etc. Other important issues
 		that broadcasters would face are the editorial quality of the
 		linked data, its persistence, and usage rights.</p>
-	</section>
+	</div>
 		
-	<section typeof="bibo:Chapter" resource="#story-mashup" rel="bibo:chapter" id="aggregation-and-mashups-of-infrastructure-data">
+	<div 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
@@ -756,9 +756,9 @@
 		independent from the internal data model of the sources that are
 		being combined, and can be used for pull-based interactions as
 		well as for push-based interactions.</p>
-	</section>
+	</div>
 	
-	<section typeof="bibo:Chapter" resource="#story-low-end_devices" rel="bibo:chapter" id="sharing-payload-of-rdf-data-among-low-end-devices">
+	<div 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 rel="nofollow" title="http://worldwidesemanticweb.wordpress.com/" href="http://worldwidesemanticweb.wordpress.com/">downscaling
@@ -780,9 +780,9 @@
 		are rather demanding pieces of software that are not always usable
 		on limited hardware. Some generic REST-like interaction backed up
 		with a lightweight column store would be better approach.</p>
-	</section>
+	</div>
 	
-	<section typeof="bibo:Chapter" resource="#story-binary_and_metadata" rel="bibo:chapter" id="sharing-binary-resources-and-metadata">
+	<div 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
@@ -805,9 +805,9 @@
 		vital. It's a compound item of image data and other data (application 
 		metadata about the image) does are not distinguished from the
 		platform's point-of-view.</p>
-	</section>
+	</div>
 	
-	<section typeof="bibo:Chapter" resource="#story-data_catalogs" rel="bibo:chapter" id="data-catalogs">
+	<div 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 rel="nofollow" title="http://joinup.ec.europa.eu/asset/adms/home" href="http://joinup.ec.europa.eu/asset/adms/home">ADMS</a>)
@@ -839,9 +839,9 @@
 	<p>
 		Related: <a rel="nofollow" title="http://spec.datacatalogs.org/" href="http://spec.datacatalogs.org/">Data Catalog Schema and Protocol</a>
 	</p>
-	</section>
+	</div>
 	
-	<section typeof="bibo:Chapter" resource="#story-constrained_devices" rel="bibo:chapter" id="constrained-devices-and-networks">
+	<div 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
@@ -868,9 +868,9 @@
 		devices to directly participate in a Linked Data-based
 		environment.
 	</p>
-	</section>
+	</div>
 	
-	<section typeof="bibo:Chapter" resource="#story-process_of_science" rel="bibo:chapter" id="services-supporting-the-process-of-science">
+	<div 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
@@ -910,9 +910,9 @@
 	<p>
 		seeAlso: <a rel="nofollow" title="http://www.wf4ever-project.org/" href="http://www.wf4ever-project.org/">Wf4Ever</a>
 	</p>
-	</section>
+	</div>
 	
-	<section typeof="bibo:Chapter" resource="#story-project_data" rel="bibo:chapter" id="project-membership-information-information-evolution">
+	<div 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.
@@ -941,9 +941,9 @@
 		<li>Access to historical state, via access to a specific
 			version of the resource description</li>
 	</ul>
-	</section>
+	</div>
 	
-	<section typeof="bibo:Chapter" resource="#story-cloud" rel="bibo:chapter" id="cloud-infrastructure-management">
+	<div 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,11 +972,11 @@
 	</ul>
 	<p>Infrastructure management may be viewed as the manipulation
 		of the underlying graph of resources.</p>
-	</section>
+	</div>
 
-</section>
+</div>
 
-<section typeof="bibo:Chapter" resource="#usecases" rel="bibo:chapter" id="use-cases">
+<div typeof="bibo:Chapter" resource="#usecases" rel="bibo:chapter" id="use-cases">
 
 <!--OddPage-->
 <h2 id="usecases"><span class="secno">4. </span>Use Cases</h2>
@@ -988,7 +988,7 @@
 		contain are included purely for illustrative purposes, and should
 		not be interpreted normatively.</p>
 		
-	<section typeof="bibo:Chapter" resource="#uc-manage_containers" rel="bibo:chapter" id="use-case-manage-containers">
+	<div 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>
@@ -1009,7 +1009,7 @@
 		</li>
 	</ul>
 	
-	<section typeof="bibo:Chapter" resource="#scen-create_container" rel="bibo:chapter" id="primary-scenario-create-container">
+	<div 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>
@@ -1030,9 +1030,9 @@
 
 &lt;&gt; a ro:ResearchObject, ore:Aggregation ;
     dct:created &quot;2012-12-01&quot;^^xsd:dateTime .</pre></div>
-	</section>
+	</div>
 	
-	<section typeof="bibo:Chapter" resource="#scen-create_a_nested_container" rel="bibo:chapter" id="alternative-scenario-create-a-nested-container">
+	<div 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>
@@ -1061,10 +1061,10 @@
 
 :attachments a oslc_cm:AttachmentList;
       oslc_cm:attachment :attachment324, :attachment251.</pre></div>
-	</section>
-	</section>
+	</div>
+	</div>
 	
-	<section typeof="bibo:Chapter" resource="#uc-manage_resources" rel="bibo:chapter" id="use-case-manage-resources">
+	<div 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
@@ -1107,7 +1107,7 @@
 		</li>
 	</ul>
 	
-	<section typeof="bibo:Chapter" resource="#scen-create_resource" rel="bibo:chapter" id="primary-scenario-create-resource">
+	<div 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
@@ -1149,9 +1149,9 @@
 		foaf:mbox &lt;mailto:[email protected]&gt;;
 		foaf:workplaceHomepage &lt;http://www.w3.org/&gt;.
 	]</pre></div>
-	</section>
+	</div>
 	
-	<section typeof="bibo:Chapter" resource="#scen-delete_resource" rel="bibo:chapter" id="alternative-scenario-delete-resource">
+	<div 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>
@@ -1165,9 +1165,9 @@
 		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>
+	</div>
 	
-	<section typeof="bibo:Chapter" resource="#scen-moving_contained_resources" rel="bibo:chapter" id="alternative-scenario-moving-contained-resources">
+	<div 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>
@@ -1182,10 +1182,10 @@
 		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>
+	</div>
+	</div>
 	
-	<section typeof="bibo:Chapter" resource="#uc-retrieve_resource_description" rel="bibo:chapter" id="use-case-retrieve-resource-description">
+	<div 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
@@ -1207,7 +1207,7 @@
 		</li>
 	</ul>
 	
-	<section typeof="bibo:Chapter" resource="#scen-fetch" rel="bibo:chapter" id="primary-scenario">
+	<div 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 title="" href="#story-project_data"> Project Membership Information</a> discusses the
@@ -1245,9 +1245,9 @@
 
 &lt;director&gt; a org:Role ;
 	rdfs:label &quot;Director&quot; .</pre></div>
-	</section>
+	</div>
 	
-	<section typeof="bibo:Chapter" resource="#scen-alt_non-document_resource" rel="bibo:chapter" id="alternative-scenario-retrieve-description-of-a-non-document-resource">
+	<div 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
@@ -1267,10 +1267,10 @@
 	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>
+	</div>
+	</div>
 	
-	<section typeof="bibo:Chapter" resource="#uc-update_existing" rel="bibo:chapter" id="use-case-update-existing-resource">
+	<div 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
@@ -1285,7 +1285,7 @@
 		</li>
 	</ul>
 	
-	<section typeof="bibo:Chapter" resource="#scen-update_enrichment" rel="bibo:chapter" id="primary-scenario-enrichment">
+	<div 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 title="" href="#story-media">
@@ -1322,9 +1322,9 @@
         a foaf:Agent ;
         foaf:name &quot;Chris Hoy&quot; .
     ] .</pre></div>
-	</section>
+	</div>
 	
-	<section typeof="bibo:Chapter" resource="#scen-alt_selective_update" rel="bibo:chapter" id="alternative-scenario-selective-update-of-a-resource">
+	<div 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>
@@ -1361,10 +1361,10 @@
     rdf:predicate dcat:dataset ;
     rdf:object :dataset/002 .
   ] .</pre></div>
-	</section>
-	</section>
+	</div>
+	</div>
 	
-	<section typeof="bibo:Chapter" resource="#uc-has_resource_changed" rel="bibo:chapter" id="use-case-determine-if-a-resource-has-changed">
+	<div 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>
@@ -1378,7 +1378,7 @@
 		unchanged.
 	</p>
 	
-	<section typeof="bibo:Chapter" resource="#scen-primary_has_changed" rel="bibo:chapter" id="primary-scenario-1">
+	<div 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 title="" href="#story-constrained_devices">
@@ -1416,10 +1416,10 @@
 &lt;http://example.com/energy-management#property_1&gt; :hasMeasurementPropertyValue &lt;&gt; .
 &lt;&gt; a :FrequencyValue;
 	:hasQuantityValue &quot;50&quot;^^xsd:float.</pre></div>
-	</section>
-	</section>
+	</div>
+	</div>
 	
-	<section typeof="bibo:Chapter" resource="#uc-aggregate_resources" rel="bibo:chapter" id="use-case-aggregate-resources">
+	<div 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
@@ -1445,7 +1445,7 @@
 		</li>
 	</ul>
 	
-	<section typeof="bibo:Chapter" resource="#scen-add_a_resource_to_a_collection" rel="bibo:chapter" id="primary-scenario-add-a-resource-to-a-collection">
+	<div 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>
@@ -1467,9 +1467,9 @@
 scheme:subject-heading a skos:ConceptScheme.
 
 concept:Outer+space+Exploration skos:inScheme scheme:subject-heading.</pre></div>
-	</section>
+	</div>
 	
-	<section typeof="bibo:Chapter" resource="#scen-add_a_resource_to_multiple_collections" rel="bibo:chapter" id="alternative-scenario-add-a-resource-to-multiple-collections">
+	<div 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>
@@ -1500,10 +1500,10 @@
 
 :_128166000 a skos:Concept;
 	rdfs:label &quot;Tissue specimen from heart&quot;.</pre></div>
-	</section>
-	</section>
+	</div>
+	</div>
 	
-	<section typeof="bibo:Chapter" resource="#uc-filter_resource_description" rel="bibo:chapter" id="use-case-filter-resource-description">
+	<div 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
@@ -1511,7 +1511,7 @@
 		be able to read a collection, or item-level description that
 		excludes the container membership.</p>
 		
-	<section typeof="bibo:Chapter" resource="#scen-retrieve_collection-level_description" rel="bibo:chapter" id="primary-scenario-retrieve-collection-level-description">
+	<div 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>
@@ -1535,9 +1535,9 @@
 	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>
+	</div>
 	
-	<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">
+	<div 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>
@@ -1569,16 +1569,16 @@
 	<p>Collections are potentially very large, so some means may be
 		required to limit the size of RDF representation returned by the
 		<abbr title="Linked Data Platform">LDP</abbr> server (e.g. pagination).</p>
-	</section>
-	</section>
+	</div>
+	</div>
 	
-	<section typeof="bibo:Chapter" resource="#uc-manage_media_resources" rel="bibo:chapter" id="use-case-manage-media-resources">
+	<div 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 typeof="bibo:Chapter" resource="#scen-access_media_resources" rel="bibo:chapter" id="primary-scenario-access-media-resources">
+	<div 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>
@@ -1605,9 +1605,9 @@
 
 &lt;dataset/image1.jpg&gt; a ma:MediaResource ;
 	ma:hasFormat &quot;image/jpeg&quot; .</pre></div>
-	</section>
+	</div>
 	
-	<section typeof="bibo:Chapter" resource="#scen-media_attachments" rel="bibo:chapter" id="alternative-scenario-media-resource-attachments">
+	<div 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>
@@ -1625,16 +1625,16 @@
 		add/remove/replace attachments to the work order during its
 		lifetime.
 	</p>
-	</section>
-	</section>
-</section>
+	</div>
+	</div>
+</div>
 
-<section typeof="bibo:Chapter" resource="#reqs" rel="bibo:chapter" id="requirements">
+<div typeof="bibo:Chapter" resource="#reqs" rel="bibo:chapter" id="requirements">
 
 <!--OddPage-->
 <h2 id="reqs"><span class="secno">5. </span>Requirements</h2>
 
-<section typeof="bibo:Chapter" resource="#reqs-functional" rel="bibo:chapter" id="functional-requirements">
+<div 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 title="" href="#uc-manage_containers">Use Case: Manage containers</a>
@@ -1683,9 +1683,9 @@
 				media resources</a>
 		</li>
 	</ol>
-	</section>
+	</div>
 	
-	<section typeof="bibo:Chapter" resource="#reqs-non-functional" rel="bibo:chapter" id="non-functional-requirements">
+	<div 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 title="" href="#uc-manage_containers">Use Case: Manage
@@ -1714,19 +1714,19 @@
 				resources</a>
 		</li>
 	</ol>
-	</section>
-</section>
+	</div>
+</div>
 
 
-<section class="appendix informative" id="acknowledgements">
+<div 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>
+</div>
     
-<section id="history" class="appendix informative" typeof="bibo:Chapter" resource="#history" rel="bibo:chapter">
+<div 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>
@@ -1734,13 +1734,13 @@
 	<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>
 	<li>2012-12-16 - Fixed cross section links and initial pass at biblio refs (SS)</li>
-</ul></section>
+</ul></div>
     
   
 
-<section id="references" class="appendix" typeof="bibo:Chapter" resource="#references" rel="bibo:chapter">
+<div 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>
+<h2><span class="secno">C. </span>References</h2><div 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>.
@@ -1754,4 +1754,4 @@
 </dd><dt id="bib-RDB2RDF-UC">[RDB2RDF-UC]</dt><dd rel="dcterms:references">Eric Prud'hommeaux; Michael Hausenblas. <a href="http://www.w3.org/TR/2010/WD-rdb2rdf-ucr-20100608/"><cite>Use Cases and Requirements for Mapping Relational Databases to RDF.</cite></a> 8 June 2010. W3C Working Draft. URL: <a href="http://www.w3.org/TR/2010/WD-rdb2rdf-ucr-20100608/">http://www.w3.org/TR/2010/WD-rdb2rdf-ucr-20100608/</a>
 </dd><dt id="bib-RFC5023">[RFC5023]</dt><dd rel="dcterms:references">J. Gregorio, B. de hOra. <a href="http://www.ietf.org/rfc/rfc5023.txt"><cite>Atom Publishing Protocol</cite></a>. IETF RFC 5023. October 2007. URL: <a href="http://www.ietf.org/rfc/rfc5023.txt">http://www.ietf.org/rfc/rfc5023.txt</a>
 </dd><dt id="bib-WEBARCH">[WEBARCH]</dt><dd rel="dcterms:references">Norman Walsh; Ian Jacobs. <a href="http://www.w3.org/TR/2004/REC-webarch-20041215/"><cite>Architecture of the World Wide Web, Volume One.</cite></a> 15 December 2004. W3C Recommendation. URL: <a href="http://www.w3.org/TR/2004/REC-webarch-20041215/">http://www.w3.org/TR/2004/REC-webarch-20041215/</a>
-</dd></dl></section></section></body></html>
+</dd></dl></div></div></body></html>