Internal links updated for link checker

dcat/index.html

@@ -301,7 +301,7 @@ <h3>Describing catalog records metadata</h3>
 </pre>
 </section>
 
-<section id="a-dataset-available-only-behind-some-web-page">
+<section id="example-landing-page">
 <h3>Dataset available only behind some Web page</h3>
 <p>:dataset-002 is available as a CSV file. However :dataset-002 can only be obtained through some Web page
 where the user needs to follow some links, provide some information and check some boxes
@@ -597,7 +597,7 @@ <h4>Property: release date</h4>
     <tr><td class="prop">Range:</td><td><a href="http://www.w3.org/2000/01/rdf-schema#Literal">rdfs:Literal</a>
     encoded using the relevant ISO 8601 Date and Time compliant string [[!DATETIME]] and typed using the appropriate XML Schema datatype [[XMLSCHEMA11-2]]
     </td></tr>
-    <tr><td class="prop">See also:</td><td><a href="#Property:dataset_release_date" title=""> dataset release date</a>, <a href="#Property:record_listing_date" title=""> catalog record listing date</a> and <a href="#Property:distribution_release_date" title=""> distribution release date</a></td></tr>
+    <tr><td class="prop">See also:</td><td><a href="#Property:resource_release_date" title=""> resource release date</a>, <a href="#Property:record_listing_date" title=""> catalog record listing date</a> and <a href="#Property:distribution_release_date" title=""> distribution release date</a></td></tr>
   </tbody>
 </table>
 </section>
@@ -611,7 +611,7 @@ <h4>Property: update/modification date</h4>
     <tr><td class="prop">Range:</td><td><a href="http://www.w3.org/2000/01/rdf-schema#Literal">rdfs:Literal</a>
     encoded using the relevant ISO 8601 Date and Time compliant string [[!DATETIME]] and typed using the appropriate XML Schema datatype [[XMLSCHEMA11-2]]
     </td></tr>
-    <tr><td class="prop">See also:</td><td><a href="#Property:dataset_update_date" title=""> dataset modification date</a>, <a href="#Property:record_update_date" title=""> catalog record modification date</a> and <a href="#Property:distribution_update_date" title=""> distribution modification date</a></td></tr>
+    <tr><td class="prop">See also:</td><td><a href="#Property:resource_update_date" title=""> resource modification date</a>, <a href="#Property:record_update_date" title=""> catalog record modification date</a> and <a href="#Property:distribution_update_date" title=""> distribution modification date</a></td></tr>
   </tbody>
 </table>
 </section>
@@ -809,11 +809,11 @@ <h3>Class: Catalogued Resource</h3>
 
 <p>The following properties are recommended for use on this class:
 	<a href="#Property:resource_conformsto">conformsTo</a>,
-	<a href="#Property:resource_contactPoint">contact point</a>,
+	<a href="#Property:resource_contact_point">contact point</a>,
 	<a href="#Property:resource_description">description</a>,
 	<a href="#Property:resource_identifier">identifier</a>,
 	<a href="#Property:resource_keyword">keyword/tag</a>,
-	<a href="#Property:resource_landingpage">landing page</a>,
+	<a href="#Property:resource_landing_page">landing page</a>,
 	<a href="#Property:resource_language">resource language</a>,
 	<a href="#Property:resource_relation">relation</a>,
 	<a href="#Property:resource_publisher">publisher</a>,
@@ -848,7 +848,7 @@ <h3>Class: Catalogued Resource</h3>
 	<tbody>
 	<tr><td class="prop">Definition:</td><td>Resource published or curated by a single agent.</td></tr>
 	<tr><td class="prop">Usage note:</td><td>The class of all catalogued resources, the superclass of
-		<a href="#Dataset">dcat:Dataset</a>, <a href="#DataService">dcat:DataService</a>, <a href="#Catalog">dcat:Catalog</a> and any other member of a <a href="#Catalog">dcat:Catalog</a>.
+		<a href="#Class:Dataset">dcat:Dataset</a>, <a href="#Class:Data_Service">dcat:DataService</a>, <a href="#Class:Catalog">dcat:Catalog</a> and any other member of a <a href="#Class:Catalog">dcat:Catalog</a>.
 		This class carries properties common to all catalogued resources, including datasets and data services.
 
 		It is strongly recommended to use a more specific sub-class when available.</td></tr>
@@ -857,7 +857,7 @@ <h3>Class: Catalogued Resource</h3>
 </table>
 
 <p class="note">
-	The class <a href="#Resource">dcat:Resource</a> has been added to the DCAT vocabulary in this revision.
+	The class <a href="#Class:Resource">dcat:Resource</a> has been added to the DCAT vocabulary in this revision.
 </p>
 
 <section id="Property:resource_title">
@@ -1090,7 +1090,7 @@ <h4>Property: keyword/tag</h4>
 </table>
 </section>
 
-<section id="Property:resource_contactPoint">
+<section id="Property:resource_contact_point">
 <h4>Property: contact point</h4>
 
 <p class="note">
@@ -1110,7 +1110,7 @@ <h4>Property: contact point</h4>
 </table>
 </section>
 
-<section id="Property:resource_landingpage">
+<section id="Property:resource_landing_page">
 <h4>Property: landing page</h4>
 
 <p class="note">
@@ -1125,7 +1125,7 @@ <h4>Property: landing page</h4>
 		<tr><td class="prop">Range:</td><td><a href="http://xmlns.com/foaf/0.1/Document">foaf:Document</a></td></tr>
 		<tr><td class="prop">Usage note:</td><td>
 			If the distribution(s) are accessible only through a landing page
-			(i.e. direct download URLs are not known), then the landing page link <em title="SHOULD" class="rfc2119">SHOULD</em> be duplicated as dcat:accessURL on a distribution. (see <a href="#example-landing-page">example 4.4</a>)
+			(i.e. direct download URLs are not known), then the landing page link <em title="SHOULD" class="rfc2119">SHOULD</em> be duplicated as dcat:accessURL on a distribution. (see <a href="#example-landing-page"></a>)
 		</td></tr>
 		</tbody>
 	</table>
@@ -1242,7 +1242,7 @@ <h4>Property: primary topic</h4>
 <h3>Class: Data Distribution Service</h3>
 
 <p class="note">
-    The class <a href="#DataDistributionService">dcat:DataDistributionService</a> has been added to the DCAT vocabulary in this revision.
+    The class <a href="#Class:Data_Distribution_Service">dcat:DataDistributionService</a> has been added to the DCAT vocabulary in this revision.
 </p>
 
 <p>In addition to the properties inherited from the super-class <a href="http://www.w3.org/ns/dcat#DataService">dcat:DataService</a>, the following properties are recommended for use on this class:
@@ -1281,7 +1281,7 @@ <h3>Class: Data Service</h3>
 	<a href="#Property:dataservice_endpointdescription">endpointDescription</a>,
 	<a href="#Property:dataservice_endpointurl">endpointURL</a>,
 	<a href="#Property:dataservice_license">license</a>,
-	<a href="#Property:dataservice_accessRights">accessRights</a>
+	<a href="#Property:dataservice_access_rights">accessRights</a>
 </p>
 
 <table class="definition">
@@ -1332,7 +1332,7 @@ <h4>Property: license</h4>
 </table>
 </section>
 
-<section id="Property:dataservice_accessrights">
+<section id="Property:dataservice_access_rights">
 <h4>Property: access rights</h4>
 <table class="definition">
   <thead><tr><th>RDF Property:</th><th><a href="http://purl.org/dc/terms/accessRights">dct:accessRights</a></th></tr></thead>
@@ -1550,7 +1550,7 @@ <h3>Class: Discovery Service</h3>
 </table>
 
 <p class="note">
-    The class <a href="#DiscoveryService">dcat:DiscoveryService</a> has been added to the DCAT vocabulary in this revision.
+    The class <a href="#Class:Discovery_Service">dcat:DiscoveryService</a> has been added to the DCAT vocabulary in this revision.
 </p>
 
 </section> <!-- end class DiscoveryService -->
@@ -1652,7 +1652,7 @@ <h4>Property: release date</h4>
     encoded using the relevant ISO 8601 Date and Time compliant string [[!DATETIME]] and typed using the appropriate XML Schema datatype [[XMLSCHEMA11-2]]
     </td></tr>
     <tr><td class="prop">Usage note:</td><td>This property <em title="SHOULD" class="rfc2119">SHOULD</em> be set using the first known date of issuance.</td></tr>
-    <tr><td class="prop">See also:</td><td><a href="#Property:dataset_release_date" title=""> dataset release date</a></td></tr>
+    <tr><td class="prop">See also:</td><td><a href="#Property:resource_release_date" title=""> resource release date</a></td></tr>
   </tbody>
 </table>
 </section>
@@ -1722,7 +1722,7 @@ <h4>Property: access address</h4>
     <tr><td class="prop">Range:</td><td><a href="http://www.w3.org/2000/01/rdf-schema#Resource">rdfs:Resource</a></td></tr>
     <tr><td class="prop">Usage note:</td><td><a href="#Property:distribution_accessurl">dcat:accessURL</a> <em title="SHOULD" class="rfc2119">SHOULD</em> be used for the address of a service or location that can provide access to this distribution, typically through a web form, query or API call.
 		<br/><a href="#Property:distribution_downloadurl">dcat:downloadURL</a> is preferred for direct links to downloadable resources.
-		<br/>If the distribution(s) are accessible only through a landing page (i.e. direct download URLs are not known), then the landingPage address associated with the dcat:Dataset <em title="SHOULD" class="rfc2119">SHOULD</em> be duplicated as accessURL on a distribution. (see <a href="#example-landing-page">example 4.4</a>)
+		<br/>If the distribution(s) are accessible only through a landing page (i.e. direct download URLs are not known), then the landingPage address associated with the dcat:Dataset <em title="SHOULD" class="rfc2119">SHOULD</em> be duplicated as accessURL on a distribution. (see <a href="#example-landing-page"></a>)
     </td></tr>
     <tr><td class="prop">See also</td><td><a href="#Property:distribution_downloadurl">download address</a>, <a href="#Property:distribution_accessservice">access service</a></td></tr>
   </tbody>
@@ -1849,7 +1849,7 @@ <h3>Class: Concept Scheme</h3>
   <thead><tr><th>RDF Class:</th><th><a href="http://www.w3.org/2004/02/skos/core#ConceptScheme">skos:ConceptScheme</a></th></tr></thead>
   <tbody>
     <tr><td class="prop">Definition:</td><td>A knowledge organization system (KOS) used to represent themes/categories of datasets in the catalog.</td></tr>
-    <tr><td class="prop">See also:</td><td><a href="#Property:catalog_themes">catalog themes</a>, <a href="#Property:dataset_theme">dataset theme</a></td></tr>
+    <tr><td class="prop">See also:</td><td><a href="#Property:catalog_themes">catalog themes</a>, <a href="#Property:resource_theme">dataset theme</a></td></tr>
   </tbody>
 </table>
 </section>
@@ -1862,7 +1862,7 @@ <h3>Class: Concept</h3>
     <tr><td class="prop">Definition:</td><td>A category or a theme used to describe datasets in the catalog.</td></tr>
     <tr><td class="prop">Usage note:</td><td>It is recommended to use either skos:inScheme or skos:topConceptOf on every skos:Concept
     used to classify datasets to link it to the concept scheme it belongs to. This concept scheme is typically associated with the catalog using dcat:themeTaxonomy</td></tr>
-    <tr><td class="prop">See also:</td><td><a href="#Property:catalog_themes">catalog themes</a>, <a href="#Property:dataset_theme">dataset theme</a></td></tr>
+    <tr><td class="prop">See also:</td><td><a href="#Property:catalog_themes">catalog themes</a>, <a href="#Property:resource_theme">dataset theme</a></td></tr>
   </tbody>
 </table>
 </section>
@@ -2359,35 +2359,35 @@ <h3>Changes since the W3C Recommendation of 16 January 2014</h3>
 In DCAT 2014 [[VOCAB-DCAT-20140116]] <a href="#Class:Dataset">dcat:Dataset</a> was a sub-class of <a href="http://purl.org/dc/dcmitype/Dataset">dctype:Dataset</a>, which is a term of the <a href="http://dublincore.org/documents/dcmi-terms/#section-7">DCMI Types vocabulary</a> [[DCTERMS]]. This relationship has been removed in the revised DCAT vocabulary - see <a href="https://github.com/w3c/dxwg/issues/98">Issue #98</a>.
 </li>
 
-<li><a href="#Property:dataset_theme">Property: theme/category</a>:
+<li><a href="#Property:resource_theme">Property: theme/category</a>:
 	In DCAT 2014 [[VOCAB-DCAT-20140116]] the domain of dcat:theme was dcat:Dataset,
   which limited use of this property in other contexts. The domain has been relaxed in this revision -
   see <a href="https://github.com/w3c/dxwg/issues/123">Issue #123</a>.
 </li>
 
-<li><a href="#Property:dataset_type">Property: type/genre</a>:
+<li><a href="#Property:resource_type">Property: type/genre</a>:
 	Added in DCAT revision - see <a href="https://github.com/w3c/dxwg/issues/64">Issue #64</a>, with examples of usage in overview section.
 </li>
 
-<li><a href="#Property:dataset_keyword">Property: keyword/tag</a>:
+<li><a href="#Property:resource_keyword">Property: keyword/tag</a>:
 	In DCAT 2014 [[VOCAB-DCAT-20140116]] the domain of dcat:keyword was dcat:Dataset,
   which limited use of this property in other contexts. The domain has been relaxed in this revision -
   see <a href="https://github.com/w3c/dxwg/issues/121">Issue #121</a>.
 </li>
 
-<li><a href="#Property:dataset_contactPoint">Property: contact point</a>:
+<li><a href="#Property:resource_contact_point">Property: contact point</a>:
 	In DCAT 2014 [[VOCAB-DCAT-20140116]] the domain of dcat:contactPoint was dcat:Dataset,
   which limited use of this property in other contexts. The domain has been relaxed in this revision -
   see <a href="https://github.com/w3c/dxwg/issues/95">Issue #95</a>.
 </li>
 
-<li><a href="#Property:dataset_landingpage">Property: landing page</a>:
+<li><a href="#Property:resource_landing_page">Property: landing page</a>:
 	In DCAT 2014 [[VOCAB-DCAT-20140116]] the domain of dcat:landingPage was dcat:Dataset,
   which limited use of this property in other contexts. The domain has been relaxed in this revision -
   see <a href="https://github.com/w3c/dxwg/issues/122">Issue #122</a>.
 </li>
 
-<li><a href="#Property:vann:usageNote">Property: vann:usageNote</a>:
+<li><a href="http://vocab.org/vann/#usageNote">Property: vann:usageNote</a>:
     DCAT 2014 [[VOCAB-DCAT-20140116]] included documentation captured as text using <a href="http://vocab.org/vann/#usageNote">vann:usageNote</a> elements,
     which is a sub-property of rdfs:seeAlso - an owl:ObjectProperty that cannot have a Literal value.
     This revision of DCAT has fixed these issues and replaced the use of vann:usageNote with <a href="https://www.w3.org/TR/skos-primer/#secdocumentation">skos:scopeNote</a> -