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 .

SAREF4AGRI was developed later than SAREF4BLDG,

• it adds a subPropertyOf to geo:sfContains.
• the comment is too succint

s4agri:contains rdf:type owl:ObjectProperty ;
 owl:inverseOf s4agri:isContainedIn .
 rdfs:comment "contains"@en ;
 rdfs:label "contains"@en ;
 **rdfs:subPropertyOf geo:sfContains** .

SAREF4EHAW was defined by different experts, and defines s4ehaw:contains with a very different meaning:

s4ehaw:contains rdf:type owl:ObjectProperty ;
 rdfs:domain **s4ehaw:Ban** ;
 rdfs:range **s4ehaw:HealthDevice** ;
 rdfs:comment "A Body Area Network or BAN contains one or multiple health devices"@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.