RE: [bt-spec] BTP Issue 83 : BTP message related to *part of*application message - 0.9.0.3 solution

[Peter Furniss <peter.furniss@choreology.com>]

 

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

Submitter: Choreology
Category: minor technical
Description:
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.

---

 

The latter changes to the SOAP binding specification, from  3879, specifiy the solution to this:

 

Only CONTEXT and ENROL messages are related (&) to application messages. If there is only one CONTEXT or one ENROL message present in the SOAP-Body, and it does not have an XML  ID attribute, it is related to the whole of the application message in the SOAP-Body. If a CONTEXT or ENROL message has an XML ID attribute, it is related only to those parts of the application message that reference it (using an XML REF attribute). There can be multiple such CONTEXT or ENROL messages, each with an XML ID attribute. If there are multiple CONTEXT or ENROL messages and any do not have an XML ID attribute, such message are not related any of the application message in the SOAP-Body.

Note -- Whether the relatedness has any significance for the application (particularly in the case of ENROL, without an ID parameter, carried with a response), is a matter for the application.

 

Is this correct in terms of XML ? (it was written in a bit of a hurry)

Does it make sense of itself

 

Peter