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


Help: OASIS Mailing Lists Help | MarkMail Help

ebxml-transport message

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

Subject: Re:


These need agreement between TP and TRP.  Please bring them up at the
Monday afternoon joint meeting.

I'm not sure what you mean by "type" values.  In CPP-CPA ver. 0.0, Action
brackets several properties, is identified by the request name, and also
has an attribute whose value is a unique identifier.  I expect that in the
MSH header, Action is the request name or the action identifier (the MSH
spec needs to be specific about this if it isn't already specific).
Similarly Service Interface brackets the set of action definitions that are
supported by each party.  It has an identifier which I expect will go in
the ServiceInterface (or whatever name) tag in the message header.



Martin W. Sachs
IBM T. J. Watson Research Center
P. O. B. 704
Yorktown Hts, NY 10598
914-784-7287;  IBM tie line 863-7287
Notes address:  Martin W Sachs/Watson/IBM
Internet address:  mwsachs @ us.ibm.com

"Burdett, David" <david.burdett@commerceone.com> on 10/31/2000 06:14:37 PM

To:   "ebXML Transport (E-mail)" <ebxml-transport@lists.ebxml.org>


To get around the Service Interface definition problem. How about using the
term Service Type in the ebXML Message Header. Similarly we could have
Action Type instead of Action. I think that both these elements will
"type" values and therefore perhaps more accurately represents what it is.



Product Management, CommerceOne
4400 Rosewood Drive 3rd Fl, Bldg 4, Pleasanton, CA 94588, USA
Tel: +1 (925) 520 4422 (also voicemail); Pager: +1 (888) 936 9599
mailto:david.burdett@commerceone.com; Web: http://www.commerceone.com

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

Search: Match: Sort by:
Words: | Help

Powered by eList eXpress LLC