- From: Simon St.Laurent <simonstl@simonstl.com>
- Date: Sat, 27 May 2000 19:41:10 -0400
- To: xml-uri@w3.org
At 07:31 PM 5/27/00 -0400, Clark C. Evans wrote: >Ok. As a compromise.... > > DEFINE NAMESPACE EQUIVALENCE AS A BYTE-FOR-BYTE COMPARISON > OF THE RESOURCE AS RESOLVED *AND* RETRIEVED. > > One might complain that this would require internet access or > excessive processing. However, with appropriate use of > 'expired' header, the "namespace service" could very easily > maintain a cache of these resources off line; or a even just > a hash-value. For those proceses which are *never* connected > to the internet; an alternative local, platform specific, > registry could be used. Overall, I don't see the problem. I've got to complain about that simply on grounds of the amount of infrastructure required to process a 'name'. Caching resources, which could conceivably be enormous, and which might very well not exist? Explaining that to the folks trying to process XML within PDAs and even smaller devices (which were an explicit goal of XML 1.0) sounds like a task for the extremely brave. Simon St.Laurent XML Elements of Style / XML: A Primer, 2nd Ed. Building XML Applications Inside XML DTDs: Scientific and Technical Cookies / Sharing Bandwidth http://www.simonstl.com
Received on Saturday, 27 May 2000 19:39:17 UTC