Issue - 125 - Proposal for Vote

[Yuzo Fujishima <fujishima@bc.jp.nec.com>]

Hi,

Below is my proposed resolution for Issue 125.


Proposed resolution for Issue 125: Literal and Expression
Assignment Semantics.

Part 1 (normative): from-literal assignment format definition

For from-literal assignment, the <from> element information item
must have one and only one child element information item that
is either the same type or a subtype of the information item
specified by the paired <to> element information item. The
namespace name and the local name of the child element
information item are arbitrary, as far as the above condition is
met and the namespace name and the local name are not
"http://schemas.xmlsoap.org/ws/2004/03/business-process/" and
"expression", respectively.

INCORRECT
  <variable name="intTypeVar" type="xsd:int"/>
  ...
  <assign>
    <copy>
      <from>0</from>   <!-- INCORRECT -->
      <to variable="intTypeVar"/>
    </copy>
  </assign>

CORRECT
  <variable name="intTypeVar" type="xsd:int"/>
  ...
  <assign>
    <copy>
      <from><p:intVal xsi:type="xsd:int">0</p:intVal></from>
      <to variable="intTypeVar"/>
    </copy>
  </assign>

Part 2 (non-normative): from-expression assignment note

For from-expression assignment, the expression must be evaluated
to an information item that is either the same type or a subtype
of the information item specified by the paired <to> element
information item.

Here, it is defined that an XPath expression is said to be
evaluated to an information item if the expression returns a
node set that contains one and only one node that represents the
information item.

Note that the following example is correct because the
expression evaluates to an information item representing 0, not
the bare number itself.

CORRECT
  <variable name="intTypeVar" type="xsd:int"/>
  ...
  <assign>
    <copy>
      <from><expression>0</expression></from>
      <to variable="intTypeVar"/>
    </copy>
  </assign>

Yuzo Fujishima
NEC Corporation