ISSUE-140: sosa:hasvalue is different to ssn:hasValue

sosa:hasValue

sosa:hasvalue is different to ssn:hasValue

State:

CLOSED

Product:

Semantic Sensor Network Ontology

Raised by:

Kerry Taylor

Opened on:

2017-01-11

Description:

sosa:hasValue is a datatype property whereas ssn:hasvalue is an object property, although they are both intended to represent the observed value of an observation. If they are different things then they need different names. If they are the same thing they should be of the same type.

With the removal of dul, the encoding of data values in ssn has become difficult,
as previously it relied on an ssn:observationresult (the range for ssn:hasvalue) being a dul:region. This was very flexible, albeit complex for the simple literal case. This should be re-considered together with sosa result encoding.

also the mapping table for sosa:hasvalue misses the ssn counterpart.

Related Actions Items:

No related actions

Related emails:

1. [Minutes SSN] 2017-03-07 (from fd@w3.org on 2017-03-08)
2. Re: Proposals (was Re: Architecture of SOSA/SSN integration) (from rob@metalinkage.com.au on 2017-02-02)
3. Re: Proposals (was Re: Architecture of SOSA/SSN integration) (from janowicz@ucsb.edu on 2017-02-01)
4. Re: Proposals (was Re: Architecture of SOSA/SSN integration) (from armin.haller@anu.edu.au on 2017-02-01)
5. Some concerns (was Re: Agenda SSN meeting this week) (from phila@w3.org on 2017-01-23)
6. Agenda SSN meeting this week (from armin.haller@anu.edu.au on 2017-01-23)

Related notes:

Display change log