mariapoveda / saref-ext Goto Github PK

Correct the typo: "sare:measuresProperty".

Clean a bit the definitions of the imported terms, leaving only the type, the label and the comment.

The auxiliary files (.DS_Store, catalog-v001.xml) should not be included in the repository.

We now have both s4city:Measurement and saref:Measurement. s4city:Measurement has no axioms assigned, it appear sin s4city:FeatureOfInterest axiom. Do we need to keep both or should we move that reference to saref:Measurement and delete the s4city one? @rgcmme

The current implementation of SAREF4CITY splits the definition of terms with blank nodes:

saref:Property a owl:Class ;
	rdfs:subClassOf _:genid50 .

The terms should be completely defined in the resource and not split in multiple resources.

The labels of at least a couple of properties are wrong:

:airFlowRateMax rdf:type owl:ObjectProperty ;
rdfs:label "air flow rate range"@en .

:airFlowRateMin rdf:type owl:ObjectProperty ;
rdfs:label "air flow rate range"@en .

In the documentation of SAREF4BLD, in the overview of classes (http://ontoology.linkeddata.es/publish/saref4bldg/index-en.html#overview) it can be seen that some of the classes do not start with capital letters.
The labels of these classes should be updated.

Review the restrictions on reused terms. If we are restricting them with our properties, we have to specialize them.

As the current proposal for modelling of SAREF4AGRI for platform, system and deployment has been taken from SSN and no changes has been proposed, it would be better to directly reuse SSN URIs.

The current versioning schema follows the pattern X.Y while in the LOT methodology we usually follow major.minor.fix. Shall we update the versions scheme for all extensions to the LOT one? @rgcmme

I did for SAREF4BLDG after a typo spotted but it can be reverted.

It is planned that SAREF 3.0 models FeatureOfInterest and related properties therefore the elements declared in SAREF4AGRI namespace should be replaced by SAREF new ones.

Hi!

There might be a typo in the definition of object property "operatingWight".

Best

Georg

It is planned that SAREF 3.0 models FeatureOfInterest and related properties therefore the elements declared in SAREF4CITY namespace should be replaced by SAREF new ones.