RE: [bt-spec] BTP Issue 57 : XML Schema applicable to more than SOAP

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

Having looked at this again, we here have realised that although, as agreed at Liberty Corner, we don't need to state that there can be non-XML encodings of the message-set, neither do we want to state that the binding proforma concept applies only to the XML encoding - and in fact, in the case of FAULT(communication-failure) we already state that it will not usually be in XML.

 

The only changes need to avoid the restriction are to delete the word "XML" in the first line of the binding profoma section (to read "the glue between the BTP messages and an underlying transport", and change the BTP message representation in the proforma text to:

 

BTP message representation: This section will define how BTP messages are represented. For many bindings, the BTP message syntax will be as specified in  the XML schema defined in this document, and the normal string encoding of that XML will be used.

 

There are no necessary changes in the binding specifications themselves.

 

Peter

-----Original Message-----
From: Peter Furniss [mailto:peter.furniss@choreology.com]
Sent: 04 January 2002 01:35
To: bt-spec@lists.oasis-open.org
Subject: RE: [bt-spec] BTP Issue 57 : XML Schema applicable to more than SOAP

 

BTP Issue 57 : XML Schema applicable to more than SOAP

Category: editorial
Submitter: Tony Fletcher, Choreology
Description:
The XML schema for the messages is given under the heading 'XML Schema for SOAP Bindings'. This would seem to suggest that this XML schema is tied to this particular binding and there could be other XML schema for other bindings. I do no think that is what is intended. I therefore propose that an 'XML Schema' section is added following the specification of the message in abstract form and that this sections (and any other bindings that use the XML schema) reference the one XML schema specification.

---

 

This was discussed at the Liberty Corner f-t-f.

 

The proposed change is just to delete the words "for SOAP binding" in the section title.

 

The discussion covered the possibility of alternative, non-XML encodings of the BTP message set, but concluded it was not necessary to call this out in the text.