[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [Fwd: Re: [wsbpel] Issue 250 - Proposal for Vote]
Rewording the last sentence based on Mark's suggestion: If a link crosses the boundary of the immediate child of <extensionActivity> element, then that element MUST be subject to mustUnderstand="yes". -------- Original Message -------- Subject: Re: [wsbpel] Issue 250 - Proposal for Vote Date: Mon, 03 Apr 2006 10:58:43 -0400 From: Rania Khalaf <rkhalaf@watson.ibm.com> To: Danny van der Rijn <dannyv@tibco.com> CC: Alex Yiu <alex.yiu@oracle.com>, Mark Ford <mark.ford@active-endpoints.com>, 'wsbpeltc' <wsbpel@lists.oasis-open.org> References: <200603312232.k2VMWkeN019331@mx1.tibco.com> <442DB106.6020904@tibco.com> <442DB44B.2000105@oracle.com> <442DB5B8.3090903@tibco.com> Hi guys, First, to help clarify, let's look at what the spec says today. It says, if you DO NOT understand the extension then replace with/treat as <empty/>. So, make that more specific and say If a processor does NOT understand the extension, then the extension activity is treated as an <empty> activity and all the standard elements and standard attributes of the immediate child of the <extensionActivity> are placed on this <empty/> activity. Notice that any additional child elements or constructs of the extensionActivity are dropped in this replacement: <extensionActivity> <foo:myWierdness standard-attributes> standard-elements </foo:myWierdness> </extensionActivity> => <empty standard-attributes> standard-elements </empty> THEN, the resolution of this isssue would be to add the above clarification and then to only adding this sentence: If a link crosses the boundary of an <extensionActivity>, then the element contained within the <extensionActivity> MUST be subject to mustUnderstand="yes".
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]