- From: Francis Norton <francis@redrice.com>
- Date: Thu, 20 Sep 2001 18:05:23 +0100
- To: "Champion, Mike" <Mike.Champion@SoftwareAG-USA.com>
- CC: xml-dist-app@w3.org
"Champion, Mike" wrote: > > - Keeping DTD information out of SOAP messages (of course, I'm talking about > the information in the SOAP namespace, not the payload) keeps the lid on a > large can of worms. Without a DTD, you can't declare entities, notations, > default attribute values, and other stuff that significantly limits the > interoperability of XML in practice. I'll guess that the subset of XML that > SOAP now uses could be defined in about 15-20 EBNF productions instead of > the 90 or so that XML 1.0 employs. > Why do you exclude the payload? Are SOAP payloads allowed to contain DTDs and PIs? If a device is too small to support full XML parsing for its SOAP handler, won't it be too small to support full XML parsing for the ultimate SOAP receiver? I have to say that I'm not in favour of subsetting XML but if you were going to subset it, no DTDs and no PIs would make an appealing combination for non-document use. Francis.
Received on Thursday, 20 September 2001 13:09:30 UTC