--- a/ldp-ucr.html Tue Jan 29 13:18:50 2013 -0500
+++ b/ldp-ucr.html Tue Jan 29 13:45:48 2013 -0500
@@ -432,7 +432,7 @@
</li>
</ul>
<ul>
- <li>Browsing: "<a href="#uc-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>
@@ -515,7 +515,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="#uc-pdate_existing" title="">
+ in metadata <a href="#uc-update_existing" title="">
enrichment</a>:
</p>
<ul>
@@ -1376,9 +1376,9 @@
</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="">
+ 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
that don't fall into a lattice. In the example below, the same
concept may fall under two different parent concepts. The example
@@ -1413,10 +1413,10 @@
<h3 id="scen-retrieve_collection-level_description">Primary scenario: retrieve
collection-level description</h3>
<p>
- This scenario, based on <a href="#Library_Linked_Data" title="">
+ 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/|"
+ 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
refer to any aggregation of physical or digital items. This
scenario covers the case whereby a client can request a
@@ -1494,7 +1494,7 @@
resources</h3>
<p>
From the User Story <a
- href="#Sharing_Binary_Resources_and_Metadata" title="">
+ href="#sharing-binary-resources-and-metadata" title="">
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
@@ -1560,7 +1560,7 @@
href="#uc-manage_resources" title="">Use Case: Manage resources</a>
</li>
<li>Deletion of resources, from <a
- href="#uc-amnage_resources" title="">Use Case: Manage resources</a>
+ href="#uc-manage_resources" title="">Use Case: Manage resources</a>
</li>
<li>Moving contained resources, from <a
href="#uc-manage_resources" title="">Use Case: Manage resources</a>