- From: Christian Wolfgang Hujer <Christian.Hujer@itcqis.com>
- Date: Fri, 14 Sep 2001 17:41:33 +0200
- To: "William F. Hammond" <hammond@csc.albany.edu>, <www-html@w3.org>
Hello, > -----Original Message----- > Christian Wolfgang Hujer <Christian.Hujer@itcqis.com> > > > Since more XML Parsers and software based on them might have this bug, > > and since it will take some time until these bugs are fixed, I > > suggest, that the HTML working group changes the URI of the drivers to > > be absolute URLs. > > Although I have not verified the correctness of all of this, it does > seem to be pointing in the right direction. > > BUT going to absolute URI's is NOT A GOOD IDEA if those URI's are > network resources. Surely we don't want all of our parsing to wait > for the network. Much less would we want a resource-serving host > to think that it is experiencing too many hits and, as a result, > close the referenced resource. > > If one likes, the resources can be imported once, and then one can > substitute "full pathnames". > > Much better to get a fixed parser. Here are citations from the original, unmodified XHTML 1.1 Driver, as it can be found at http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd: ..."http://www.w3.org/TR/xhtml-modularization/DTD/xhtml-inlstyle-1.mod"... ..."xhtml11-model-1.mod"... ..."http://www.w3.org/TR/xhtml-modularization/DTD/xhtml-framework-1.mod"... ..."http://www.w3.org/TR/xhtml-modularization/DTD/xhtml-text-1.mod"... ..."http://www.w3.org/TR/xhtml-modularization/DTD/xhtml-hypertext-1.mod"... ..."http://www.w3.org/TR/xhtml-modularization/DTD/xhtml-list-1.mod"... ..."http://www.w3.org/TR/xhtml-modularization/DTD/xhtml-edit-1.mod"... ..."http://www.w3.org/TR/xhtml-modularization/DTD/xhtml-bdo-1.mod"... ..."http://www.w3.org/TR/ruby/xhtml-ruby-1.mod"... ..."http://www.w3.org/TR/xhtml-modularization/DTD/xhtml-pres-1.mod"... I do not continue this list. I don't understand your argument since the driver already uses tons of absolute URLs, and this would just one other. You are right that this could cause a lot of traffic. But the solution for that is not using relative URI's, the solution for that developing XML Parsers that cache resources by their public name from e.g. <!ENTITY % PUBLIC "-//W3C//ELEMENTS XHTML Presentation 1.0//EN" "http://www.w3.org/TR/xhtml-modularization/DTD/xhtml-pres-1.mod"> or by the absolute URL of the resource (like Proxies do). No reason to scream. Greetings Christian Hujer
Received on Friday, 14 September 2001 11:41:20 UTC