Lists Home |
Date Index |
10/30/2002 12:57:21 PM, Elliotte Rusty Harold <email@example.com> wrote:
>Yes, so a SOAP engine needs an XML parser that will detect and report
>the presence of a document type declaration so it can respond with
>the appropriate fault. It cannot use a processor that simply ignores
>the document type declaration,
No disagreement. I thought the issue was over strict conformance to
specs; you can't conform to SOAP if you accept everything XML defines
as legal. Clearly an XML processor is a BIG help in building a
>On no. Not another one. You mean you can send something to a SOAP
>service that is not an XML document, provided the service knows how
>to turn it into an infoset?
As someone pointed out, it's in the spec, but not in any known toolkits.
The use case for this is exactly what the "horror of XML" article hints
at -- compression, encryption, etc. Better to anchor interop in some specs
rather than encouraging the HTML-ish liberality and bug-for-bug
compatibility. Whether or not the W3C Infoset spec is up to this
job is another matter, but the IDEA of anchoring SOAP on the "infoset"
rather than syntax seems sound to me.