Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feature epo 614 #116

Merged
merged 2 commits into from
Oct 27, 2022
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 1 addition & 2 deletions config/ePO-default/config-parameters.xsl
Original file line number Diff line number Diff line change
Expand Up @@ -20,8 +20,7 @@
<xd:p>This module defines project level variables and parameters</xd:p>
</xd:desc>
</xd:doc>
<!-- List of xmi files to be merged into a single xmi file-->
<xsl:variable name="xmiFileList" select="collection('../../test/test-multi-xmi?select=*.xmi')"/>

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

indeed we do not need this

<!-- a set of prefix-baseURI definitions -->
<xsl:variable name="namespacePrefixes" select="fn:doc('namespaces.xml')"/>

Expand Down
6 changes: 4 additions & 2 deletions config/ePO-default/namespaces.xml
Original file line number Diff line number Diff line change
Expand Up @@ -14,15 +14,15 @@
<prefix name="skos" value="http://www.w3.org/2004/02/skos/core#"/>

<prefix name="epo" value="http://data.europa.eu/a4g/ontology#"/>
<prefix name="epo-not" value="http://data.europa.eu/a4g/ontology#"/>
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

good input for the moment.

I fear we will need other namespace definitions too, at least for eOrdering, eFulfillment.
you may as well add them now: "epo-cat", "epo-ful" (same base URI as above)

<prefix name="epo-cat" value="http://data.europa.eu/a4g/ontology#"/>
<prefix name="epo-ecat" value="http://data.europa.eu/a4g/ontology#"/>
<prefix name="nuts" value="http://data.europa.eu/nuts/"/>
<prefix name="reg2015" value="http://data.europa.eu/a4g/extension/ontology#"/>
<prefix name="espd" value="https://github.com/ESPD/ESPD-EDM/"/>
<prefix name="at-voc" value="http://publications.europa.eu/resource/authority/"/>
<prefix name="time" value="http://www.w3.org/2006/time#"/>
<prefix name="locn" value="http://www.w3.org/ns/locn#"/>
<prefix name="core-voc" value="http://data.europa.eu/m8g/"/>
<prefix name="cv" value="http://data.europa.eu/m8g/"/>
<prefix name="core" value="http://data.europa.eu/m8g/"/>
<prefix name="cpv" value="http://data.europa.eu/m8g/"/>
<prefix name="cpsv" value="http://data.europa.eu/m8g/"/>
Expand All @@ -31,4 +31,6 @@
<prefix name="geosparql" value="http://www.opengis.net/ont/geosparql#"/>
<prefix name="dul" value="http://www.loa-cnr.it/ontologies/DUL.owl#"/>

<prefix name="person" value="http://www.w3.org/ns/person#"/>

</prefixes>
3 changes: 3 additions & 0 deletions src/xml/merge-multi-xmi.xsl
Original file line number Diff line number Diff line change
Expand Up @@ -16,6 +16,9 @@

<xsl:import href="../../config/config-proxy.xsl"/>

<!-- List of xmi files to be merged into a single xmi file-->
<xsl:variable name="xmiFileList" select="collection('../../test/test-multi-xmi?select=*.xml')"/>
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

why do we want to take XMI files from a "test" location?
This shall not be in the master branch. We need a proper mechanism to indicate where is the input location.


<xsl:template match="/">

<xmi:XMI xmlns:uml="http://www.omg.org/spec/UML/20131001" xmlns:xmi="http://www.omg.org/spec/XMI/20131001" xmlns:umldi="http://www.omg.org/spec/UML/20131001/UMLDI" xmlns:dc="http://www.omg.org/spec/UML/20131001/UMLDC" xmlns:thecustomprofile="http://www.sparxsystems.com/profiles/thecustomprofile/1.0">
Expand Down
46,933 changes: 46,933 additions & 0 deletions test/test-multi-xmi/ePO_CM.xml

Large diffs are not rendered by default.

6,283 changes: 6,283 additions & 0 deletions test/test-multi-xmi/ePO_catalogue.xml

Large diffs are not rendered by default.

2,661 changes: 2,661 additions & 0 deletions test/test-multi-xmi/ePO_notice.xml

Large diffs are not rendered by default.

21 changes: 21 additions & 0 deletions test/test-multi-xmi/metadata.xml
Original file line number Diff line number Diff line change
@@ -0,0 +1,21 @@
<?xml version="1.0" encoding="windows-1252"?>
<metadata>
<title>eProcurement core ontology</title>
<!-- Ontology version -->
<version>3.0.1</version>
<!-- Description for the CORE module -->
<description>
This module provides the definitions for the core eProcurement ontology.
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.
</description>
<!-- default imports for each module -->
<imports resource="http://purl.org/dc/terms/"/>
<imports resource="http://www.w3.org/2004/02/skos/core"/>
</metadata>