Joe,
I believe that we've hit on this bigger picture - in terms of
the SOA BUP - creating a higher level of abstraction that
then directs the technology needs. Ours should definately
be a holistic approach - and one that is extensible to future
patterns and technology.
For me - coming from the OASIS BCM approach - there
was never any confusion - BCM requires characteristics
that neither ebXML nor WS deliver - a pure-play SOA
with specific components - such as linking and switching
and the ability to manage context across the entire
implementation space.
So in seeking the means to implement these within the
ebSOA - we achieve a new a vibrant technology mix.
BTW Joe - I guess you realize that for each SOA BUP -
that you need to create business use semantic templates
that capture the equivalent of class models associated
with the BUP. As I always say you only need to
fix things if they are bust.
Thanks, DW
----- Original Message -----
From: "Chiusano Joseph" <>
To: "Duane Nickull" <>
Cc: <>
Sent: Wednesday, June 09, 2004 7:33 PM
Subject: [ebsoa] [Scope and Mission] Re: [ebsoa] Ben's document
> Apologies if this was discussed on the call today, which I could not
> participate in:
>
> p.12, bottom states the following:
>
> <Quote>
> The ebSOA group may have been created as a response to the urgent
> industry need to solve the B2B and EAI problems, or by the ebXML folks
> as they are trying to upgrade their ebXML to newer versions. Whatever
> the cause that was behind the creation of the ebSOA group, ebSOA group
> should understand what is at stake here and the broader scope of its
> mission. Therefore, ebSOA group should not consider itself as some sort
> of extension to the ebXML efforts, or an extension to the Web services
> e orts. If the ebSOA group follows this line of thinking (an extension
> of ebXML and Web Services combined), the mission of ebSOA group would
> fail and be very scope restrictive. The mission would then fail in
> keeping up with Microsoft work and fail in being able to standardize the
> next revolution of the Web. The "eb" in ebSOA should bear no whatsoever
> relationship with the "eb" as in ebXML.
> </Quote>
>
> How does all of this compare with our charter and our agreed mission?
>
> Thanks,
> Joe
>
> Duane Nickull wrote:
> >
> > I also urge each and every one of you to read Ben's PDF document
> > uploaded to our members section. This reads very well.
> >
> > Duane
> >
> > --
> > Senior Standards Strategist
> > Adobe Systems, Inc.
> > http://www.adobe.com
>
> --
> Kind Regards,
> Joseph Chiusano
> Associate
> Booz | Allen | Hamilton
>
