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


Help: OASIS Mailing Lists Help | MarkMail Help

ebxml-jc message

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

Subject: RE: [ebxml-jc] FW: reminder: TC mapping

Title: RE: [ebxml-jc] FW: reminder: TC mapping

Step 5b: The CPA negotiation process may be described by a BPSS instance.

I also think that there may be a relationship between CPP/CPA and WSDL (or some future version of it): The same services that I refrence in my CPPs and CPAs may have WSDL descriptions. A CPP says here's all my behavioural capabilities and a service directory (WSDL instances) says here's my interfaces.


-----Original Message-----
From: Dale Moberg [mailto:dmoberg@cyclonecommerce.com]
Sent: Friday, November 16, 2001 12:31 PM
To: Karl F. Best; ebxml-jc@lists.oasis-open.org
Subject: RE: [ebxml-jc] FW: reminder: TC mapping


The following  relational links would be ones
that could be added to the diagram you
attached. ( I haven't studied the labels
used on the links to indicate the relation's
flavor, but these are some relational flavors
that exist).

1. CPPA _uses_ the Registry (CPPs or CPA templates can be stored in the
2. CPPA _has_xlinks_to BPSS instance documents (and so the TCs have to
3. Messaging may_export_or_import CPP or CPA instances (so TCs have to
4. Registry uses Messaging.
5. CPPA (future) may use Messaging in Negotiation.
6. The CPPA itself binds BPSS instances to MSH collaboration channels
(forces CPPA TC to be concerned that MSH aligns with BPSS, in addition
aligning with them)
(bind here means to show how the BP is implemented within MSH

That is a start.


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

Powered by eList eXpress LLC