> [Elena Cusenza] > - I can't understand the purpose of maintaining both "hasOutput" and > "hasResult" property. > If a Process has some unConditionalOutputs, they can be specified in a > Result instance with no > inCondition property set. So why preserve "hasOutput"? > I think that removing "hasOutput" property, defining the outputs of a > Process will be more simple, > better, you'll have only a unique way of specify them. hasOutput declares the types of outputs. hasResult can specify (among other things) the _values_ of the outputs (as functions of the input and local parameters). > - Wich purpose has the property "parameterValue"? Is it the specification of > a range of possible value or the specification of the actual value of the > variable? Do we still have parameterValue? -- -- Drew McDermott Yale University CS Dept.Received on Wednesday, 22 September 2004 15:09:55 UTC
This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 17:32:46 UTC