SAREF4AGRI-2. The extension defines restrictions on saref:Device

Situation: The extension defines a restriction on saref:Device: that it is a subclass of ssn:System.

Proposal: There are two options: either to specialize saref:Device in the extension or to move the restriction to SAREF core.

Status: To be discussed.

added contravenes best practice in saref-portal label

I am against any specialization with the same local name such as s4agri:Device. I consider this would be really confusing for the end users.

In general, because we import SAREF Core, my proposal is to avoid duplicating the declarations and axioms from SAREF Core in extensions.

A lot of lines would need to be deleted from SAREF4AGRI.

mentioned in issue saref-portal#29 (closed)

mentioned in issue saref-portal#31 (closed)

mentioned in issue saref-portal#32 (closed)

mentioned in issue saref-portal#33 (closed)

The issue is about whether to specialize or move the axiom.

I created saref-portal#39 (closed) in order to debate the naming issue.

s4agri saref:Device is used as a rdfs:subClassOf for s4agri saref:Actuator and s4agri saref:Sensor, and as an owl:onClass (minQualifiedCardinality) for s4agri saref:Task. I would suggest specializing s4agri saref:Device with a new name such as s4agri:AgriDevice.

I propose we delete this axiom from SAREF4AGRI.

There is no official alignment to SOSA/SSN on the SAREF side. If there was one, it should be located in the TS of SAREF Core.

I move this issue to SAREF4AGRI, and create one about the SOSA/SSN alignment in SAREF Core

moved from saref-portal#28 (moved)

mentioned in issue saref-core#61

changed milestone to %V2.1.1

closed