RE: [wsbpel] Issue - 146 - Draft of a proposal for vote

["Eckenfels. Bernd" <B.Eckenfels@seeburger.de>]

Hello,

I can't say what the reason for the non-deterministic comment is, but I wonder if we touch the schema here, if we should also add multiple elements for the specific variable types and therefore allow formal definition of which attributes  are allowed. 

I.e. we could have a ElementVariabe, TypeVariable and MessageVariable.


Mit freundlichen Grüßen
Bernd Eckenfels
Chief Architect
--
SEEBURGER AG - Edisonstr.1 , D-75015 Bretten, Germany
Fax: +49 (0)7252 96-2400 - Phone: +49 (0)7252 96-1256
mailto:b.eckenfels@seeburger.de - http://www.seeburger.de


-----Original Message-----
From: Yaron Y. Goland [mailto:ygoland@bea.com]
Sent: Saturday, July 31, 2004 2:23 AM
To: wsbpeltc
Subject: [wsbpel] Issue - 146 - Draft of a proposal for vote


I am thinking of putting the following up for a vote. What do y'all think?

I propose that the definition of tVariable be changed to:

<complexType name="tVariable">
    <complexContent>
       <extension base="bpws:tExtensibleElements">
          <attribute name="name" type="NCName" use="required"/>
          <attribute name="messageType" type="QName" use="optional"/>
          <attribute name="type" type="QName" use="optional"/>
          <attribute name="element" type="QName" use="optional"/>
       </extension>
    </complexContent>
</complexType>

I checked this out with both XML Spy 2004 and the W3C XML Schema 
validator <http://www.w3.org/2001/03/webdata/xsv> and they both said it 
was fine.

	Thanks,

		Yaron

To unsubscribe from this mailing list (and be removed from the roster of the OASIS TC), go to http://www.oasis-open.org/apps/org/workgroup/wsbpel/members/leave_workgroup.php.