every term must have a definition #520
Replies: 3 comments
-
Another example: What's the difference between these classes? epo:Amount a owl:Class ;
rdfs:isDefinedBy <http://data.europa.eu/a4g/ontology> ;
rdfs:label "Amount"@en ;
skos:prefLabel "Amount"@en .
epo:Value a owl:Class ;
rdfs:isDefinedBy <http://data.europa.eu/a4g/ontology> ;
rdfs:label "Value"@en ;
skos:prefLabel "Value"@en . From examination I see: epo:hasMinimumAmount rdfs:domain epo:Value ; rdfs:range epo:Amount . and that
So
|
Beta Was this translation helpful? Give feedback.
-
@VladimirAlexiev Value is currently under revision by the working group with a proposal to use MonetaryValue instead of Value and to use just this class without the need of the class Amount. In any case, in version 2.0.1, Amount is a general amount concept with a value and a currency. Value is a Procurement Value, more domain specific with maximum and minimum value and VAT. |
Beta Was this translation helpful? Give feedback.
-
@andreea-pasare @giorgialodi can you run the query on a current version of the ontologies to see how many lack definition? |
Beta Was this translation helpful? Give feedback.
-
This query shows 194 terms without a definition:
19 of them are classes and the rest are properties.
A prop like this is hard to understand, and using the IT jargon word "Indicator" doesn't make it any easier:
epo:hasVATIncludedIndicator rdfs:label "V a t included indicator"@en .
See how much easier is to understand this:
Beta Was this translation helpful? Give feedback.
All reactions