Andreea Pasare

Check if this is used in standard form mappings first. 

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

2

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

Alignment with PEPPOL for eFulfilment

1

The alignment between PEPPOL business term requirements and ePO eFulfilment module is a work in progress. This alignment is done by linking ePO concepts that correspond to each Business Term...

- It is about data and not the data transactions/processes/technical implementations - Present the module (use cases, resources) - Present conceptual model on the documentation page. - Sharepoint structure description

This attribute was an oversight on ePO's side. The classes to be used instead are in the eNotice module: 

Implement mapping of the competition notices content to situations

5

The mapping of the competition notes content to situations is implemented in the following branch: https://github.com/OP-TED/ePO/tree/feature/model-refactoring

The ePO 3.1.1 should contain the following: - bug in handling skos:ConceptScheme class reference - update of metadata

The property "constrains" appears in the HTML specification of CCCEV:  but is missing from the RDF file: https://github.com/SEMICeu/CCCEV/blob/master/releases/2.00/voc/cccev.ttl

Model2owl should not append any new information to the skos:definition property. Please see examples below: - https://github.com/OP-TED/ePO/issues/396 - https://github.com/OP-TED/ePO/issues/397