Applying changes from commit 17b67cfcec11212f0cee5b5aa7009d529203968c

SEMICeu · Jan 5, 2024 · bc7b0b3 · bc7b0b3
1 parent 54a1cd9
commit bc7b0b3
Show file tree

Hide file tree

Showing 222 changed files with 15,639 additions and 17,290 deletions.
diff --git a/Core-Business-Vocabulary/releases/2.2.0/context/core-business-ap.jsonld b/Core-Business-Vocabulary/releases/2.2.0/context/core-business-ap.jsonld
@@ -87,8 +87,7 @@
       "@context": {
         "contactPage": {
           "@container": "@set",
-          "@id": "http://data.europa.eu/m8g/contactPage",
-          "@type": "@id"
+          "@id": "http://data.europa.eu/m8g/contactPage"
         },
         "hasEmail": {
           "@container": "@set",
@@ -102,6 +101,7 @@
       "@id": "http://data.europa.eu/m8g/ContactPoint"
     },
     "Date": "http://www.w3.org/2001/XMLSchema#date",
+    "Document": "http://xmlns.com/foaf/0.1/Document",
     "FormalOrganization": "http://www.w3.org/ns/org#FormalOrganization",
     "Identifier": {
       "@context": {
@@ -218,6 +218,7 @@
       },
       "@id": "http://www.w3.org/ns/org#Organization"
     },
-    "Text": "http://www.w3.org/1999/02/22-rdf-syntax-ns#langString"
+    "Text": "http://www.w3.org/1999/02/22-rdf-syntax-ns#langString",
+    "Uri": "http://www.w3.org/2001/XMLSchema#anyURI"
   }
 }
diff --git a/Core-Business-Vocabulary/releases/2.2.0/context/core-business-ap_en.jsonld b/Core-Business-Vocabulary/releases/2.2.0/context/core-business-ap_en.jsonld
@@ -87,8 +87,7 @@
       "@context": {
         "contactPage": {
           "@container": "@set",
-          "@id": "http://data.europa.eu/m8g/contactPage",
-          "@type": "@id"
+          "@id": "http://data.europa.eu/m8g/contactPage"
         },
         "hasEmail": {
           "@container": "@set",
@@ -102,6 +101,7 @@
       "@id": "http://data.europa.eu/m8g/ContactPoint"
     },
     "Date": "http://www.w3.org/2001/XMLSchema#date",
+    "Document": "http://xmlns.com/foaf/0.1/Document",
     "FormalOrganization": "http://www.w3.org/ns/org#FormalOrganization",
     "Identifier": {
       "@context": {
@@ -218,6 +218,7 @@
       },
       "@id": "http://www.w3.org/ns/org#Organization"
     },
-    "Text": "http://www.w3.org/1999/02/22-rdf-syntax-ns#langString"
+    "Text": "http://www.w3.org/1999/02/22-rdf-syntax-ns#langString",
+    "Uri": "http://www.w3.org/2001/XMLSchema#anyURI"
   }
 }
diff --git a/Core-Business-Vocabulary/releases/2.2.0/html/overview.jpg b/Core-Business-Vocabulary/releases/2.2.0/html/overview.jpg
diff --git a/Core-Business-Vocabulary/releases/2.2.0/index.html b/Core-Business-Vocabulary/releases/2.2.0/index.html
@@ -373,7 +373,7 @@ <h2>Overview</h2>
                         <p>
                             And supported by these datatypes:
                             <br />
-                            | <a href="#"></a> | <a href="#Code">Code</a> | <a href="#Literal">Literal</a> | <a href="#Text">Text</a> |
+                            | <a href="#"></a> | <a href="#Code">Code</a> | <a href="#Document">Document</a> | <a href="#Literal">Literal</a> | <a href="#Text">Text</a> | <a href="#URI">URI</a> |
                         </p>
 
     </div>
@@ -2014,13 +2014,6 @@ <h3 id="ContactPoint">
                                 </td>
                                 <td>
 
-
-                                            <a href="#Document"
-                                               data-toggle="tooltip"
-                                               data-content="http://xmlns.com/foaf/0.1/Document"
-                                               data-placement="right">Document</a>
-
-
                                 </td>
                                 <td>
                                     0..*
@@ -2823,6 +2816,22 @@ <h2>
 		</td><td>
                     An idea or notion; a unit of thought.
 		</td></tr>
+		<tr><td>
+                   <a href="https://github.com/SEMICeu/Core-Business-Vocabulary/issues/new?title=Issue%20for%20Document&body=Explain%20your%20issue"}}>
+                     <img src="html/callout.png" loading="lazy" alt="(create issue)" width="50" height="50"/>
+		   </a>
+		</td><td>
+
+                    <div id="Document">
+                        <a href="http://xmlns.com/foaf/0.1/Document"
+                           data-toggle="tooltip"
+                           data-content="http://xmlns.com/foaf/0.1/Document"
+                           data-placement="right">Document</a>
+                    </div>
+
+		</td><td>
+                    A self-contained collection of information in a readable format.
+		</td></tr>
 		<tr><td>
                    <a href="https://github.com/SEMICeu/Core-Business-Vocabulary/issues/new?title=Issue%20for%20Literal&body=Explain%20your%20issue"}}>
                      <img src="html/callout.png" loading="lazy" alt="(create issue)" width="50" height="50"/>
@@ -2855,6 +2864,22 @@ <h2>
 		</td><td>
                     The text data type is a combination of a string and a language identifier.
 		</td></tr>
+		<tr><td>
+                   <a href="https://github.com/SEMICeu/Core-Business-Vocabulary/issues/new?title=Issue%20for%20Uri&body=Explain%20your%20issue"}}>
+                     <img src="html/callout.png" loading="lazy" alt="(create issue)" width="50" height="50"/>
+		   </a>
+		</td><td>
+
+                    <div id="URI">
+                        <a href="http://www.w3.org/2001/XMLSchema#anyURI"
+                           data-toggle="tooltip"
+                           data-content="http://www.w3.org/2001/XMLSchema#anyURI"
+                           data-placement="right">URI</a>
+                    </div>
+
+		</td><td>
+                    anyURI represents an Internationalized Resource Identifier Reference (IRI).  An anyURI value can be absolute or relative, and may have an optional fragment identifier (i.e., it may be an IRI Reference).  This type should be used when the value fulfills the role of an IRI, as defined in [RFC 3987] or its successor(s) in the IETF Standards Track.
+		</td></tr>
             </tbody>
 	</table>
 
@@ -2910,7 +2935,7 @@ <h2>Support for implementation</h2>
 The following section provides support for implementing the Core Business Vocabulary.
 <p/>
 
-<h4>JSON-LD context file</h4>
+<h3>JSON-LD context file</h3>
 
 One common technical question is the format in which the data is being exchanged. 
 For conformance with the Core Business Vocabulary, it is not mandatory that this happens in a RDF serialisation, but the exhanged format SHOULD be unambiguously be transformable into RDF.
@@ -2922,7 +2947,7 @@ <h4>JSON-LD context file</h4>
 The JSON-LD context file downloadable <a href="./context/core-business-ap.jsonld">here</a>.
 <p/>
 
-<h4>Validation</h4>
+<h3>Validation</h3>
 
 To verify if the data is (technically) conformant to the Core Business Vocabulary, the exchanged data can be validated using the provided SHACL shapes. 
 SHACL is a W3C Recommendation to express constraints on a RDF knowledge graph. 
@@ -2937,7 +2962,7 @@ <h4>Validation</h4>
 The shapes can be found <a href="./shacl/core-business-ap-SHACL.ttl">here</a>.
 
 <!--
-<h4>Mapping</h4>
+<h3>Mapping</h3>
 A mapping towards Schema.org can be found <a href="https://github.com/SEMICeu/Semantic-Mappings/tree/main/Core%20Location">here</a>
 <p/>
 -->
@@ -2946,7 +2971,7 @@ <h4>Mapping</h4>
     <section class="informative">
 <h2>Governance</h2>
 
-<h4>Versioning governance</h4>
+<h3>Versioning governance</h3>
 All specifications produced in SEMIC will follow the versioning rule described by the SEMIC Style Guide rule 
 <a href="https://semiceu.github.io/style-guide/1.0.0/gc-publication-conventions.html#sec:pc-r3">PC-R3</a>.
 In case a SEMIC asset is deprecated the asset will remain available through its PURI.
@@ -2958,7 +2983,7 @@ <h4>Versioning governance</h4>
 </ul>
 <p/>
 
-<h4>Governance requirements for re-used assets</h4>
+<h3>Governance requirements for re-used assets</h3>
 In order to adhere to the SEMIC Style Guide rule <a href="https://semiceu.github.io/style-guide/1.0.0/gc-general-conventions.html#sec:gc-r2">GC-R2</a>
  a specification should have quality and governance standards for the assets that are being reused.
 <p/>
@@ -2978,7 +3003,7 @@ <h4>Governance requirements for re-used assets</h4>
 Once considered and validated an asset can be adopted if it is approved by the community.
 <p/>
 
-<h4>Lexicalisation rules</h4>
+<h3>Lexicalisation rules</h3>
 
 In order to adhere to the SEMIC Style Guide rule <a href="https://semiceu.github.io/style-guide/1.0.0/gc-semantic-conventions.html#sec:sc-r3">SC-R3</a> a specification requires formal lexicalisation rules.
 The Style Guide proposes two options either by using RDFS or SKOS lexicalisation.

diff --git a/Core-Business-Vocabulary/releases/2.2.0/index_en.html b/Core-Business-Vocabulary/releases/2.2.0/index_en.html
@@ -373,7 +373,7 @@ <h2>Overview</h2>
                         <p>
                             And supported by these datatypes:
                             <br />
-                            | <a href="#"></a> | <a href="#Code">Code</a> | <a href="#Literal">Literal</a> | <a href="#Text">Text</a> |
+                            | <a href="#"></a> | <a href="#Code">Code</a> | <a href="#Document">Document</a> | <a href="#Literal">Literal</a> | <a href="#Text">Text</a> | <a href="#URI">URI</a> |
                         </p>
 
     </div>
@@ -2014,13 +2014,6 @@ <h3 id="ContactPoint">
                                 </td>
                                 <td>
 
-
-                                            <a href="#Document"
-                                               data-toggle="tooltip"
-                                               data-content="http://xmlns.com/foaf/0.1/Document"
-                                               data-placement="right">Document</a>
-
-
                                 </td>
                                 <td>
                                     0..*
@@ -2823,6 +2816,22 @@ <h2>
 		</td><td>
                     An idea or notion; a unit of thought.
 		</td></tr>
+		<tr><td>
+                   <a href="https://github.com/SEMICeu/Core-Business-Vocabulary/issues/new?title=Issue%20for%20Document&body=Explain%20your%20issue"}}>
+                     <img src="html/callout.png" loading="lazy" alt="(create issue)" width="50" height="50"/>
+		   </a>
+		</td><td>
+
+                    <div id="Document">
+                        <a href="http://xmlns.com/foaf/0.1/Document"
+                           data-toggle="tooltip"
+                           data-content="http://xmlns.com/foaf/0.1/Document"
+                           data-placement="right">Document</a>
+                    </div>
+
+		</td><td>
+                    A self-contained collection of information in a readable format.
+		</td></tr>
 		<tr><td>
                    <a href="https://github.com/SEMICeu/Core-Business-Vocabulary/issues/new?title=Issue%20for%20Literal&body=Explain%20your%20issue"}}>
                      <img src="html/callout.png" loading="lazy" alt="(create issue)" width="50" height="50"/>
@@ -2855,6 +2864,22 @@ <h2>
 		</td><td>
                     The text data type is a combination of a string and a language identifier.
 		</td></tr>
+		<tr><td>
+                   <a href="https://github.com/SEMICeu/Core-Business-Vocabulary/issues/new?title=Issue%20for%20Uri&body=Explain%20your%20issue"}}>
+                     <img src="html/callout.png" loading="lazy" alt="(create issue)" width="50" height="50"/>
+		   </a>
+		</td><td>
+
+                    <div id="URI">
+                        <a href="http://www.w3.org/2001/XMLSchema#anyURI"
+                           data-toggle="tooltip"
+                           data-content="http://www.w3.org/2001/XMLSchema#anyURI"
+                           data-placement="right">URI</a>
+                    </div>
+
+		</td><td>
+                    anyURI represents an Internationalized Resource Identifier Reference (IRI).  An anyURI value can be absolute or relative, and may have an optional fragment identifier (i.e., it may be an IRI Reference).  This type should be used when the value fulfills the role of an IRI, as defined in [RFC 3987] or its successor(s) in the IETF Standards Track.
+		</td></tr>
             </tbody>
 	</table>
 
@@ -2910,7 +2935,7 @@ <h2>Support for implementation</h2>
 The following section provides support for implementing the Core Business Vocabulary.
 <p/>
 
-<h4>JSON-LD context file</h4>
+<h3>JSON-LD context file</h3>
 
 One common technical question is the format in which the data is being exchanged. 
 For conformance with the Core Business Vocabulary, it is not mandatory that this happens in a RDF serialisation, but the exhanged format SHOULD be unambiguously be transformable into RDF.
@@ -2922,7 +2947,7 @@ <h4>JSON-LD context file</h4>
 The JSON-LD context file downloadable <a href="./context/core-business-ap.jsonld">here</a>.
 <p/>
 
-<h4>Validation</h4>
+<h3>Validation</h3>
 
 To verify if the data is (technically) conformant to the Core Business Vocabulary, the exchanged data can be validated using the provided SHACL shapes. 
 SHACL is a W3C Recommendation to express constraints on a RDF knowledge graph. 
@@ -2937,7 +2962,7 @@ <h4>Validation</h4>
 The shapes can be found <a href="./shacl/core-business-ap-SHACL.ttl">here</a>.
 
 <!--
-<h4>Mapping</h4>
+<h3>Mapping</h3>
 A mapping towards Schema.org can be found <a href="https://github.com/SEMICeu/Semantic-Mappings/tree/main/Core%20Location">here</a>
 <p/>
 -->
@@ -2946,7 +2971,7 @@ <h4>Mapping</h4>
     <section class="informative">
 <h2>Governance</h2>
 
-<h4>Versioning governance</h4>
+<h3>Versioning governance</h3>
 All specifications produced in SEMIC will follow the versioning rule described by the SEMIC Style Guide rule 
 <a href="https://semiceu.github.io/style-guide/1.0.0/gc-publication-conventions.html#sec:pc-r3">PC-R3</a>.
 In case a SEMIC asset is deprecated the asset will remain available through its PURI.
@@ -2958,7 +2983,7 @@ <h4>Versioning governance</h4>
 </ul>
 <p/>
 
-<h4>Governance requirements for re-used assets</h4>
+<h3>Governance requirements for re-used assets</h3>
 In order to adhere to the SEMIC Style Guide rule <a href="https://semiceu.github.io/style-guide/1.0.0/gc-general-conventions.html#sec:gc-r2">GC-R2</a>
  a specification should have quality and governance standards for the assets that are being reused.
 <p/>
@@ -2978,7 +3003,7 @@ <h4>Governance requirements for re-used assets</h4>
 Once considered and validated an asset can be adopted if it is approved by the community.
 <p/>
 
-<h4>Lexicalisation rules</h4>
+<h3>Lexicalisation rules</h3>
 
 In order to adhere to the SEMIC Style Guide rule <a href="https://semiceu.github.io/style-guide/1.0.0/gc-semantic-conventions.html#sec:sc-r3">SC-R3</a> a specification requires formal lexicalisation rules.
 The Style Guide proposes two options either by using RDFS or SKOS lexicalisation.

diff --git a/Core-Business-Vocabulary/releases/2.2.0/xsd/core-business-ap.xsd b/Core-Business-Vocabulary/releases/2.2.0/xsd/core-business-ap.xsd
@@ -4,6 +4,7 @@
   <xs:element name="ContactPoint" type="ContactPointType"/>
   <xs:element name="Text" type="TextType"/>
   <xs:element name="Literal" type="LiteralType"/>
+  <xs:element name="Uri" type="UriType"/>
   <xs:element name="Date" type="DateType"/>
   <xs:element name="Code" type="CodeType"/>
   <xs:element name="Identifier" type="IdentifierType"/>
@@ -12,6 +13,7 @@
   <xs:element name="FormalOrganization" type="FormalOrganizationType"/>
   <xs:element name="Organization" type="OrganizationType"/>
   <xs:element name="Agent" type="AgentType"/>
+  <xs:element name="Document" type="DocumentType"/>
   <xs:complexType name="AccountingDocumentType">
     <xs:sequence/>
     <xs:attribute name="AccountingDocumentRef" type="xs:IDREF">
@@ -60,6 +62,14 @@
       </xs:annotation>
     </xs:attribute>
   </xs:complexType>
+  <xs:complexType name="UriType">
+    <xs:sequence/>
+    <xs:attribute name="UriRef" type="xs:IDREF">
+      <xs:annotation>
+        <xs:documentation xml:lang="en">Reference to Uri ID</xs:documentation>
+      </xs:annotation>
+    </xs:attribute>
+  </xs:complexType>
   <xs:complexType name="DateType">
     <xs:sequence/>
     <xs:attribute name="DateRef" type="xs:IDREF">
@@ -347,4 +357,12 @@ The key difference between a locator designator and a locator name is that the l
       </xs:annotation>
     </xs:attribute>
   </xs:complexType>
+  <xs:complexType name="DocumentType">
+    <xs:sequence/>
+    <xs:attribute name="DocumentRef" type="xs:IDREF">
+      <xs:annotation>
+        <xs:documentation xml:lang="en">Reference to Document ID</xs:documentation>
+      </xs:annotation>
+    </xs:attribute>
+  </xs:complexType>
 </xs:schema>
diff --git a/Core-Business-Vocabulary/releases/2.2.0/xsd/core-business-ap_en.xsd b/Core-Business-Vocabulary/releases/2.2.0/xsd/core-business-ap_en.xsd
@@ -4,6 +4,7 @@
   <xs:element name="ContactPoint" type="ContactPointType"/>
   <xs:element name="Text" type="TextType"/>
   <xs:element name="Literal" type="LiteralType"/>
+  <xs:element name="Uri" type="UriType"/>
   <xs:element name="Date" type="DateType"/>
   <xs:element name="Code" type="CodeType"/>
   <xs:element name="Identifier" type="IdentifierType"/>
@@ -12,6 +13,7 @@
   <xs:element name="FormalOrganization" type="FormalOrganizationType"/>
   <xs:element name="Organization" type="OrganizationType"/>
   <xs:element name="Agent" type="AgentType"/>
+  <xs:element name="Document" type="DocumentType"/>
   <xs:complexType name="AccountingDocumentType">
     <xs:sequence/>
     <xs:attribute name="AccountingDocumentRef" type="xs:IDREF">
@@ -60,6 +62,14 @@
       </xs:annotation>
     </xs:attribute>
   </xs:complexType>
+  <xs:complexType name="UriType">
+    <xs:sequence/>
+    <xs:attribute name="UriRef" type="xs:IDREF">
+      <xs:annotation>
+        <xs:documentation xml:lang="en">Reference to Uri ID</xs:documentation>
+      </xs:annotation>
+    </xs:attribute>
+  </xs:complexType>
   <xs:complexType name="DateType">
     <xs:sequence/>
     <xs:attribute name="DateRef" type="xs:IDREF">
@@ -347,4 +357,12 @@ The key difference between a locator designator and a locator name is that the l
       </xs:annotation>
     </xs:attribute>
   </xs:complexType>
+  <xs:complexType name="DocumentType">
+    <xs:sequence/>
+    <xs:attribute name="DocumentRef" type="xs:IDREF">
+      <xs:annotation>
+        <xs:documentation xml:lang="en">Reference to Document ID</xs:documentation>
+      </xs:annotation>
+    </xs:attribute>
+  </xs:complexType>
 </xs:schema>