CLV release 2.1.0

releases/2.1.0/index.html

@@ -134,9 +134,9 @@
     var respecConfig = {
       postProcess: [quickreference],
       edDraftURI: "https://semiceu.github.io/Core-Location-Vocabulary/releases/2.1.0",
-      latestVersion: "https://semiceu.github.io/Core-Location-Vocabulary/releases/2.0.2",
+      latestVersion: "https://semiceu.github.io/Core-Location-Vocabulary/releases/2.1.0",
       specStatus: "LD",
-      publishDate: "2024-01-31",
+      publishDate: "2024-05-06",
       editors: myeditors,
       authors: myauthors,
       github: "SEMICeu/Core-Location-Vocabulary",
@@ -268,7 +268,7 @@ <h2>
 <section id="specstatus">
     <h2>Status</h2>
         <p>
-            This Core Vocabulary has the status SEMIC Candidate Recommendation published at 2024-01-31.
+            This Core Vocabulary has the status SEMIC Recommendation published at 2024-05-06.
         </p>
         <p>
             Information about the process and the decisions involved in the creation of this specification are consultable at the <a href="https://github.com/SEMICeu/Core-Location-Vocabulary/blob/master/releases/2.1.0/Changelog.md">Changelog</a>.
@@ -416,7 +416,7 @@ <h3 id="Address">
                         Usage Note
                     </dt>
                     <dd>
-                        An "address representation" as conceptually defined by the <a href="https://inspire-regadmin.jrc.ec.europa.eu/dataspecification/ScopeObjectDetail.action?objectDetailId=9353">INSPIRE Address Representation data type</a>: "Representation of an address spatial object for use in external application schemas that need to include the basic, address information in a readable way.".
+                        An "address representation" as conceptually defined by the <a href="https://knowledge-base.inspire.ec.europa.eu/publications/inspire-data-specification-addresses-technical-guidelines_en">INSPIRE Address Representation data type</a>: "Representation of an address spatial object for use in external application schemas that need to include the basic, address information in a readable way.".
 <br/><br/>
 The representation of Addresses varies widely from one country's postal system to another. Even within countries, there are almost always examples of Addresses that do not conform to the stated national standard. However, <a href="https://www.iso.org/standard/61710.html">ISO 19160-1</a> provides a method through which different Addresses can be converted from one conceptual model to another.
 <br/><br/>
@@ -2555,7 +2555,7 @@ <h3>Validation</h3>
 The shapes can be found <a href="./shacl/core-location-ap-SHACL.ttl">here</a>.
 
 <h3>RDF representation</h3>
-The RDF representation of the Core Location Vocabulary is available <a href="./voc/core-location.ttl">here</a>.
+The RDF representation of the Core Location Vocabulary is available <a href="./voc/core-location-ap.ttl">here</a>.
 
 <h3>UML representation</h3>
 The UML representation from which the Core Location Vocabulary has been build is available <a href="./uml">here</a>.