-
Notifications
You must be signed in to change notification settings - Fork 18
Mapping CM Object type properties
eprocurementontology edited this page May 24, 2017
·
5 revisions
Mapping of the object type properties in the conceptual data model for the three use cases selected:
To propose a new mapping for an object type property or to create any issue related to object type properties, please click here and then click on "New issue". For a new mapping, adapt the first column of the table proposed to follow the object type property template below:
Element | Description |
---|---|
Label | A short title of the object type property, e.g. “specifies” |
Domain | A domain is a way to state that any resource that has a given property is an instance of one or more classes. E.g. the relationship “publishes” has domain “Contracting Authority” and range “call for tender”. |
Range | A range state that the values of a property are instances of one or more classes, e.g. the relationship “publishes” has domain “Contracting Authority” and range “call for tender”. |
URI | A string of characters used to identify a resource |
Use the second column of the template as guidance to propose the new relationship.
see more
-
Presentations
- IFLA-LRM-Volume Aggregation Serialisation
- Notice Types
- ePO-LEX Resource Versioning and Identification
- ePO-Roles
- Discussion Procurement Criteria
- Buyer and Organisation Examples
- Definitions of classes and attributes
- Roles Taxonomy and Procurement Events (Work in Progress)
- DCAT-EPO (Discussion 14/01/2021)
- Roles Group of lots (Discussion 11/05/2021)
see more
see more
- ePO Glossary (spread-sheet)
- ePO Glossary
- Glossary management
- Improve term and definition
- Add new term and definition
Online documentation
Information requirements
Conceptual Model (CM)
OWL
Proof of Concept
see more
Information requirements
Conceptual model
Mapping of the conceptual data entities to OWL