Skip to content
GitLab
Closed
Issue created by Maxime Lefrançois@lefrancoisOwner

Check conformance with SAREF Core ETSI TS 103 264 Clause 5.13 Features of Interest, devices, and spatial objects

See saref-portal#9: "Inconsistent / redundant use of "contains" ObjectProperty in SAREF extensions."

SAREF4ENVI and SAREF4BLDG were developed first.

SAREF4BLDG defines the contains property as transitive.

saref4bldg:contains a owl:ObjectProperty ;
 owl:inverseOf ???:isContainedIn ;
 a **owl:TransitiveProperty** ;
 rdfs:comment "A relation between a physical space and the objects located in such space."@en ;
 rdfs:label "contains"@en .

SAREF4ENVI adds the word "physical" in the comment.

saref4envi:contains rdf:type owl:ObjectProperty ;
 owl:inverseOf ???:isContainedIn ;
 rdfs:comment "A relation between a physical object and the **physical** objects that can be contained in it."@en ;
 rdfs:label "contains"@en .

Proposal for :contains:

  • use definition: "A relation between a physical object and another physical object it contains."@en
  • define as transitive
  • define domain and range as PhysicalObject: a 3D spatial extent, which is also promoted to the core
  • do not align to GeoSPARQL. Leave GeoSPARQL for 2D SpatialObjects
  • add a comparison to saref:consistsOf in the definition (?)
  • in SARE4EHAW, use saref:consistsOf instead of s4ehaw:contains

Status: agreed during STF641 WP2 and STF653 joint meeting 2023-04-25.

In ETSI TS 103 264:

An instance may be classified as both saref:Feature> OfInterest and geo:SpatialObject. The class saref:Device is a sub-class of geo:Feature from the GeoSPARQL standard [8, section 6.2].

SAREF application may attach a geometry to a saref:FeatureOfInterest or a saref:Device using geo:hasGeometry or its sub-properties geo:hasBoundingBox, geo:hasCentroid, geo:hasDefaultGeometry [8, section 6.4].