Issue 4 in sensorml-data-processing: Make processes self-describing
sensorml-dat...@googlecode.com
Owner: csdillard
CC: mike.bo...@uah.edu
Labels: Type-Enhancement Usability Priority-Low
New issue 4 by csdillard: Make processes self-describing
http://code.google.com/p/sensorml-data-processing/issues/detail?id=4
** BACKGROUND **
Suppose someone gives you a ".jar" containing a new ProcessModel. There's
no support in the DataProcess API to discover what inputs and parameters it
is expecting, nor which outputs it produces.
On a related subject, if you are attempting to use a process class (through
code or SensorML), you can't know ahead of time whether you've made any
spelling mistakes in the inputs, outputs, or parameters. The only way
(that I know of) is to attempt to execute the process and then examine any
exceptions or error messages that may result.
** REQUEST **
I propose that we add methods to the DataProcess class: describeInputs(),
describeOutputs(), and describeParameters(). I'm not exactly sure what the
return values should be, but you should be able to tell the names, data
types, and cardinality of all inputs, outputs, and parameters from the
result.
--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings