Hi Alex,
I assume you are talking about the XSD for issue 111, maybe I am wrong. If
so, shouldn't we wait to see how the issue is closed? AFAIK there are two
proposals on hte table.
Paco
Alex Yiu
<alex.yiu@oracle. To: bpel spec <>
com> cc: Francisco Curbera/Watson/IBM@IBMUS, Alex Yiu <>, Yaron
Goland <>, Satish Thatte <>
05/25/2005 11:47 Subject: [wsbpel-spec-edit] XSD details of <extensibleAssign>
PM
Hi all,
As the dusts around extension syntax got settled, I guess it's time to
proceed with some XSD details for <extensibleAssign>.
I believe the XSD of <extensibleAssign> can be as straight forward as that.
<element name="extensibleAssign" type="bpws:tExtensibleElements" />
And, it supports these two variants of syntax.
<extensibleAssign>
<foo:update> .... </foo:update>
</extensibleAssign>
<extensibleAssign foo:emptyVariable="myVar" />
Does it sound good to everybody?
If so, I will forward this email from the editor list to the main TC list.
Do you guys think that we need to have a simple voting to confirm this
XSD details? Or, leave as editorial changes?
Thanks!
Regards,
Alex Yiu