-
Notifications
You must be signed in to change notification settings - Fork 18
Add new information requirements
eprocurementontology edited this page Apr 26, 2017
·
6 revisions
To propose new information requirement(s), please submit an issue by clicking here. And then click on "New issue".
Replace the text of the default template (first row and first column) by the text of the table below:
Element | Description |
---|---|
ID | Identifier, short string to be used as reference to the requirement, for example R1, R2. |
Description | Description of the requirement, using keywords such as MUST, COULD and SHOULD. |
Related Use Case | In the context of the e-procurement ontology, requirements are directly linked to use cases. Therefore, it is useful to indicate to which use case(s) the requirement is related, e.g. “UC1”. |
And then fill the table with your input by following the guidelines provided in the table above (second column).
Find a list of issues related to this topic by clicking here.
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