W3C home > Mailing lists > Public > www-tag@w3.org > November 2002

Re: SOAP's prohibiting use of XML internal subset

From: Mark Nottingham <mnot@mnot.net>
Date: Mon, 25 Nov 2002 14:31:23 -0800
Message-ID: <057a01c294d2$c7f1f0c0$f4457743@mnotlaptop>
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
> 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
> feature was used).
> At some point of time the spec *required* usage of the XML declaration
> is, implementations MUST reject XML request bodies without XML
> In practice, as XML processors are not required to report the XML decl
> 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

Received on Monday, 25 November 2002 17:34:48 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 22:55:55 UTC