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


Help: OASIS Mailing Lists Help | MarkMail Help

ebxml-cppa-ws message

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

Subject: initial discussion


This is the first in a series of messages that I will send to the list
get things kicked off in the Web Services subgroup.  Unless there are
objections, the initial order of business will be to establish the
and objectives of the team.  Next, I would like to have a series of
discussions on possible solutions/approaches, followed by a concrete
plan of
action for implementation.  Pretty standard stuff. ;-)

One of the most important things we need to iron out is what our
charter will be in the upcoming months.  Based on my review of previous
activities in this SC, the web services effort seems to break down into
separate camps:

 Camp 1) Identify integration points between CPP (and possibly CPA?) and

 WSDL documents to achieve a WSDL representation of CPP content.

 Camp 2) Identify methods for introducing variability into the existing
 CPPA schema to accommodate a broader range of web services activities
 (business choreography, security, reliability, etc.)

I definitely get the impression that the previous work done by Arvola,
et al.,
was in Camp 1.  Based on previous F2F presentation materials, I gathered
the main thrust of their activity was towards establishing an
representation of CPP/CPA content in the form of WSDL.  Naturally, the
focused on representing configuration details below the business
layer.  One open item is whether this work should be continued.  Yet
is whether or not the scope of this work should be expanded to include
representation of business collaboration details within WSDL (perhaps by

importing/substituting CPPA collaboration definitions??).

Camp 2 seems to be a bit more apropos given the alignment discussions of
Essentially, the main effort involved here is to allow for the
integration of
other WS definitions within a CPP/A document.  Without getting into the
technical details at this point, I would like to iron out the goals of
effort.  Specifically, I feel we should develop a strategy for including

additional specifications 'by reference' that will not lead to a
binding to any particular definition/specification.

In the upcoming weeks, I would like to narrow down our focus a bit to
some substantial (yet achievable) objectives.  Once we trim the fat, so
speak, then we can go neck deep into the technical details.


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