Re: [ebxml-cppa] Re: [ebxml-cppa-negot] RE: BSI distinguishingsuccess,failure, and transition conditions

[Duane Nickull <duane@xmlglobal.com>]

Karsten:

With all due respect, I must disagree.  The BSI is an abstract concept,
not a component.  There may be an implication that something is missing
from th eother artifacts.  Let's explore that.  What is there that you
would put into a BSI that is not present in the CPP/A, MS, BPSS and
other artifacts?  If something is missing,  it means that we have not
done our jobs properly in writing those artifacts, not that we should
now start another group, add yet another specification and duplicate the
scope of our existing work.

WSDL is another way to describe a BSI, albeit somewhat primitive
compared to the level of detail in all the related ebXML specs (WSDL has
no tie in to the business level agreement etc).  WSDL is also very
implementable.  I point this out because a WSDL instance is an artifact
that describes the BSI.

I agree with you 100% Karsten that people want to build software for
ebXML.  Unfortunately,  we cannot complete the stack until we have
certain artifacts finishes.  For the Design time,  we *really* need the
XML representation of Core COmponents and BIE's, an artifact to bind the
raw CC's and BIE's to business processes (some called this the "assembly
doc"), an artifact for declaring context conditions (some called this
the "Context Rules Message") and more.

At Runtime,  we need to be able to execute the BPSS instances and build
state machines, capture guard and error conditions and exceptions
thereto, access a higher level artifact that controls the business
collaboration (preferrably all in XML format) and have programmatic
access to a variety of other artifacts for BET, Business objects et al. 
I vote to focus our efforts on finishing these items.

Until we decide to actually commit to putting these things into a format
that programmers can work with,  theoretical boxes and lines are all
there is and programmers will have to sit out patiently on the sidelines
waiting for this message to be heard and heeded.

Either that or someone will invent a parser for the Microsoft PPT
palette   ;-)

My $0.02 CAD

Duane

Karsten Riemer wrote:
> 
> Duane,
> 
> I actually think there SHOULD be a spec for the BSI.
> People want to build software for ebXML, and one of the things they need to
> build is a BSI. But nowhere do we describe clearly what exactly we expect such
> a BSI to be able to do, and as importantly, what we do not expect it to do.
> There are bits and pieces in the various specs, but it is so scattered that no
> two readers would get the same collective view of a BSI, and subsequently no
> two implementations will probably be fully interoperable.
> 
> -karsten
> 
> >I wish to clarify what a BSI is for all those who have been actively
> >discussing the subject.
> >
> >The Business Service Interface is an abstract architectural concept that
> >is declared by several implementable artifacts.  Those artifacts include
> >the CPP/A, Message Service and the Business Processes/Collaborations and
> >other associated information.  Together,  the instance values/details
> >contained in those artifacts must represent all the possible information
> >that another party would need to conduct business with you
> >electronically.  Thus,  these declare the interface one may use for
> >servicing e-business.
> >
> >The BSI is not something that will be described in a specification or
> >built as a stand alone application.
> >
> >This is not represented clearly in the current draft due to us not
> >receiving an editable version of the overview (ahem - Mr. Yunker, may we
> >please have this?).  The BSI is akin to the UMM Business Service View
> >collection, albeit not exactly.  Please be aware that there are several
> >changes due for the current archtiecture draft and there is no current
> >comment period hence we are not collecting comments.
> >
> >Thank you.
> >
> >Duane Nickull
> >
> >
> >--
> >VP Strategic Relations,
> >Technologies Evangelist
> >XML Global Technologies
> >****************************
> >ebXML software downloads - http://www.xmlglobal.com/prod/
> >
> >----------------------------------------------------------------
> >To subscribe or unsubscribe from this elist use the subscription
> >manager: <http://lists.oasis-open.org/ob/adm.pl>
> 
> ----------------------------------------------------------------
> To subscribe or unsubscribe from this elist use the subscription
> manager: <http://lists.oasis-open.org/ob/adm.pl>

-- 
VP Strategic Relations,
Technologies Evangelist
XML Global Technologies
****************************
ebXML software downloads - http://www.xmlglobal.com/prod/