ISSUE-89: How is it different to an ssn:process? Is it needed at all?

sosa-core:Process

How is it different to an ssn:process? Is it needed at all?

State:

CLOSED

Product:

Semantic Sensor Network Ontology

Raised by:

Kerry Taylor

Opened on:

2016-11-07

Description:

The SOSA rdfs:comment description is entirely new. (long rdfs:comment not copied here).

O&M definition by contrast: "An instance of OM_Process is often an instrument or sensor, but may be a human observer, a simulator, or a process or algorithm applied to more primitive results used as inputs."

ssn definition by contrast:
"A process has an output and possibly inputs and, for a composite process, describes the temporal and dataflow dependencies and relationships amongst its parts. [SSN XG]".

Note that ssn:process is not a dul:process but instead a dul:method, deliberately catching the meaning of reusability that was discussed at a recent meeting.


Btw --- the rdfs:comment to sosa:observation makes it clear that a sosa:observation is NOT an activity nor an act -- "millions of observations may be created via the same Process"! Should it be "millions of observations may be initiated via the same Process"?

(1) Are these alternative meanings for "process" compatible? The O&M one appears to be incompatible (e.g it says a sensor is a process). The sosa:core and ssn seem compatible. Which description is preferred? Do we really need a new one? Can or should both be maintained? If so, how?

(2)Also -- "(as information objects, not their concrete realization)". Can this be clarified?

(3) It is possible here to just remove Process from sosa:core? Although it is used (in documentation, not in reasoning) to restrict the range of the property 'usedProcess', Process is not further defined in sosa-core. It is only a named class -- so there seems little point to it. Again, by advising people to use a process object (whatever that might be) in the filler of usedProcess we have achieved exactly the same result with one fewer class. Why do we need it at all?

Related Actions Items:

No related actions

Related emails:

1. [minutes SSN] 2017-03-28 (from fd@w3.org on 2017-03-29)
2. Re: Agenda SSN meeting this week - 28-03-17 20:00 - 22:00 UTC (from ssimmons@opengeospatial.org on 2017-03-27)
3. Agenda SSN meeting this week - 28-03-17 20:00 - 22:00 UTC (from armin.haller@anu.edu.au on 2017-03-27)
4. Re: [Minutes SSN] 2017 03 15 (from phila@w3.org on 2017-03-20)
5. RE: [Minutes SSN] 2017 03 15 (from Simon.Cox@csiro.au on 2017-03-20)
6. RE: [Minutes SSN] 2017 03 15 (from kerry.taylor@anu.edu.au on 2017-03-20)
7. [Minutes SSN] 2017 03 15 (from phila@w3.org on 2017-03-15)
8. Re: Procedure vs Process in SOSA & ISSUE-89 (from janowicz@ucsb.edu on 2017-02-10)
9. Re: Procedure vs Process in SOSA & ISSUE-89 (from maxime.lefrancois@emse.fr on 2017-02-10)
10. Procedure vs Process in SOSA & ISSUE-89 (from armin.haller@anu.edu.au on 2017-02-10)
11. [Minutes SSN] 2017 02 08 (from phila@w3.org on 2017-02-08)
12. Agenda SSN meeting this week (from armin.haller@anu.edu.au on 2017-02-06)
13. RE: Agenda SSN meeting this week (from kerry.taylor@anu.edu.au on 2017-01-30)
14. Agenda SSN meeting this week (from armin.haller@anu.edu.au on 2017-01-30)
15. [sdw] ssn meeting this week (from armin.haller@anu.edu.au on 2016-12-05)
16. Re: various Issues wrt sosa-core (from janowicz@ucsb.edu on 2016-11-08)
17. Re: various Issues wrt sosa-core (from armin.haller@anu.edu.au on 2016-11-08)
18. various Issues wrt sosa-core (from kerry.taylor@anu.edu.au on 2016-11-07)

Related notes:

Display change log