Extensions copy declarations and definitions from SAREF Core

Situation: many extensions copy declarations and definitions of entities from SAREF Core or other SAREF extensions. Sometimes the copy is partial, or wrong. It is unnecessary to copy definitions if the reused ontology is imported. These could be deleted to limit the number of changes necessary when SAREF Core evolves.

Examples:

SAREF4CITY defines saref:controlsProperty with wrong comment and no rdfs:isDefinedBy metadata.
SAREF4CITY keeps some axioms from SAREF V2.1.1 that were deleted in SAREF V3.1.1. For example it still contains a universal restriction on saref:measurementMadeBy to only instances of the saref:Device class. In fact, saref:Device is now the range of saref:measurementMadeBy so this local restriction was considered useless, and deleted in SAREF V3.1.1.
In SAREF4AGRI saref:FeatureOfInterest contains rdfs:comment https://saref.etsi.org/core/, which is wrong.

Affects: SAREF4ENER, SAREF4ENVI, SAREF4BLDG, SAREF4CITY, SAREF4INMA, SAREF4EHAW, SAREF4WEAR, SAREF4WATR

Proposal: SAREF ontologies should import SAREF ontologies when relevant. Definitions should not be copied.

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information