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


Help: OASIS Mailing Lists Help | MarkMail Help

ebsoa message

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

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


I'm agreeing with that - but I was also saying that
the BPSS team need only set the scene here fior
the V2 specification - since the heavy lifting on
this probably can be differed and continued
by the ebSOA team more effectively beyond
that start point.

There's abviously more that can be done in
terms of detailed specification of the mechanisms
and options for controlling the interactions
between the various moving parts here. And
that of coruse carries us into the BPSS V3 too.

Thanks, DW

----- Original Message ----- 
From: "Monica J. Martin" <Monica.Martin@Sun.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"
Sent: Friday, February 04, 2005 11:34 AM
Subject: [ebsoa] Re: [ebxml-bp] Closing the gap between MSI and BSI and move

> David Webber (XML) wrote:
> >Webber: 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
> >
> >
> mm1: David, I would suggest we have some clear boundaries before
> engaging ebSOA team. Some of the discussion surrounds assumptions about
> the role of the MSI or BSI should be clarified by the experienced
> parties and experts involved from ebBP and ebMS teams (not to say there
> are not experts in ebSOA). Thanks.

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