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


Help: OASIS Mailing Lists Help | MarkMail Help

bt-spec message

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

Subject: [bt-spec] BTP Issue 83 : BTP message related to *part of* applicationmessage

This issue has been added to the BTP issue list

BTP Issue 83 : BTP message related to *part of* application message

Submitter: Choreology
Category: minor technical
In the SOAP bindings, any and all application message in the SOAP-Body is related to the appropriate BTP messages in the SOAP-Header. It is possible to conceive of applications where a compound *application* message has parts that are intended to be in one BT, some in another (almost certainly atoms within the same cohesion).

A relationship between a particular BTP message (CONTEXT or ENROL) and part of an application message could be indicated using the ID and REF mechanisms of XML. There would be significant implications for the application at each end, which has got to sort out which BT applies, but the basic protocol mechanism would be easy to specify.

To comment on this issue, please follow-up to this announcement on the bt-spec@lists.oasis-open.org (replying to this message should automatically send your message to that list).

The current draft, with line numbers is available in pdf format and word format.

To add a new issue, please email to Peter Furniss peter.furniss@choreology.com. It helps if you propose a category (technical, minor technical, editorial, minor editorial).

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

Powered by eList eXpress LLC