added variables for metadata

OP-TED · Sep 20, 2023 · 6493fa9 · 6493fa9
1 parent 0098d12
commit 6493fa9
Show file tree

Hide file tree

Showing 4 changed files with 26 additions and 18 deletions.
diff --git a/src/owl-core.xsl b/src/owl-core.xsl
@@ -68,10 +68,10 @@
             </xsl:for-each>      
 
             <dct:title xml:lang="en">
-                <xsl:value-of select="$ontologyTitle"/>
+                <xsl:value-of select="$ontologyTitleCore"/>
             </dct:title>
             <dct:description xml:lang="en">
-                <xsl:value-of select="$ontologyDescription"/>
+                <xsl:value-of select="$ontologyDescriptionCore"/>
             </dct:description>
             <dct:publisher>
                 <xsl:value-of select="$publisher"/>

diff --git a/src/owl-restrictions.xsl b/src/owl-restrictions.xsl
@@ -63,13 +63,13 @@
             </xsl:for-each>      
             <owl:imports rdf:resource="{$coreArtefactURI}"/>
             <dct:title xml:lang="en">
-                <xsl:value-of select="$ontologyTitle"/>
+                <xsl:value-of select="$ontologyTitleRestrictions"/>
             </dct:title>
             <dct:publisher>
                 <xsl:value-of select="$publisher"/>
             </dct:publisher>
             <dct:description xml:lang="en">
-                <xsl:value-of select="$ontologyDescription"/>
+                <xsl:value-of select="$ontologyDescriptionRestrictions"/>
             </dct:description>
             <rdfs:comment>This version is automatically generated from <xsl:value-of select="tokenize(base-uri(.), '/')[last()]"/> on 
                 <xsl:value-of select="format-date(current-date(),'[Y0001]-[M01]-[D01]')"/>

diff --git a/src/shacl-shapes.xsl b/src/shacl-shapes.xsl
@@ -71,13 +71,13 @@
             <owl:imports rdf:resource="{$restrictionsArtefactURI}"/>
 
             <dct:title xml:lang="en">
-                <xsl:value-of select="$ontologyTitle"/>
+                <xsl:value-of select="$ontologyTitleShapes"/>
             </dct:title>
             <dct:publisher>
                 <xsl:value-of select="$publisher"/>
             </dct:publisher>
             <dct:description xml:lang="en">
-                <xsl:value-of select="$ontologyDescription"/>
+                <xsl:value-of select="$ontologyDescriptionShapes"/>
             </dct:description>
             <rdfs:comment>This version is automatically generated from <xsl:value-of
                     select="tokenize(base-uri(.), '/')[last()]"/> on <xsl:value-of

diff --git a/test/ePO-default-config/config-parameters.xsl b/test/ePO-default-config/config-parameters.xsl
@@ -95,20 +95,28 @@
     <!-- _______________________________________________________________________   -->
     <!--    This section contains the variables used to build the ontology metadata-->
     <xsl:variable name="moduleReference" select="'core'"/>
-    <!--    dct:title -->
-    <xsl:variable name="ontologyTitle" select="'eProcurement Ontology - core'"/>
+    <!--    dct:title-->
+    <xsl:variable name="ontologyTitleCore" select="'ePO Core core'"/>
+    <xsl:variable name="ontologyTitleRestrictions" select="'ePO Core restrictions'"/>
+    <xsl:variable name="ontologyTitleShapes" select="'ePO Core shapes'"/>
     <!--    dct:description-->
-    <xsl:variable name="ontologyDescription"
+    <xsl:variable name="ontologyDescriptionCore"
         select="
-            'This module provides the definitions for the eProcurement ontology core.
-        Procurement data has been identified as data with a high-reuse potential.
-        Given the increasing importance of data standards for eProcurement, a number of initiatives
-        driven by the public sector, the industry and academia have been kick-started in recent years.
-        Some have grown organically, while others are the result of standardisation work.
-        The vocabularies and the semantics that they are introducing, the phases of public procurement that they are covering,
-        and the technologies that they are using all differ. These differences hamper data interoperability and thus its reuse by them or by the wider public.
-        This creates the need for a common data standard for publishing procurement data, hence allowing data
-        from different sources to be easily accessed and linked, and consequently reused.'"/>
+        'This artefact provides the definitions for the eProcurement Ontology Core.
+        This artefact excludes the restrictions.
+        The eProcurement Ontology describes objects and concepts, with definitions, attributes and relationships which are present within the European public procurement domain.
+        The provision of these concepts provides the basis for a common understanding of the domain for all stakeholders ensuring the quality of data exchange and transparency.'"/>
+    <xsl:variable name="ontologyDescriptionRestrictions"
+        select="
+        'This artefact provides the restrictions and inference-related specifications for the eProcurement Ontology Core.
+        This artefact excludes the definitions of concepts.
+        The eProcurement Ontology describes objects and concepts, with definitions, attributes and relationships which are present within the European public procurement domain.
+        The provision of these concepts provides the basis for a common understanding of the domain for all stakeholders ensuring the quality of data exchange and transparency.'"/>
+    <xsl:variable name="ontologyDescriptionShapes"
+        select="
+        'This artefact provides the generic datashape specifications for the eProcurement Ontology Core.
+        The eProcurement Ontology describes objects and concepts, with definitions, attributes and relationships which are present within the European public procurement domain.
+        The provision of these concepts provides the basis for a common understanding of the domain for all stakeholders ensuring the quality of data exchange and transparency.'"/>
 
     <!--    rdfs:seeAlso -->
     <xsl:variable name="seeAlsoResources"