Locn: adminUnit L1 and L2: Although in the ontology not used in mappings

OP-TED / ePO

The eProcurement Ontology provides the formal, semantic foundation for the creation and reuse of linked open data in the domain of public procurement in the EU.

European Union Public License 1.2

57 stars 18 forks source link

Locn: adminUnit L1 and L2: Although in the ontology not used in mappings #374

Open andreea-pasare opened 1 year ago

andreea-pasare commented 1 year ago

See details in the following issue: https://github.com/OP-TED/ted-rdf-mapping/issues/95

andreea-pasare commented 1 year ago

Will handle this when it will be decided what's the proper alignment methodology to be used between ePO and Core Vocabularies.

AchillesDougalis commented 4 months ago

locn:adminUnitL1 and locn:adminUnitL2 were added in order to be aligned with core-location vocabulary. However they seem to be the literal alternative option for epo:hasNutsCode and epo:hasCountryCode, which are relations to controled lists.

We need to decide on whether locn:adminUnitL1 and locn:adminUnitL2 should be removed in ePO 5.0.0.