Public procurement graphs is self-descriptive and decoupled from applications
Rule Definition
Public procurement graphs are self-descriptive and do not rely on applications for their interpretation or meaning.
“Self-descriptive” means that the graph contains explicit semantics related to its business domain, provenance, policies, validation, and business rules.
Additional Information
Rule elaboration
Public procurement graphs “know” their meaning, provenance (including transformations), policies, validation, and business rules.
This semantics is explicit and part of the graphs themselves.
For example, if the graph contains a statement <s> <p> <o>, it should be able to answer the following questions:
-
What is the meaning of the predicate
<p>?
The answer should provide the definition of the respective property, what kind of property it is, which ontology defines it, its version, when it was last updated, and which axioms are related to it (such as domain, range, or sub-property). -
If
<o>is a class, what does this class mean?
Similar to the predicate above. -
How was the statement created?
It could have been created manually (linked to an agent and a specific date); through transformations (related to a transformation map, such as an RML triple map); or inferred (associated with a rule, source data, and the agent that triggered the inference at a certain time). -
What is the policy of that statement?
For example, who has what kind of rights. - Which validation rules target
<o>? - What constraints are defined for
<p>?
Rule source
https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX%3A52023XC0316%2802%29&qid=1678976891382 https://www.go-fair.org/fair-principles/ https://datacentricmanifesto.org/principles/ https://ec.europa.eu/info/funding-tenders/opportunities/portal/screen/opportunities/tender-details/docs/1837c208-7869-4190-bf65-3bccd8a1f919-CN/ANNEX%20I%20-%20Annex%20I.a%20Tender%20specifications%20EC-GROW2025OP0002%20Part%202_V1.pdf#page=11&zoom=100,102,185
Rule implementation
(Provide only URIs of formal encodings of the rules for execution. These are typically URIs of SHACL rules or RML maps. Each URI should be provided on a new line with no additional information)
Implementation note
(Provide additional implementation information if needed)
Related rules
(Include URLs of related rules)
Related generic rule
(If the rule is a specialisation of a generic rule registered in this Rulebook, include here URL of that generic rule)
History note
(If applicable, add here a note about a previous state of the rule, before the Rulebook)