Fixed up local links and inserted first pass at biblio refs
authorsspeiche
Sun, 16 Dec 2012 13:16:48 -0500
changeset 27 bf23e5525c6f
parent 26 a3eb8135ecc4
child 28 068c4a4f0481
Fixed up local links and inserted first pass at biblio refs
ldp-ucr.html
--- a/ldp-ucr.html	Sun Dec 16 11:37:08 2012 -0500
+++ b/ldp-ucr.html	Sun Dec 16 13:16:48 2012 -0500
@@ -206,7 +206,7 @@
 </p>
 	<p>This document is organized as follows:</p>
 	<ul>
-		<li><b><a href="#user-stories" title=""> User Stories</a></b>
+		<li><b><a href="#userstories" title="User Stories">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
@@ -216,37 +216,29 @@
 			title="http://www.agilemodeling.com/artifacts/userStory.htm"
 			rel="nofollow">[2]</a>. Analysis of each user story will reveal a
 			number of (functional) use-cases and other non-functional
-			requirements. See <a
-			href="http://www.w3.org/TR/dap-policy-reqs/|"
-			class="external text"
-			title="http://www.w3.org/TR/dap-policy-reqs/|" rel="nofollow">Device
-				API Access Control Use Cases and Requirements</a> for a good example
+			requirements. See Device
+				API Access Control Use Cases and Requirements [[DAP-REQS]] for a good example
 			of user stories and their analysis.</li>
 	</ul>
 	<ul>
-		<li><b><a href="#use-cases" title=""> Use Cases</a></b> are
+		<li><b><a href="#use-cases" title="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>,
-			cataloguing who does what with the system, for what purpose, but
+			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
 			reference number to aid cross-reference from other documentation;
-			use-case indexing in this document is based on <a
-			href="http://www.w3.org/TR/rdb2rdf-ucr/" class="external text"
-			title="http://www.w3.org/TR/rdb2rdf-ucr/" rel="nofollow">rdb2rdf
-				use-cases</a>. A variety of styles may be used to capture use-cases,
+			use-case indexing in this document is based on rdb2rdf
+			use-cases [[RDB2RDF-UC]]. 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 behaviours as in <a
-			href="http://www.w3.org/TR/powder-use-cases/"
-			class="external text"
-			title="http://www.w3.org/TR/powder-use-cases/" rel="nofollow">POWDER:
-				Use Cases and Requirements</a>, and non-functional requirements
+			pre/post conditions, and step-by-step behaviors as in POWDER:
+			Use Cases and Requirements [[POWDER-USE-CASES]], 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
@@ -255,24 +247,17 @@
 	<ul>
 		<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 <a
-			href="http://www.w3.org/TR/media-frags-reqs/"
-			class="external text"
-			title="http://www.w3.org/TR/media-frags-reqs/" rel="nofollow">Use
-				cases and requirements for Media Fragments</a>, to being formally
+			lightweight narratives as seen in Use
+			cases and requirements for Media Fragments [[MEDIA-FRAGMENTS-REQS]], 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</a></b>
+		<li><b><a href="#reqs" title="Requirements">Requirements</a></b>
 			lists non-functional or quality requirements, and the use cases
-			they may be derived from. This approach is exemplified in the <a
-			href="http://dvcs.w3.org/hg/gld/raw-file/default/dcat-ucr/index.html"
-			class="external text"
-			title="http://dvcs.w3.org/hg/gld/raw-file/default/dcat-ucr/index.html"
-			rel="nofollow">Use Cases and Requirements for the Data
-				Catalog Vocabulary</a>. It also lists functional requirements that
+			they may be derived from. This approach is exemplified in the Use Cases and Requirements for the Data
+			Catalog Vocabulary [[DCAT-UCR]]. 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>
@@ -307,11 +292,11 @@
 		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="#UC3:_Retrieve_resource_description" title="">reading</a>,
-		<a href="#UC4:_Update_existing_resource" title="">updating</a>,
-		and <a href="#Alternative_scenario:_delete_resource" title="">deleting</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="#Primary_scenario:_create_resource" title="">create a
+			href="#scen-create_resource" title="">create a
 			new contact</a> and 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
@@ -350,20 +335,20 @@
 		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="#UC3:_Retrieve_resource_description" title="">examine</a>
-		or <a href="#UC4:_Update_existing_resource" title="">change</a>
+			href="#uc-retrieve_resource_description" title="">examine</a>
+		or <a href="#uc-update_existing" title="">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="#UC6:_Aggregate_resources" title="">simple collection</a>.
+			href="#uc-aggregate_resources" title="">simple collection</a>.
 		The information held by any single organization might be a mix of
-		simple data and <a href="#UC6:_Aggregate_resources" title="">collections
+		simple data and <a href="#uc-aggregate_resources" title="">collections
 			of other data</a>, for example, a bank account balance and a
 		collection of historical transactions. Our bank might easily have
-		<a href="#Alternative_scenario:_create_a_nested_container"
+		<a href="#scen-create_a_nested_container"
 			title="">a collection of accounts for each of its collection
 			of customers</a>.
 	</p>
@@ -420,11 +405,7 @@
 	<h2 id="story-lld">Library Linked Data</h2>
 	<p>
 		The W3C Library Linked Data working group has a number of use
-		cases cited in their Use Case Report. <a
-			href="http://www.w3.org/2005/Incubator/lld/wiki/UseCaseReport"
-			class="external text"
-			title="http://www.w3.org/2005/Incubator/lld/wiki/UseCaseReport"
-			rel="nofollow">LLD-UC</a> These referenced use cases focus on the
+		cases cited in their Use Case Report [[LLD-UC]]. 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
@@ -436,7 +417,7 @@
 		use-cases:</p>
 	<ul>
 		<li>Grouping: This should "Allow the end-users to define <a
-			href="#UC6:_Aggregate_resources" title="">groups of resources</a>
+			href="#uc-aggregate_resources" title="">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
@@ -445,12 +426,12 @@
 	</ul>
 	<ul>
 		<li>Enrichment: "Enable end-users to <a
-			href="#UC4:_Update_existing_resource" title="">link resources
+			href="#uc-update_existing" title="">link resources
 				together</a>."
 		</li>
 	</ul>
 	<ul>
-		<li>Browsing: "<a href="#UC7:_Filter_resource_description"
+		<li>Browsing: "<a href="#uc-Filter_resource_description"
 			title="">Support end-user browsing through groups</a> and
 			resources that belong to the groups."
 		</li>
@@ -464,7 +445,7 @@
 		use-cases:</p>
 	<ul>
 		<li>Collection-level description: "Provide <a
-			href="#UC7:_Filter_resource_description" title="">metadata
+			href="#uc-filter_resource_description" title="">metadata
 				pertaining to a collection as a whole</a>, in contrast to item-level
 			description."
 		</li>
@@ -483,7 +464,7 @@
 	</section>
 	
 	<section>
-	<h2 id="story-meter-monitoring">Municipality Operational
+	<h2 id="story-meter_monitoring">Municipality Operational
 			Monitoring</h2>
 	<p>
 		Across various cities, towns, counties, and various municipalities
@@ -494,7 +475,7 @@
 		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="#UC3:_Retrieve_resource_description" title="">expose
+			href="#uc-retrieve_resource_description" title="">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
@@ -533,7 +514,7 @@
 	<h2 id="story-media">Metadata Enrichment in Broadcasting</h2>
 	<p>
 		There are many different use cases when broadcasters show interest
-		in metadata <a href="#UC4:_Update_existing_resource" title="">
+		in metadata <a href="#uc-pdate_existing" title="">
 			enrichment</a>:
 	</p>
 	<ul>
@@ -561,9 +542,9 @@
 		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="#UC6:_Aggregate_resources"
+		different sources can be <a href="#uc-aggregate_resources"
 			title="">aggregated</a>, <a
-			href="#UC7:_Filter_resource_description" title="">filtered</a>,
+			href="#uc-filter_resource_description" title="">filtered</a>,
 		and visualized effectively. Specifically, the following use cases
 		need to be taken into account:
 	</p>
@@ -591,11 +572,10 @@
 	</section>
 	
 	<section>
-	<h2 id="story-device">Sharing payload of RDF data among low-end devices</h2>
+	<h2 id="story-low-end_devices">Sharing payload of RDF data among low-end devices</h2>
 	<p>
 		Several projects around the idea of <a
 			href="http://worldwidesemanticweb.wordpress.com/"
-			class="external text"
 			title="http://worldwidesemanticweb.wordpress.com/" rel="nofollow">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
@@ -618,7 +598,7 @@
 	</section>
 	
 	<section>
-	<h2 id="story-binary_and_etadata">Sharing Binary Resources and Metadata</h2>
+	<h2 id="story-binary_and_metadata">Sharing Binary Resources and Metadata</h2>
 	<p>When publishing datasets about stars one may want to publish
 		links to the pictures in which those stars appear, and this may
 		well require publishing the pictures themselves. Vice versa: when
@@ -643,18 +623,17 @@
 	</section>
 	
 	<section>
-	<h2 id="story-data_cats">Data Catalogs</h2>
+	<h2 id="story-data_catalogs">Data Catalogs</h2>
 	<p>
 		The Asset Description Metadata Schema (<a
 			href="http://joinup.ec.europa.eu/asset/adms/home"
-			class="external text"
 			title="http://joinup.ec.europa.eu/asset/adms/home" rel="nofollow">ADMS</a>)
 		provides the data model to describe semantic assets repositories
 		contents, but this leaves many open challenges when building a
 		federation of these repositories to serve the need of assets
 		reuse. These include accessing and querying individual
 		repositories and efficiently retrieving <a
-			href="#UC5:_Determine_if_a_resource_has_changed" title="">
+			href="#uc-has_resource_changed" title="">
 			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
@@ -677,17 +656,16 @@
 		challenge of efficient access to the data not fully addressed.</p>
 	<p>
 		Related: <a href="http://spec.datacatalogs.org/"
-			class="external text" title="http://spec.datacatalogs.org/"
+			title="http://spec.datacatalogs.org/"
 			rel="nofollow">Data Catalog Schema and Protocol</a>
 	</p>
 	</section>
 	
 	<section>
-	<h2 id="story-donstrained_devices">Constrained Devices and Networks</h2>
+	<h2 id="story-constrained_devices">Constrained Devices and Networks</h2>
 	<p>
 		Information coming from resource constrained devices in the Web of
 		Things (<a href="http://en.wikipedia.org/wiki/Web_of_Things"
-			class="external text"
 			title="http://en.wikipedia.org/wiki/Web_of_Things" rel="nofollow">WoT</a>)
 		has been identified as a major driver in many domains, from smart
 		cities to environmental monitoring to real-time tracking. The
@@ -699,12 +677,10 @@
 		constrained devices, abstracting away heterogeneities, will become
 		possible. Up-coming IoT/WoT standards such as <a
 			href="http://datatracker.ietf.org/wg/6lowpan/"
-			class="external text"
 			title="http://datatracker.ietf.org/wg/6lowpan/" rel="nofollow">6LowPAN</a>
 		- IPv6 for resource constrained devices - and the Constrained
 		Application Protocol (<a
 			href="http://tools.ietf.org/html/draft-ietf-core-coap"
-			class="external text"
 			title="http://tools.ietf.org/html/draft-ietf-core-coap"
 			rel="nofollow">CoAP</a>), which provides a downscaled version of
 		HTTP on top of UDP for the use on constrained devices, are already
@@ -716,7 +692,6 @@
 		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"
-			class="external text"
 			title="http://tools.ietf.org/html/draft-castellani-core-http-mapping"
 			rel="nofollow">HTTP-CoAP Mapping</a> would enable constrained
 		devices to directly participate in a Linked Data-based
@@ -735,7 +710,7 @@
 		through local trusted sharing, analysis, dissemination (including
 		publishing of experimental data "beyond the PDF"), and re-use.</p>
 	<ul>
-		<li><a href="#UC6:_Aggregate_resources" title="">Aggregations</a>,
+		<li><a href="#uc-aggregate_resources" title="">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.
@@ -763,7 +738,7 @@
 	</ul>
 	<p>
 		seeAlso: <a href="http://www.wf4ever-project.org/"
-			class="external text" title="http://www.wf4ever-project.org/"
+			title="http://www.wf4ever-project.org/"
 			rel="nofollow">Wf4Ever</a>
 	</p>
 	</section>
@@ -859,7 +834,7 @@
 	<ul>
 		<li>Provide "access guidance for ... resources" (affordances)
 			(from user-story, <a
-			href="#Maintaining_Social_Contact_Information" title="">Maintaining
+			href="#story-social" title="Social Contacts">Maintaining
 				Social Contact Information</a>).
 		</li>
 	</ul>
@@ -869,29 +844,27 @@
 			container</h3>
 	<p>
 		Create a new container resource within the LDP server. In <a
-			href="#Services_Supporting_the_Process_of_Science" title="">Services
+			href="#story-process_of_science" title="">Services
 			supporting the process of science</a>, <a
-			href="http://wf4ever.github.com/ro-primer/" class="external text"
+			href="http://wf4ever.github.com/ro-primer/" 
 			title="http://wf4ever.github.com/ro-primer/" rel="nofollow">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"
-			class="external text"
 			title="http://ceur-ws.org/Vol-903/paper-01.pdf" rel="nofollow">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
 		throughout the lifecycle of the project.
 	</p>
-	<pre>
+	<pre class='example'>
 @prefix ro:     http://purl.org/wf4ever/ro#
 @prefix dct:    http://purl.org/dc/terms/
 @prefix ore:    http://www.openarchives.org/ore/
 
 &lt;&gt; a ro:ResearchObject, ore:Aggregation ;
     dct:created &quot;2012-12-01&quot;^^xsd:dateTime .
- 
 </pre>
 	</section>
 	
@@ -900,14 +873,14 @@
 			nested container</h3>
 	<p>
 		The motivation for nested containers comes from the <a
-			href="#System_and_Software_Development_Tool_Integration" title="">
+			href="#story-oslc" title="Story Tool Integration">
 			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
 		oslc_cm:attachment. The 'top-level-container' contains issues, and
 		each issue resource has its own container of attachment resources.
 	</p>
-	<pre>
+	<pre class='example'>
 @prefix dcterms: &lt;http://purl.org/dc/terms/&gt;.
 @prefix rdfs: &lt;http://www.w3.org/2000/01/rdf-schema#&gt;.
 @prefix oslc_cm: &lt;http://open-services.net/ns/cm#&gt;.
@@ -926,7 +899,6 @@
 
 :attachments a oslc_cm:AttachmentList;
       oslc_cm:attachment :attachment324, :attachment251.
- 
 </pre>
 	</section>
 	</section>
@@ -954,28 +926,26 @@
 		contained resources. While the LDP has ultimate control over
 		resource naming, some applications may require more control over
 		naming, perhaps to provide a more human-readable URI. An LDP
-		server could support something like the <a
-			href="http://tools.ietf.org/html/rfc5023" class="external text"
-			title="http://tools.ietf.org/html/rfc5023" rel="nofollow">Atom
-			Publishing Protocol</a> slug header to convey a user defined naming
-		'hint'.
+		server could support something like the Atom
+			Publishing Protocol slug header to convey a user defined naming
+		'hint' [[RFC5023]].
 	</p>
 	<ul>
 		<li>Non-duplication of resources: "Eliminate multiple
 			copies", representing resources in a single place (from <a
-			href="#Maintaining_Social_Contact_Information" title="">#Maintaining
+			href="#story-social" title="Story Social Informatinon">#Maintaining
 				Social Contact Information</a>).
 		</li>
 		<li>Distribution of resources: Linked aata "may be stored on
 			separate servers" (from <a
-			href="#Maintaining_Social_Contact_Information" title="">#Maintaining
+			href="#story-social" title="Story Social Informatinon">#Maintaining
 				Social Contact Information</a>).
 		</li>
 		<li>Consistent, global naming: Resources should be "linked to
 			consistently, ... instead of maintaining various identifiers in
 			different formats" (from <a
-			href="#Keeping_Track_of_Personal_and_Business_Relationships"
-			title="">#Keeping Track of Personal and Business
+			href="#story-tracking_relationships"
+			title="Story Tracking Relationships">#Keeping Track of Personal and Business
 				Relationships</a>).
 		</li>
 	</ul>
@@ -984,8 +954,8 @@
 	<h3 id="scen-create_resource">Primary scenario: create resource</h3>
 	<p>
 		Resources begin life by being created within a container. From
-		user-story, <a href="#Maintaining_Social_Contact_Information"
-			title="">Maintaining Social Contact Information</a>, It should be
+		user-story, <a href="#story-social" title="Story Social Informatinon">
+		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
 		to the application context. The new resource is created in a
@@ -1001,15 +971,13 @@
 		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
-		to describe contact information using the <a
-			href="http://www.foaf-project.org" class="external text"
-			title="http://www.foaf-project.org" rel="nofollow">FOAF</a>
-		vocabulary. A contact is represented here by a
+		to describe contact information using the FOAF
+		vocabulary [[FOAF]]. 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.
 	</p>
-	<pre>
+	<pre class='example'>
 @prefix foaf:  &lt;http://xmlns.com/foaf/0.1/&gt; .
 
 &lt;&gt; a foaf:PersonalProfileDocument;
@@ -1025,7 +993,6 @@
 		foaf:mbox &lt;mailto:[email protected]&gt;;
 		foaf:workplaceHomepage &lt;http://www.w3.org/&gt;.
 	]
- 
 </pre>
 	</section>
 	
@@ -1040,9 +1007,7 @@
 		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 "<a href="http://www.w3.org/TR/cooluris/|"
-			class="external text" title="http://www.w3.org/TR/cooluris/|"
-			rel="nofollow">Cool URIs don't change</a>", which implies that
+		practice states that "Cool URIs don't change" [[COOLURIS]], which implies that
 		deleted URIs shouldn't be recycled.
 	</p>
 	</section>
@@ -1059,11 +1024,7 @@
 		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 LDP naming policy. While assigning a
-		new URI to a resource is discouraged <a
-			href="http://www.w3.org/DesignIssues/Architecture.html#HTTP"
-			class="external autonumber"
-			title="http://www.w3.org/DesignIssues/Architecture.html#HTTP"
-			rel="nofollow">[5]</a>, it is possible to indicate that a
+		new URI to a resource is discouraged [[WEBARCH]], it is possible to indicate that a
 		resource has moved with an appropriate HTTP response.
 	</p>
 	</section>
@@ -1084,11 +1045,11 @@
 	<ul>
 		<li>Use standard vocabularies as appropriate to enable a
 			"common understanding of the resource" (from <a
-			href="#Maintaining_Social_Contact_Information" title="">Maintaining
+			href="#story-social" title="">Maintaining
 				Social Contact Information</a>).
 		</li>
 		<li>A "scalable linking model is key" (from <a
-			href="#Municipality_Operational_Monitoring" title="">#Municipality
+			href="#story-meter_monitoring" title="">#Municipality
 				Operational Monitoring</a>).
 		</li>
 	</ul>
@@ -1097,17 +1058,16 @@
 	<h3 id="scen-fetch">Primary scenario</h3>
 	<p>
 		The user-story <a
-			href="#Project_Membership_Information_:_Information_Evolution"
+			href="#story-project_data"
 			title=""> Project Membership Information</a> discusses the
 		representation of information about people and projects. It calls
 		for "Resource descriptions for each person and project" 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" class="external text"
+			href="http://www.epimorphics.com"
 			title="http://www.epimorphics.com" rel="nofollow">Epimorphics</a>
 		<a href="http://www.epimorphics.com/public/vocabulary/org.html"
-			class="external text"
 			title="http://www.epimorphics.com/public/vocabulary/org.html"
 			rel="nofollow">organizational ontology</a>.
 	</p>
@@ -1117,7 +1077,7 @@
 		include descriptions of related resources, such as
 		http://www.w3.org/, that that fall under a different authority and
 		therefore can't be served from the LDP at this location.</p>
-	<pre>
+	<pre class='example'>
 @prefix org: &lt;http://www.w3.org/ns/org#&gt; .
 @prefix owltime: &lt;http://www.w3.org/2006/time&gt; .
 @prefix xsd: &lt;http://www.w3.org/2001/XMLSchema#&gt; .
@@ -1133,7 +1093,6 @@
 &lt;http://www.w3.org/&gt; a org:FormalOrganization ;
 	skos:prefLabel &quot;The World Wide Web Consortium&quot;@en ;
 	skos:altLabel &quot;W3C&quot; .
- 
 </pre>
 					<pre>
 @prefix org: &lt;http://www.w3.org/ns/org#&gt; .
@@ -1158,7 +1117,7 @@
 		requires that the fragment part be stripped off before requesting
 		the URI from the server. The result is a resolvable URI for the
 		profile.</p>
-	<pre>
+	<pre class='example'>
 @base &lt;http://www.w3.org/People/Berners-Lee/card&gt;
 @prefix foaf: &lt;http://xmlns.com/foaf/0.1/&gt;.
 @prefix dc: &lt;http://purl.org/dc/elements/1.1/&gt;.
@@ -1167,7 +1126,6 @@
 	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>
 	</section>
 	</section>
@@ -1183,7 +1141,7 @@
 	<ul>
 		<li>Unrestricted vocabulary: It should be possible be "able
 			to add ... application-specific data" to resources (from <a
-			href="#Maintaining_Social_Contact_Information" title="">#Maintaining
+			href="#story-social" title="">#Maintaining
 				Social Contact Information</a>).
 		</li>
 	</ul>
@@ -1192,10 +1150,9 @@
 	<h3 id="scen-update_enrichment">Primary scenario: enrichment</h3>
 	<p>
 		This relates to user-story <a
-			href="#Metadata_Enrichment_in_Broadcasting" title="">
+			href="#story-media" title="">
 			Metadata Enrichment in Broadcasting</a> and is based on the <a
 			href="http://www.bbc.co.uk/ontologies/sport/"
-			class="external text"
 			title="http://www.bbc.co.uk/ontologies/sport/" rel="nofollow">BBC
 			Sports Ontology</a>. The <i>resource-centric</i> view of linked-data
 		provides a natural granularity for substituting, or overwriting a
@@ -1206,7 +1163,7 @@
 		of the LDP would allow a user to replace the information about the
 		award without disturbing the information about the event.
 	</p>
-	<pre>
+	<pre class='example'>
 @prefix sport: &lt;http://www.bbc.co.uk/ontologies/sport/&gt; .
 @prefix rdfs: &lt;http://www.w3.org/2000/01/rdf-schema#&gt; .
  
@@ -1215,12 +1172,11 @@
     sport:award &lt;#gold_medal&gt; .
 
 &lt;#gold_medal&gt; a sport:Award .
- 
 </pre>
 	<p>We can enrich the description as events unfold, linking to
 		the winner of the gold medal by substituting the above description
 		with the following.</p>
-	<pre>
+	<pre class='example'>
 @prefix sport: &lt;http://www.bbc.co.uk/ontologies/sport/&gt; .
 @prefix rdfs: &lt;http://www.w3.org/2000/01/rdf-schema#&gt; .
 @prefix foaf: &lt;http://xmlns.com/foaf/0.1/&gt; .
@@ -1233,7 +1189,6 @@
         a foaf:Agent ;
         foaf:name &quot;Chris Hoy&quot; .
     ] .
- 
 </pre>
 	</section>
 	
@@ -1241,37 +1196,31 @@
 	<h3 id="scen-alt_selective_update">Alternative scenario: selective
 			update of a resource</h3>
 	<p>
-		This relates to user-story <a href="#Data_Catalogs" title="">Data
+		This relates to user-story <a href="#story-data_catalogs" title="">Data
 			Catalogs</a>, based on the <a href="http://vocab.deri.ie/dcat"
-			class="external text" title="http://vocab.deri.ie/dcat"
+			title="http://vocab.deri.ie/dcat"
 			rel="nofollow">Data Catalog Vocabulary</a>. A catalogue is
 		described by the following RDF model.
 	</p>
-	<pre>
+	<pre class='example'>
 @prefix dcat: &lt;http://www.w3.org/ns/dcat#&gt;	.
 @prefix dcterms: &lt;http://purl.org/dc/terms/&gt; .
    
  :catalog a dcat:Catalog ;
     dcat:dataset :dataset/001;
     dcterms:issued &quot;2012-12-11&quot;^^xsd:date.
- 
 </pre>
 	<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 Talis <i>changeset</i> <a
+		just the new dataset links. A <a
 			href="http://docs.api.talis.com/getting-started/changesets"
-			class="external autonumber"
 			title="http://docs.api.talis.com/getting-started/changesets"
-			rel="nofollow">[6]</a><a
-			href="http://www.w3.org/2009/12/rdf-ws/papers/ws07"
-			class="external autonumber"
-			title="http://www.w3.org/2009/12/rdf-ws/papers/ws07"
-			rel="nofollow">[7]</a> could be used to add a new dc:title to the
+			rel="nofollow">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>
-	<pre>
+	<pre class='example'>
 @prefix : &lt;http://example.com/&gt;.
 @prefix dcterms: &lt;http://purl.org/dc/terms/&gt; .
 @prefix cs: &lt;http://purl.org/vocab/changeset/schema#&gt; .
@@ -1288,7 +1237,6 @@
     rdf:predicate dcat:dataset ;
     rdf:object :dataset/002 .
   ] .
- 
 </pre>
 	</section>
 	</section>
@@ -1311,15 +1259,10 @@
 	<h3 id="scen-primary_has_changed">Primary scenario</h3>
 	<p>
 		Based on the user-story, <a
-			href="#Constrained_Devices_and_Networks" title="">
+			href="#story-constrained_devices" title="">
 			Constrained Devices and Networks</a>, an LDP could be configured to
-		act as a proxy for a <a
-			href="http://tools.ietf.org/html/draft-ietf-core-coap"
-			class="external text"
-			title="http://tools.ietf.org/html/draft-ietf-core-coap"
-			rel="nofollow">CoAP</a> based <a
+		act as a proxy for a CoAP [[COAP]] based <a
 			href="http://en.wikipedia.org/wiki/Web_of_Things"
-			class="external text"
 			title="http://en.wikipedia.org/wiki/Web_of_Things" rel="nofollow">Web
 			of Things</a>. As an observer of CoAP resources, the LDP registers
 		its interest so that it will be notified whenever the sensor
@@ -1331,11 +1274,10 @@
 		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/"
-			class="external text"
 			title="http://www.w3.org/2005/Incubator/ssn/" rel="nofollow">Semantic
 			Sensor Network</a> ontology.
 	</p>
-	<pre>
+	<pre class='example'>
 @prefix : &lt;http://example.com/energy-management/&gt;.
 
 &lt;&gt; a :MainsFrequencySensor;
@@ -1344,7 +1286,6 @@
 	a :FrequencyMeasurementCapability;
 	ssn:hasMeasurementProperty &lt;#property_1&gt; .
   ] .
- 
 </pre>
 	<p>
 		The value of the sensor changes in real-time as measurements are
@@ -1354,19 +1295,18 @@
 		are represented disjointly (separate RDF representations) they may
 		change independently.
 	</p>
-	<pre>
+	<pre class='example'>
 @prefix : &lt;http://example.com/energy-management/&gt;.
 
 &lt;http://example.com/energy-management#property_1&gt; :hasMeasurementPropertyValue &lt;&gt; .
 &lt;&gt; a :FrequencyValue;
 	:hasQuantityValue &quot;50&quot;^^xsd:float.
- 
 </pre>
 	</section>
 	</section>
 	
 	<section>
-	<h2 id="uc-aggregate_resources">>Use Case: Aggregate resources</h2>
+	<h2 id="uc-aggregate_resources">Use Case: Aggregate resources</h2>
 	<p>
 		There is a requirement to be able to manage <i>collections</i> of
 		resources. The concept of a collection overlaps with, but is
@@ -1382,13 +1322,13 @@
 	<ul>
 		<li>Resource descriptions are a "mix of simple data and
 			collections" (from <a
-			href="#Keeping_Track_of_Personal_and_Business_Relationships"
+			href="#story-tracking_relationships"
 			title="">#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="#Constrained_Devices_and_Networks" title="">#Constrained
+			(from <a href="#story-constrained_devices" title="">Constrained
 				Devices and Networks</a>).
 		</li>
 	</ul>
@@ -1397,14 +1337,9 @@
 	<h3 id="scen-add_a_resource_to_a_collection">Primary scenario: add a resource
 			to a collection</h3>
 	<p>
-		This example is from <a href="#Library_Linked_Data" title="">Library
-			Linked Data</a> and <a
-			href="http://www.w3.org/2005/Incubator/lld/wiki/UseCaseReport"
-			class="external text"
-			title="http://www.w3.org/2005/Incubator/lld/wiki/UseCaseReport"
-			rel="nofollow">LLD-UC</a>, specifically <a
+		This example is from <a href="#story-lld" title="">Library
+			Linked Data</a> and >LLD-UC [[LLC-UC]], specifically <a
 			href="http://www.w3.org/2005/Incubator/lld/wiki/Use_Case_Subject_Search"
-			class="external text"
 			title="http://www.w3.org/2005/Incubator/lld/wiki/Use_Case_Subject_Search"
 			rel="nofollow">Subject Search</a>.
 	</p>
@@ -1417,14 +1352,13 @@
 		"outer space exploration", is not necessarily owned by a
 		container. The following RDF would be added to the (item-level)
 		description of the collection.</p>
-	<pre>
+	<pre class='example'>
 @prefix scheme : &lt;http://example.com/concept-scheme/&gt;.
 @prefix concept : &lt;http://example.com/concept/&gt;.
 
 scheme:subject-heading a skos:ConceptScheme.
 
 concept:Outer+space+Exploration skos:inScheme scheme:subject-heading.
- 
 </pre>
 	</section>
 	
@@ -1441,7 +1375,7 @@
 	</p>
 	<p>
 		As a machine-readable collection of medical terms, the <a
-			href="http://www.ihtsdo.org|" class="external text"
+			href="http://www.ihtsdo.org|"
 			title="http://www.ihtsdo.org|" rel="nofollow">SNOMED</a> ontology
 		is of key importance in <a href="#Healthcare" title="">
 			healthcare</a>. SNOMED CT allows concepts with more than one parent
@@ -1449,7 +1383,7 @@
 		concept may fall under two different parent concepts. The example
 		uses skos:narrowerTransitive to elide intervening concepts.
 	</p>
-	<pre>
+	<pre class='example'>
 @prefix : &lt;http://example.com/snomed/&gt;.
 
 :_119376003 a skos:Concept ;
@@ -1462,7 +1396,6 @@
 
 :_128166000 a skos:Concept;
 	rdfs:label &quot;Tissue specimen from heart&quot;.
- 
 </pre>
 	</section>
 	</section>
@@ -1482,7 +1415,6 @@
 		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/|"
-			class="external text"
 			title="http://dublincore.org/groups/collections/collection-application-profile/|"
 			rel="nofollow">Collection-Level</a> description. A collection can
 		refer to any aggregation of physical or digital items. This
@@ -1491,7 +1423,7 @@
 		without necessarily having to download a full listing of the items
 		within the collection.
 	</p>
-	<pre>
+	<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;.
@@ -1504,7 +1436,6 @@
 	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>
 	</section>
 	
@@ -1513,7 +1444,7 @@
 			item-level description of a collection</h3>
 	<p>
 		This use-case scenario, also based on <a
-			href="#Library_Linked_Data" title=""> Library Linked Data</a>,
+			href="#story-lld" title=""> 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
@@ -1525,13 +1456,12 @@
 		captured using the Functional Requirements for Bibliographic
 		Records (<a
 			href="http://www.ifla.org/publications/functional-requirements-for-bibliographic-records"
-			class="external text"
 			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>.
 	</p>
-	<pre>
+	<pre class='example'>
 @prefix frbr: &lt;http://purl.org/vocab/frbr/core#&gt;.
 
 &lt;&gt; rdfs:member &lt;#ebooks97&gt;, &lt;#ebooks21279&gt;.
@@ -1545,7 +1475,6 @@
 	dc:title &quot;2 B R 0 2 B&quot; ;
 	frbr:creator &lt;#Vonnegut_Kurt&gt;;
 	frbr:manifestation &lt;ebook21279&gt;.
- 
 </pre>
 	<p>Collections are potentially very large, so some means may be
 		required to limit the size of RDF representation returned by the
@@ -1576,14 +1505,11 @@
 		the usual ways.
 	</p>
 	<p>
-		This example uses the <a
-			href="http://www.w3.org/TR/mediaont-10/#ont-ttl"
-			class="external text"
-			title="http://www.w3.org/TR/mediaont-10/#ont-ttl" rel="nofollow">Ontology
-			for Media Resources</a> to describe a media resource added to a
-		collection.
+		This example uses the Ontology
+			for Media Resources to describe a media resource added to a
+		collection [[MEDIAONT]].
 	</p>
-	<pre>
+	<pre class='example'>
 @prefix ma: &lt;http://www.w3.org/ns/ma-ont#&gt; .
 
 &lt;dataset&gt; a ma:Collection ;
@@ -1591,12 +1517,11 @@
 
 &lt;dataset/image1.jpg&gt; a ma:MediaResource ;
 	ma:hasFormat &quot;image/jpeg&quot; .
- 
 </pre>
 	</section>
 	
 	<section>
-	<h3 id="Alternative_scenario:_media-resource_attachments">Alternative scenario:
+	<h3 id="scen-media_attachments">Alternative scenario:
 			media-resource attachments</h3>
 	<p>
 		A resource may have multiple <i>renditions</i>; the idea that you
@@ -1623,64 +1548,64 @@
 <section>
 	<h2 id="reqs-functional">Functional Requirements</h2>
 	<ol>
-		<li>Create Containers, from <a href="#UC1:_Manage_containers"
-			title="">#UC1: Manage containers</a>
+		<li>Create Containers, from <a href="#uc-manage_containers"
+			title="">Use Case: Manage containers</a>
 		</li>
 		<li>Creation of nested containers, from <a
-			href="#UC1:_Manage_containers" title="">#UC1: Manage
+			href="#uc-manage_containers" title="">Use Case: Manage
 				containers</a>
 		</li>
 		<li>Creation of resources (within a container), from <a
-			href="#UC2:_Manage_resources" title="">#UC2: Manage resources</a>
+			href="#uc-manage_resources" title="">Use Case: Manage resources</a>
 		</li>
 		<li>Deletion of resources, from <a
-			href="#UC2:_Manage_resources" title="">#UC2: Manage resources</a>
+			href="#uc-amnage_resources" title="">Use Case: Manage resources</a>
 		</li>
 		<li>Moving contained resources, from <a
-			href="#UC2:_Manage_resources" title="">#UC2: Manage resources</a>
+			href="#uc-manage_resources" title="">Use Case: Manage resources</a>
 		</li>
 		<li>Retrieve resource description, from <a
-			href="#UC3:_Retrieve_resource_description" title="">#UC3:
+			href="#uc-retrieve_resource_description" title="">Use Case:
 				Retrieve resource description</a>
 		</li>
 		<li>Retrieve description of a non-document resource, from <a
-			href="#UC3:_Retrieve_resource_description" title="">#UC3:
+			href="#uc-retrieve_resource_description" title="">Use Case:
 				Retrieve resource description</a>
 		</li>
 		<li>Enrichment (substituting update of existing resource),
-			from <a href="#UC4:_Update_existing_resource" title="">#UC4:
+			from <a href="#uc-update_existing" title="">Use Case:
 				Update existing resource</a>
 		</li>
 		<li>Selective update of a resource, from <a
-			href="#UC4:_Update_existing_resource" title="">#UC4: Update
+			href="#uc-update_existing" title="">Use Case: Update
 				existing resource</a>
 		</li>
 		<li>Determine if a resource has changed, from <a
-			href="#UC5:_Determine_if_a_resource_has_changed" title="">#UC5:
+			href="#uc-has_resource_changed" title="">Use Case:
 				Determine if a resource has changed</a>
 		</li>
 		<li>Add a resource to a collection, from <a
-			href="#UC6:_Aggregate_resources" title="">#UC6: Aggregate
+			href="#uc-aggregate_resources" title="">Use Case: Aggregate
 				resources</a>
 		</li>
 		<li>Add a resource to multiple collections, from <a
-			href="#UC6:_Aggregate_resources" title="">#UC6: Aggregate
+			href="#uc-aggregate_resources" title="">Use Case: Aggregate
 				resources</a>
 		</li>
 		<li>Retrieve collection-level description, from <a
-			href="#UC7:_Filter_resource_description" title="">#UC7:
+			href="#uc-filter_resource_description" title="">Use Case:
 				Filter resource description</a>
 		</li>
 		<li>Retrieve item-level description of a collection, from <a
-			href="#UC7:_Filter_resource_description" title="">#UC7:
+			href="#uc-filter_resource_description" title="">Use Case:
 				Filter resource description</a>
 		</li>
 		<li>Access media resources, from <a
-			href="#UC8:_Manage_media_resources" title="">#UC8: Manage
+			href="#uc-manage_media_resources" title="">Use Case: Manage
 				media resources</a>
 		</li>
 		<li>Media-resource attachments, from <a
-			href="#UC8:_Manage_media_resources" title="">#UC8: Manage
+			href="#uc-manage_media_resources" title="">Use Case: Manage
 				media resources</a>
 		</li>
 	</ol>
@@ -1690,36 +1615,36 @@
 	<h2 id="reqs-non-functional">Non-Functional Requirements</h2>
 	<ol>
 		<li>Provide access guidance to resources, from <a
-			href="#UC1:_Manage_containers" title="">#UC1: Manage
+			href="#uc-manage_containers" title="">Use Case: Manage
 				containers</a>
 		</li>
 		<li>Non-duplication of resources, from <a
-			href="#UC2:_Manage_resources" title="">#UC2: Manage resources</a>
+			href="#uc-manage_resources" title="">Use Case: Manage resources</a>
 		</li>
 		<li>Distribution of resources, from <a
-			href="#UC2:_Manage_resources" title="">#UC2: Manage resources</a>
+			href="#uc-manage_resources" title="">Use Case: Manage resources</a>
 		</li>
 		<li>Consistent, global naming, from <a
-			href="#UC2:_Manage_resources" title="">#UC2: Manage resources</a>
+			href="#uc-manage_resources" title="">Use Case: Manage resources</a>
 		</li>
 		<li>Use standard vocabularies as appropriate, from <a
-			href="#UC3:_Retrieve_resource_description" title="">#UC3:
+			href="#uc-retrieve_resource_description" title="">Use Case:
 				Retrieve resource description</a>
 		</li>
 		<li>Scalable linking model, from <a
-			href="#UC3:_Retrieve_resource_description" title="">#UC3:
+			href="#uc-retrieve_resource_description" title="">Use Case:
 				Retrieve resource description</a>
 		</li>
 		<li>Unrestricted vocabulary, from <a
-			href="#UC4:_Update_existing_resource" title="">#UC4: Update
+			href="#uc-update_existing" title="">Use Case: Update
 				existing resource</a>
 		</li>
 		<li>Resource descriptions are a "mix of simple data and
-			collections", from <a href="#UC6:_Aggregate_resources" title="">#UC6:
+			collections", from <a href="#uc-aggregate_resources" title="">Use Case:
 				Aggregate resources</a>
 		</li>
 		<li>Relative URIs enabling sharing of collections, from <a
-			href="#UC6:_Aggregate_resources" title="">#UC6: Aggregate
+			href="#uc-aggregate_resources" title="">Use Case: Aggregate
 				resources</a>
 		</li>
 	</ol>
@@ -1738,6 +1663,7 @@
 <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>
+	<li>2012-12-16 - Fixed cross section links and initial pass at biblio refs (SS)</li>
 </ul></section>
     
   </body>