Dear all,
Please find attached a proposal for SOSA, and a figure that illustrates it.
1)
I have taken the liberty to add some RDFS axioms in SOSA, knowing that such
axioms will never prevent SOSA to become one day part of schema.org. As a
matter of fact, goodrelations, the well known ontology that has been
integrated into schema.org is highly axiomatized:
- it uses disjoint classes axioms
- it uses domains and ranges that are union of classes.
The second point makes it pretty well aligned with schema.org
domainIncludes and rangeIncludes actually, while using only the RDFS and
OWL vocabulary.
See http://purl.org/goodrelations/v1.owl
2)
I also propose to remove the sosa:hasValue.
schema.org already has its way of assigning values to elements (see
http://schema.org/value). Plus, other ways exist to give a value and a unit
of measure to an observation result (QUDT, OM,..)
3)
I have renamed some properties,
- either to be more aligned with SSN
- or so that there is a clear naming convention
There may be other noticeable differences that I did not document yet.
Shall I issue a pull request before we discuss these different points in
separate threads ?
I'm working on the rest of my proposal:
- SSNX: http://www.w3.org/ns/ssn/ssnx
- SSN: http://www.w3.org/ns/ssn/
- various alignment documents proposed by Simon
- some specifications for the server to expose documents and terms in
accordance with best practices.
The old namespace http://purl.oclc.org/NET/ssnx/ssn# would redirect to
http://www.w3.org/ns/ssn/ssnx
- Ontology SSNX deprecates the old terms and aligns them with either a
sosa term, or a ssn term
- Ontology SSN imports SOSA, adds axioms, and other SSN terms.
To me, the only tricky parts in the integration of SOSA/SSN so far are:
- property oldssn:isProducedBy
- SensorOutput and Observation are merged into a single class.
Best,
Maxime
>
