You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Feb 28, 2019. It is now read-only.
Previously (SensorML v1.0) the process map associated the process method ID with the executable class. Instead the process execution engine should rely on using the base process UniqueID. During parsing of the AggregateProcess the parser shall get this UniqueID from the typeOf xlink:title attribute (typically) or from the base (i.e. executable) SimpleProcess uniqueID if the process is defined inline.
Recommended Best Practice is to treat executable process components as instance of the base (executable) process. This would certainly be the approach for a configurable process but it should be the case for any component of an aggregate process whether it has additional configuration information or not.
Previously (SensorML v1.0) the process map associated the process method ID with the executable class. Instead the process execution engine should rely on using the base process UniqueID. During parsing of the AggregateProcess the parser shall get this UniqueID from the typeOf xlink:title attribute (typically) or from the base (i.e. executable) SimpleProcess uniqueID if the process is defined inline.
Recommended Best Practice is to treat executable process components as instance of the base (executable) process. This would certainly be the approach for a configurable process but it should be the case for any component of an aggregate process whether it has additional configuration information or not.
Such as:
http://www.sensorml.com/sensorML-2.0/examples/aggregateConfigured.html
The text was updated successfully, but these errors were encountered: