Proposed implementation of #106

[maximelefrancois86]

As part of our work at ETSI on the development of a new version of SAREF, we reached last week an agreement on how to solve this issue.

Note that this is a compromise that resolves a six year long dispute between two former contributors to SOSA/SSN 😉, so I hope it will be well received by the group.

• https://raw.githack.com/w3c/sdw-sosa-ssn/property-of-interest/ssn/index.html#SSNProperty
• https://raw.githack.com/w3c/sdw-sosa-ssn/property-of-interest/ssn/index.html#SSNPropertyOfInterest

[dr-shorthair]

Also see #49 and #52

Closes #106

[rob-metalinkage]

Label of PropertyOfInterest is just "Property"

is there a need for a PropertyKind as well for symmetry to allow for more general classifications? And potentially a constraint for ObservationCollections that observedProperty objects are some form of specialisation of PropertyKind? Is there an equivalent constraint for Property w.r.t to PropertyOfInterest ?

also we have identified 3 possible profiles for observedProperty depending on which case - is the range of observedProperty a union of these options or do we need more predicates?

examples are critical here me feels..

[maximelefrancois86]

@rob-metalinkage I fixed the nit in latest commit on this branch.

If in addition to "PropertyOfInterest" you believe we would need a third class named "PropertyKind", I suggest you approve this PR first, then we could discuss that need.

I intentionally left out any modification of the ranges of object properties, to proceed incrementally