[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Issue - 125 - semantics of <literal>
Alex, The current draft for Issue 157 reads: In WS-BPEL, the <copy> operation is essentially a one-to-one replacement operation. This requires that both the from-spec and to-spec MUST select exactly one information item each, which includes the case of one TII. Note that this restriction indicates that literal values (the literal variant of from-spec) MUST only contain either a TII, or a single EII, as its top-level value; when the RValue is an AII, a TII is constructed from the normalized value property to be copied as specified in Section 9.4.1, “Replacement Logic of Copy Operations”. Can we say: a <literal> from-spec can be treated as if it were a from-spec that selects the child of the <literal> element, be it a TII or an EII? If we can, we should be able to define the semantics of <literal> as such. What else do we need for the resolution of Issue 125? Yuzo Fujishima NEC Corporation Alex Yiu wrote: > > Could you clarify more about your questions? > Do you mean the XMLNS declaration for child elements? > If so, the XMLNS declaration will be preserved. > > Regards, > Alex Yiu > > > Rania Khalaf wrote: > >> Hi guys, >> one more question. In RE, what happens to namespaces of child elements >> if they are namespace qualified ? >> >> thanks, >> Rania >> > > > > --------------------------------------------------------------------- > To unsubscribe from this mail list, you must leave the OASIS TC that > generates this mail. You may a link to this group and all your TCs in > OASIS > at: > https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php > >
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]