OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

wsbpel message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: Re: [wsbpel] Issue 157 - proposal - latest revision


Hi Charlton

Great that you like this name.

Here is my updated consolidated text:

"RE (Replace-Element-properties): Replace the element at the
destination with a copy of the element at the source. By default, an 
extra step is performed to replace the name of this copied element with 
the name of the destination element. An OPTIONAL keepSrcElementName 
attribute is provided for the case where one desires this extra step not 
to occur, effectively keeping the source elements name. Therefore, the 
default of keepSrcElementName is 'no'.  The result in both cases is that 
all [children] and [attribute] properties of the destination  EII are 
removed, and all [children] and [attribute]  properties of the source 
EII appear at the destination EII.

What do you think ?

Thanks
Rania

Charlton Barreto wrote:
> Hi Rania,
> 
> On further review I don't see any issue with using  "keepSrcElementName" 
> (or "keepSourceElementName").
> 
> With your amendment, do you intend to replace:
> 
> "*      If the replaceDestinationElementName attribute is set to  "yes", 
> an extra replacement step MUST be performed to replace the  destination 
> element-name with the source element-name (i.e.  [namespace name] and 
> [local name] properties)."
> 
> with
> 
> "*      If the keepSrcElementName attribute is set to  "false" 
> (default), an extra replacement step MUST be performed to  replace the 
> destination element-name with the source element-name  (i.e. [namespace 
> name] and [local name] properties)."
> 
> and to replace:
> 
> "RE (Replace-Element-properties): First, remove all [children] and  
> [attribute] properties of the destination EII. Then, copy and add all  
> [children] and [attribute] properties of the source EII to the  
> destination EII. An OPTIONAL replaceDestinationElementName attribute  is 
> provided to further refine the behavior:"
> 
> with
> 
> "RE (Replace-Element-properties): Replace the element at the  
> destination with a copy of the element at the source - by first  
> removing all [children] and [attribute] properties of the destination  
> EII, then copying and adding all [children] and [attribute]  properties 
> of the source EII to the destination EII. An OPTIONAL  
> keepSrcElementName attribute is provided to further refine the  behavior:"
> 
> This is how I see the text reading with your amendment.
> 
> I would use the example provided for EII-to-EII copy with  
> keepSrcElementName to illustrate it.
> 
> I also wanted to pin down whether you sought to have the examples  
> incorporated into the spec itself or a part of a primer. Let me know  
> what your stance is on this....
> 
> -Charlton.
> 
> On 10/08/2005, at 08:30, Rania Khalaf wrote:
> 
>> I strongly  prefer  'keepSrcElementName' instead of  
>> 'replaceDestinationElementName' for the sakes of simplicity and XML ;)
>>
>> That would also change the description of RE (Replace element  
>> properties) to say: "replace the element at the destination with a  
>> copy of the element at the source. If the 'keepElementName'  attribute 
>> is set to false (default), then an additional step is  required where 
>> the name of the copied element is replaced with the  name of the 
>> destination element (add an example)."
>>
>> This is instead of the current description:
>> •    RE (Replace-Element-properties): First, remove all [children]  
>> and [attribute] properties of the destination EII. Then, copy and  add 
>> all [children] and [attribute] properties of the source EII to  the 
>> destination EII. An OPTIONAL replaceDestinationElementName  attribute 
>> is provided to further refine the behavior:
>>
>> Charlton Barreto wrote:
>>
>>> Attached is the latest revision of the Issue 157 proposal,  
>>> reflecting  the comments Alex and I have received since last week,  
>>> including  examples of each of the copy operations in the  proposal's 
>>> matrix.
>>> -Charlton.
>>> -- 
>>> Charlton Barreto
>>> P 1.408.536.4496
>>> cbarreto@adobe.com
>>> www.adobe.com
>>>
>>
>>
>>
> 
> Charlton Barreto
> P 1.408.536.4496
> cbarreto@adobe.com
> www.adobe.com
> 
> 




[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]