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

 


Help: OASIS Mailing Lists Help | MarkMail Help

wsbpel-spec-edit message

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


Subject: Re: [wsbpel-spec-edit] mistakes in XSD in transitionCondition andjoinCondition syntax description



No problem. I would prefer editing it after F2F.
Tons of TO-DO and emails to catch up before F2F. :-)

Regards,
Alex



Satish Thatte wrote:
Why don't you take the pen and make the changes.

-----Original Message-----
From: Alex Yiu [mailto:alex.yiu@oracle.com] 
Sent: Friday, September 17, 2004 4:22 PM
To: Satish Thatte
Cc: bpel spec
Subject: Re: [wsbpel-spec-edit] mistakes in XSD in transitionCondition
and joinCondition syntax description


Agreed.  :-)

Satish Thatte wrote:

  
This is not a spec bug in the sense of "clarify uniqueness of activity
    
naming".  It is a bunch of clerical mistakes.  We should just fix them.
  
________________________________

From: Alex Yiu [mailto:alex.yiu@oracle.com]
Sent: Thu 9/16/2004 4:18 PM
To: bpel spec
Cc: Alex Yiu
Subject: [wsbpel-spec-edit] mistakes in XSD in transitionCondition and
    
joinCondition syntax description
  

Hi, all editors,

When Yaron and I were cooking the formal proposal for Issue 103, we
    
found a syntax mistake about joinCondition in Section 6.2: 
  
========================
<targets>?            
  <target linkName="ncname">+
     <joinCondition expressionLanguage="anyURI"?>?
       ... bool-expr ... 
     </joinCondition>
  </target>
</targets>
<sources>?
  <source linkName="ncname">+
     <transitionCondition expressionLanguage="anyURI"?>?
       ... bool-expr ... 
     </transitionCondition>
  </source>
</sources>
========================

It is not in sync with the rest of the spec. 

I guess it should become: 
========================
<targets>?            
  <joinCondition expressionLanguage="anyURI"?>?
       ... bool-expr ... 
  </joinCondition>
  <target linkName="ncname"/>+
</targets>
<sources>?
  <source linkName="ncname">+
     <transitionCondition expressionLanguage="anyURI"?>?
       ... bool-expr ... 
     </transitionCondition>
  </source>
</sources>
========================

Also, in the XSD, I believe the "minOccurs" is missing in XSD for
    
joinCondition and transitionCondition:
  
========================
   <complexType name="tTargets">
       <complexContent>
           <extension base="bpws:tExtensibleElements">
               <sequence>
                   <element name="joinCondition"
    
type="bpws:tCondition" minOccurs="0"/>
  
                   <element name="target" type="bpws:tTarget"
    
maxOccurs="unbounded"/>
  
               </sequence>
           </extension>
       </complexContent>
   </complexType>
========================
========================
   <complexType name="tSource">
       <complexContent>
           <extension base="bpws:tExtensibleElements">
               <sequence>
                   <element name="transitionCondition"
    
type="bpws:tCondition" minOccurs="0"/>
  
               </sequence>
               <attribute name="linkName" type="NCName"
    
use="required"/>
  
           </extension>
       </complexContent>
========================


Is this change big enough to file a bug issue ?


Thanks!


Regards,
Alex Yiu




 

    

  



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