Re: [ebsoa] Re: [ebxml-bp] Closing the gap between MSI and BSI and move on

["David Webber \(XML\)" <david@drrw.info>]

Duane,

Clearly - but on the other hand the BSI can specify
behaviours, characteristics and functionality that
implementations should support and enable.

It's that level of detail that needs to be clear for
implementers - what the intended functional
patterns are.

I think we have moved a very large distance
from the old 1.04  model in that regard and
what is now possible to configure and
orchestrate.

The factis though that the CPA is still at
the heart of faciliting a lot of this.

DW

----- Original Message ----- 
From: "Duane Nickull" <dnickull@adobe.com>
To: "David Webber (XML)" <david@drrw.info>
Cc: "Sacha Schlegel" <sschlegel@cyclonecommerce.com>; "ebXML BP"
<ebxml-bp@lists.oasis-open.org>; <ebxml-msg@lists.oasis-open.org>; "ebsoa"
<ebsoa@lists.oasis-open.org>
Sent: Friday, February 04, 2005 3:18 PM
Subject: Re: [ebsoa] Re: [ebxml-bp] Closing the gap between MSI and BSI and
move on


> It is already defined in the 1.04 TA doc - the CPA is the gatekeeper.
> It points at the BPSS instance. It constrains the parameters that make
> up the BSI.  THe BSI is an abstract architectural concept, not a
> concrete implement able thing.
>
> Duane
>
> David Webber (XML) wrote:
>
> >Sacha,
> >
> >I think this is also something that involves the ebSOA team - as
> >these are part of the patterns needed.
> >
> >We can certainly jointly develop this - and put initial outline work
> >in the BPSS specification - that can then be more formally
> >detailed for the ebSOA work in 2005 here.
> >
> >Thanks, DW
> >
> >----- Original Message ----- 
> >From: "Sacha Schlegel" <sschlegel@cyclonecommerce.com>
> >To: "ebXML BP" <ebxml-bp@lists.oasis-open.org>;
> ><ebxml-msg@lists.oasis-open.org>
> >Sent: Friday, February 04, 2005 9:32 AM
> >Subject: [ebxml-bp] Closing the gap between MSI and BSI and move on
> >
> >
> >Hi ebXML Message Service team
> >Hi ebXML Business Process team
> >
> >I suggest to define an interface between
> >
> >o MSI and BSI (or MSH and BSH)
> >
> >and close that gap in the ebXML spec and move on to the next step, from a
> >ebBP view point, to define an interface between
> >
> >o BSI and private business process engines (or BSH and OASIS WSBPEL for
> >example)
> >
> >Regards
> >
> >Sacha
> >
> >-----------------------------
> >
> >MSH = Message Service Handler
> >BSH = Business Service Handler
> >MSI = Message Service Interface
> >BSI = Business Service Interface
> >WSBPEL = Web Services Business Process Execution Language
> >
> >PS: BSH is to ebXML Business Process what MSH is to ebXML Message Service
> >
> >
> >
> >
> >
> >
> >
>
> -- 
> ***********
> Senior Standards Strategist - Adobe Systems, Inc. - http://www.adobe.com
> Vice Chair - UN/CEFACT Bureau Plenary - http://www.unece.org/cefact/
> Enterprise Server Products - http://www.adobe.com/enterprise/main.html
> ***********
>
>
>