Andreea Pasare
Andreea Pasare
Check if this is used in standard form mappings first. ![image](https://github.com/OP-TED/ePO/assets/88081600/8e07a6fa-d687-49d8-af2e-45bcdae8c411)
See details in the following issue: https://github.com/OP-TED/ted-rdf-mapping/issues/95
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: ![image](https://github.com/OP-TED/ePO/assets/88081600/3dbf1a15-2a4f-4cc8-a4a9-6009d752fee5)
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: ![image](https://github.com/SEMICeu/CCCEV/assets/88081600/53a75d13-0ad6-4269-898b-20d458174276) 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