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

 


Help: OASIS Mailing Lists Help | MarkMail Help

ebxml-bp message

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


Subject: Re: [ebxml-bp] [ebBP] 6/14/2004: WI-21 Pre- and Post Conditions


Monica,

I mentioned last week when John brought this up that I thought
there was an opportunity here to use the ebContext mechanism
to leapfrog this and get to a simple resolution.

I've added use Case #4 to the context proposal to tackle this.

Hopefully this provides a simple and elegant means to achieve
this - where you state a boolean condition in either
beginsWhen / endsWhen declarations - and then point to
an actual context condition in the ebContext instance using
that boolean condition name as effectively the lookup of
the condition you want evaluated (as:setID="ruleName").

The goal here is to give implementers a neat and simple
mechanism in V2.0 BPSS that will cover off most
obvious uses via consistent XML syntax (XPath V1.0).

Thanks, DW

----- Original Message ----- 
From: "Monica J. Martin" <Monica.Martin@Sun.COM>
To: "ebXML BP" <ebxml-bp@lists.oasis-open.org>
Sent: Monday, June 14, 2004 3:51 PM
Subject: [ebxml-bp] [ebBP] 6/14/2004: WI-21 Pre- and Post Conditions


> OASIS.ebBP.WI-21-Pre- and post-conditions;
> Topic|;
> Point|Conditional Attributes that Guide Business Processes;
>
Attachment|http://www.oasis-open.org/archives/ebxml-bp/200405/msg00100.html;
>
Attachment|http://www.oasis-open.org/archives/ebxml-bp/200406/msg00083.html:
>
Attachment|http://www.oasis-open.org/archives/ebxml-bp/200406/msg00084.html;
>
> mm1@
> Dale,
> In late May, I sent an updated summary on the pre-post conditions work
> item (Issue 21) [1]. In that discussion, I proposed we have the
> capability to effectively marry pre-post conditions and beginsWhen and
> endsWhen. At that time I suggested we make these elements to allow us to
> make incremental steps to provide the functionality (i.e. not preclude
> their effective use in implementation). I could see these attributes
> (soon to be elements) as business process constraints. They may apply
> (when fully functional) to how we have started to look at QoS elements
> (such as TTP). However, I realize this may span ebBP versions.
>
> We will have to resolve how external events affect the process (and
> when). I believe this concept supports John's business requirements
> related to content driven process performance.
>
> Thanks.
>
> [1] Martin summary 23 May:
> http://www.oasis-open.org/archives/ebxml-bp/200405/msg00139.html
> Moberg questions:
> http://www.oasis-open.org/archives/ebxml-bp/200406/msg00083.html
> Yunker response:
> http://www.oasis-open.org/archives/ebxml-bp/200406/msg00084.html
> @mm1
>
>
>



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