Value passing in an execute request.

[pvretano]

Allow value passing to be specified per input rather than requiring thes erver to support both by-value and by-refernce in all cases. The default value for the valuePassing parameter is ["byValue","byReference"] to maintain backward compatability.

Closes #369

[bpross-52n]

SWG meeting from Dec 11th: maxItems will be removed from the enumeration. Enum will be made extensible.

[fmigneault]

@pvretano
Sorry I couldn't assist this morning. Can you add precision about valuePassing?
Is it an extra parameter to be added for each input of each process description?
Can the server specify a conformance class it supports server-wide in the conformsTo response?

[jerstlouis]

@fmigneault My understanding is that it is to be explicitly specified for each input of each process description

[pvretano]

@fmigneault, @jerstlouis is correct. The valuePassing parameter can be specified for each input in a process description. If it is not specified the default value defined by the specification is ["byValue","byReference"] which is backward compatible with the current version of processes.

Question: Would it be of value to also add a valuePassing parameter at the top level of the process description to be a sort of global default? It would alleviate having to repeat the same values over and over and to also override the specification default.

[jerstlouis]

@pvretano My opinion is that would not be very helpful, because the supported values are very likely to depend a lot more on the type of inputs.

e.g., a number or text input would normally be supported "byValue" and a GeoTIFF "byReference".

[fmigneault]

I agree. I prefer to have them repeated in each input than having to cross-validate with the process description each time.

[bpross-52n]

SWG Meeting from January 22nd: Remove min/max items and make the enum extensible.