OP-TED / ePO

The eProcurement Ontology provides the formal, semantic foundation for the creation and reuse of linked open data in the domain of public procurement in the EU.
European Union Public License 1.2
58 stars 18 forks source link

add more `FunctionalProperty` annotations #406

Closed VladimirAlexiev closed 7 months ago

VladimirAlexiev commented 1 year ago
epo:hasEEAReceivedTenders
        rdfs:domain  epo:SubmissionStatisticalInformation ;
        rdfs:range   xsd:integer .

epo:hasEUReceivedTenders
        rdf:type     owl:FunctionalProperty ;
        rdfs:domain  epo:SubmissionStatisticalInformation ;
        rdfs:range   xsd:integer .

Why the latter is functional but the former is not?

Consider all props with ranges integer, decimal, date, dateTime, boolean: I think all of them should be declared owl:FunctionalProperty. Eg it won't be any good to have two values for thee flags:

epo:hasEInvoicing  rdfs:domain  epo:ContractTerm ;
        rdfs:range   xsd:boolean .

epo:hasEORoleType  rdfs:range  <skos:Concept> .

epo:hasEOrdering  rdfs:domain  epo:ContractTerm ;
        rdfs:range   xsd:boolean .

epo:hasEPayment  rdfs:domain  epo:ContractTerm ;
        rdfs:range   xsd:boolean .