Add `sosa:Observation` to the domain of `hasInput`

[dr-shorthair]

Some 'Observations' use previously generated information as input, in addition to or instead of sensor stimuli. This particularly applies to 'observations' where the procedure is some complex processing or interpretation algorithm.

Observation should be added to the schema:domainIncludes for hasInput to allow specific input values to be indicated, in addition to any general inputs indicated in the procedure description.

[dr-shorthair]

Or should it be renamed hadInput in this context?

[maximelefrancois86]

Good idea ! Then what about hasOutput? How would it relate to hasResult?

[maximelefrancois86]

Or should it be renamed hadInput in this context?

I think this single-letter difference has the potential to generate great confusion among users

[hylkevds]

There are two different uses of hasInput:

• The hasInput of the Procedure points to a parameter description.
• The hasInput of the ProcedureExecution must point to a parameter value and to the parameter description of the hasInput of the Procedure that this value is for.

These are different object properties, so using different names would be better. How about hasInputValue for the second one? I suppose that for the second one we'll still need a class.

[dr-shorthair]

I agree.

[dr-shorthair]

173 introduces hasInputValue and hasOutputValue

[dr-shorthair]

Closed by #173