`s4inma:hasIdentifier` vs `s4inma:hasIDValue` - see saref-portal#2

See saref-portal#2 (closed)

TODO:

• use datatype property saref:hasIdentifier
• define subproperties in extension if needed.

Also:

DP s4ehaw:serialNb conflicts with how serial numbers are represented in SAREF4INMA.

changed milestone to %V2.1.1

changed title from s4{-agri-}:hasID - see saref-portal#2 (closed) to s4{+inma:hasIdentifier vs s4inma+}:hasID{+Value+} - see saref-portal#2 (closed)

See saref-portal#2 (comment 3351)

In SAREF4INMA it is needed to model ID as instances as they might be organized for example as SKOS taxonomies. This alternative model could be added as an option in core. @garciacastro opinions?

At the moment, the decision is to switch to a modeling with datatype properties.

If this alternative modeling choice gathers more support, we should account for it in SAREF Core, so that all the extensions remain "compatible" with SAREF Core, in some sense.

related to saref-portal#67 (closed)

I think that the IDs in SAREF4INMA are more than just textual identifiers. Furthermore, I don't see the need for promoting this to core, since it hasn't appeared in other extensions.

ok with letting it this way for this version

closed