s4envi:contains

OP s4envi:contains link a physical object and the physical objects that can be contained in it. The “can” in this definition makes it ambiguous; The domain and range is not defined; Physical objects are relevant for other extensions and could be promoted to SAREF Core, together with this property.

added clarity issue in saref-portal label

Agreed it's ambiguous.

I'd propose to at least change the name to remove the ambiguity.

I inspected the ontology and found that s4envi:contains is not used in the examples and only mentioned as a property that can be applied on a PhysicalObject. We may remove the "can" and promote it to core along with the PhysicalObject.

I don't see the word "can" ambiguous, sometime it is used for properties that may be used or not, that is for cardinality 0..N. But agree to rewrite the comment.

2023-09-11

Proposed solution: delete or deprecate s4envi:contains . At least delete the "can" which is ambiguous

Have some property saref:contains in SAREF for the containment of physical objects. OR recommend to do how GeoSPARQL recommends to do.

In SAREF4ENVI, use that way of doing things instead.

moved from saref-portal#43 (moved)

changed milestone to %V2.1.1

delete s4envi:contains and use saref:contains instead, or geosparql whenever relevant

mentioned in issue saref4bldg#13 (closed)

mentioned in commit 4f5429e0

mentioned in merge request !17 (merged)

added 5 - Propose closing label

mentioned in issue #6 (closed)

mentioned in issue saref-core#55 (closed)

SAREF V3.2.1 does not yet define saref:contains

Issue saref-core#55 (closed) is a proposal to fix that.

mentioned in commit 98d59726

closed with commit 4f5429e0

closed with merge request !17 (merged)