Re: [wsbpel-spec-edit] <until> activity => <repeatUntil> activity?

Hi, Yaron, Assaf and all others,

I have checked in the changes for:

----------------------

Apply
Issue 182, Issue 148, Issue 140

(with renaming <until> activity to <repeatUntil> activity
to avoid
conflict in <onAlarm>) 

----------------------

I have not heard anything from other people regarding the renaming
<until> to <repeatUntil>. I still decide checked-in the
<repeatUntil> version anyway because I want to keep our XSD valid
in our CVS and I want to check in my changes before I get on the plane
... :-) ...  And, if we don't like <repeatUntil> we can always
replace it with another activity name later. 

According to Diane's previous email, the pen is passed to Assaf.

Thanks!

Happy July 4th in advance. 

Regards,

Alex Yiu

Alex Yiu wrote:

Hi Yaron and others,
  

  

It seems to me there is conflict between <until> from
<onAlarm> and the new <until> activity.
  

  

(Conflict detection ... thanks to W3C XSV and Oracle XDK in Java -
  

Xerces XSD in Java does not do the detection, while Xerces XSD in C
does the detection)
  

  

=========================
  

 <complexType name="tOnAlarm">
  

   <complexContent>
  

     <extension base="bpws:tExtensibleElements">
  

         <sequence>
  

           <choice>
  

             <element name="for" type="bpws:tDuration-expr"/>
  

             <element name="until" type="bpws:tDeadline-expr"/>
  

           </choice>
  

           <element name="repeatEvery" type="bpws:tDuration-expr"
minOccurs="0"/>
  

           <group ref="bpws:activity"/>
  

         </sequence>
  

     </extension>
  

   </complexContent>
  

 </complexType>
  

=========================
  

  

Note: group "activity" can point to a "until" activity.
  

  

Hence, I would like to suggest to rename the new "until" activity to
"repeatUntil".
  

  

Is that OK with everyone?
  

  

Thanks!
  

  

  

  

Regards,
  

Alex Yiu