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: [Fwd: Re: BPEL XML Schema]

FYI ... some old mistakes discovered in the schema.

-------- Original Message --------
Subject: Re: BPEL XML Schema
Date: Thu, 23 Sep 2004 19:14:03 +0200
From: Dieter Koenig1 <dieterkoenig@de.ibm.com>
To: Alex Yiu <alex.yiu@oracle.com>
CC: Alex Yiu <alex.yiu@oracle.com>, Francisco Curbera <curbera@us.ibm.com>, Rania Khalaf <rkhalaf@us.ibm.com>, Satish Thatte <satisht@microsoft.com>

Great, thanks!!
Kind Regards

             Alex Yiu                                                      
             com>                                                       To 
                                       Dieter Koenig1/Germany/IBM@IBMDE    
             23.09.2004 18:56                                           cc 
                                       Francisco Curbera                   
                                       <curbera@us.ibm.com>, Rania Khalaf  
                                       <rkhalaf@us.ibm.com>, Satish Thatte 
                                       <satisht@microsoft.com>, Alex Yiu   
                                       Re: BPEL XML Schema                 

Hi, Dieter,

Thanks for discovering these issues in the schema.
I concur all of your findings.

Those issues have been hidden inside the schema for a while.  It sure
feels good to kill those bugs in schema. :-)

One technical note: for item (5), I will use schema extension to fix
this problem. tOnEvent will extend from tOnMessage.


Alex Yiu

Dieter Koenig1 wrote:

>Hi Alex, there are a couple of places where the XML schema is not yet
>"compliant" with the specification. Please consider the following for one
>of the next XML schema versions:
> 1) In tProcess, element tImport may occur more than once --> add
> 2) In tImport, all attributes are required --> add use="required" (3x)
> 3) In tTargets, element joinCondition must be optional --> add
> 4) In tSource, element transitionsCondition must be optional --> add
> 5) In tEventhandlers, element onEvent is defined with type tOnMessage
>    In tPick, element onMessage is defined with type tOnMessage as well
>    In tOnMessage, a new required attribute messageType has been
>    However, messageType is only needed for onEvent, but not for onMessage
>    -->
>    Introduce new type tOnEvent with attribute messageType
>    Define element onEvent with the new type tOnEvent
>    In tOnMessage, delete attribute messageType
>Kind Regards

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