Stop hijacking SAREF Core terms

Some extensions like SAREF4ENVI imposes several disjointWith axioms, including across SAREF Core entities. These axioms should either be promoted to SAREF Core, or deleted from SAREF4ENVI.

added lack of homogeneity label

Proposal:

1. DisjointFrom axioms may be defined in SAREF extensions, but if they are used, at least one class in the DisjointFrom axiom should be in the namespace of the extension that is under development.

2. Discuss later which set of SAREF Core classes are pairwise disjoint.

added Agreed label

Examples that violate rule 1 from above:

SAREF4BLDG: saref:Measurement owl:disjointWith saref:Property , saref:UnitOfMeasure ;
SAREF4BLDG: saref:Property a owl:Class ; owl:disjointWith saref:UnitOfMeasure ;
SAREF4CITY: saref:Measurement owl:disjointWith saref:Property , saref:UnitOfMeasure ;
SAREF4CITY: saref:Property a owl:Class ; owl:disjointWith saref:UnitOfMeasure ;
SAREF4AGRI: saref:Property rdf:type owl:Class ;	owl:disjointWith saref:UnitOfMeasure ;
###  https://saref.etsi.org/core/Actuator
saref:Actuator rdf:type owl:Class ;
               rdfs:subClassOf saref:Device ;
               owl:disjointWith saref:Sensor ;
               rdfs:isDefinedBy <https://saref.etsi.org/core/> ;
               rdfs:comment "A device responsible for moving or controlling a mechanism or system."@en ;
               rdfs:label "Actuator"@en .

mentioned in issue saref4envi#12 (closed)

mentioned in issue saref4city#15 (closed)

mentioned in issue saref4bldg#22 (closed)

mentioned in issue saref4agri#15 (closed)

From what I can tell, all affected extensions have now a corresponding issue.

We can safely close this one then.

added 5 - Propose closing label

closed

removed 5 - Propose closing label

mentioned in merge request saref4city!13 (merged)