ebxml-tp message


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

 


Help: OASIS Mailing Lists Help | MarkMail Help
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index]

Subject: service binding - tech comment v0.2 CPP/CPA


All,

One of the issues that has been discussed both on and
off list is the purpose and function of the ServiceBinding
element.

There has been some confusion and also some concern that
the current draft of the CPP will make it difficult
at best for automated CPP+CPP->CPA mapping.

One of the concerns was that in the current design, it is difficult 
to determine if all of the messages for a given collaboration
protocol are actually "bound" to a DeliveryChannel. 

Another concern raised is how to map alternate delivery channels
to a given collaboration protocol, etc.

I would therefore like to propose the attached revision to the
Role element that I think will make things a little clearer
than they are in v0.2 as well as to provide a little better
closure on ensuring that all messages are "bound" to
a delivery channel.

This proposal also involves removing the ServiceBinding child
element from the DeliveryChannel, as this function is now covered
with the attached proposed change to the Role and ServiceBinding 
elements.

Comments are encouraged.

Cheers,

Chris

Role element.doc

begin:vcard 
n:Ferris;Christopher
tel;cell:508-667-0402
tel;work:781-442-3063
x-mozilla-html:FALSE
org:Sun Microsystems, Inc;XTC Advanced Development
adr:;;;;;;
version:2.1
email;internet:chris.ferris@east.sun.com
title:Sr. Staff Engineer
fn:Christopher Ferris
end:vcard


[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index]
Search: Match: Sort by:
Words: | Help

Powered by eList eXpress LLC