[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Traffic Analysis and Namespace Dereferencing
- From: Norman Walsh <firstname.lastname@example.org>
- To: email@example.com
- Date: Mon, 08 Jan 2001 14:47:06 -0500
/ Miles Sabin <MSabin@interx.com> was heard to say:
| There are already many production-side systems which validate,
| and I'm sure there'll be many more in the future. Where the input
| docs can't be assumed up front to be valid and where DTDs/
| schemas are cached locally, this doesn't seem like such a crime.
The local caching seems to be part of the problem. I make extensive
use of OASIS Catalogs on my own system to map public identifers (and a
few system identifiers) to local copies.
The OASIS Entity Resolution Technical Committee is currently working
on a revision to OASIS Catalogs.
I'd like to see other systems (like XSLT processors and Schema
processors) extended so that they passed all their URIs through a
resolver as well.
The other alternative is to design some sort of caching system (like
wwwoffle) to do the caching work for you. But this generally seems to
require vastly more technical skill on the part of the person setting
up the system. I know lots of people who could be trained to edit a
catalog file that would find setting up a proxy server way too
Be seeing you,
Norman.Walsh@East.Sun.COM | The stone fell on the pitcher? Woe to the
XML Technology Center | pitcher. The pitcher fell on the stone? Woe
Sun Microsystems, Inc. | to the pitcher.--Rabbinic Saying