Does SOAP define an XML Subset for the Rest of the World?
Maybe, but that certainly wasn’t a goal, and there’s some reason for caution. SOAP places other restrictions on its use of XML. For example (again from [1]): “SOAP messages sent by initial SOAP senders MUST NOT contain processing instruction information items. SOAP intermediaries MUST NOT insert processing instruction information items in SOAP messages they relay. SOAP receivers receiving a SOAP message containing a processing instruction information item SHOULD generate a SOAP fault with the Value of Code set to “env:Sender”. However, in the case where performance considerations make it impractical for an intermediary to detect processing instruction information items in a message to be relayed, the intermediary MAY leave such processing instruction information items unchanged in the relayed message.” This was the subject of long debate on distApp and in the working group, and this is not the place to reopen that debate.