- From: Mark Nottingham <mnot@mnot.net>
- Date: Mon, 25 Nov 2002 14:31:23 -0800
- To: "Julian Reschke" <julian.reschke@gmx.de>, "Tim Bray" <tbray@textuality.com>, "Paul Grosso" <pgrosso@arbortext.com>
- Cc: <www-tag@w3.org>
> The issue is the other way around. If a spec specifically forbids some XML > feature, you won't be able to use a conforming XML parser (unless it's > configurable to switch off that feature, or it reliably reports that this > feature was used). > > At some point of time the spec *required* usage of the XML declaration (that > is, implementations MUST reject XML request bodies without XML declaration). > In practice, as XML processors are not required to report the XML decl to > the application, how are you supposed to come up with a conforming > application? It depends on the wording of the specification; if it says "SOAP receivers MUST reject/fault/whatever upon encountering mechanism foo", then yes, it would be impossible. However, if it just says "SOAP messages MUST NOT contain mechanism foo", then it is perfectly possible to build a conforming processor. Based on the principle of being liberal in what you accept, strict in what you emit (also from the IETF ;), I'd say the latter language is preferable (I don't recall what the language is in SOAP1.2, but I'd hope it goes that way...) Cheers,
Received on Monday, 25 November 2002 17:34:48 UTC