Mailing-List: contact commons-dev-help@xml.apache.org; run by ezmlm
Precedence: bulk
To: commons-dev@xml.apache.org
Subject: Re: New resolver all checked in
From: Norman Walsh <ndw@nwalsh.com>
Date: Sun, 16 Feb 2003 12:05:57 -0500
In-Reply-To: <3E00F25C.6020707@uiowa.edu> (Brian Smith's message of "Wed, 18
 Dec 2002 16:10:36 -0600")
Message-ID: <87of5ctatm.fsf@nwalsh.com>
User-Agent: Gnus/5.090015 (Oort Gnus v0.15) Emacs/21.1
References: 
 <OF4647B8C4.2982F10C-ON85256C93.0051E35F-85256C93.00535DDB@lotus.com>
	<3E00F25C.6020707@uiowa.edu>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

/ Brian Smith <brian-l-smith@uiowa.edu> was heard to say:
| Shane Curcuru/CAM/Lotus wrote:
|>> (b) The resolver library does not have any special support for
|>> resolving the public ID for the DTD for XML catalogs. Thus, if you
|>> don't put that DTD in your local personal system-wide catalog, the
|>> catalog resolver will attempt to retrieve the DTD from the OASIS
|>> website. Again, it is seems very difficult to override this in a
|>> client application. Probably the resolver library should include
|>> the OASIS XML Catalog DTD inside its
|>
|>>own JAR file and resolve this public ID specially.
|> Here I'm not so sure.  I'd defer to a larger array of cataloging
|> experts: in particular, does this DTD at OASIS change
|> ever/frequently?  If so, we
|
| It is my understanding that any changes to the DTD mean that a new
| System ID and Public ID must (should) be assigned. Also, if the DTD
| changes "silently" in any way that is semantically significant then
| the resolver library would likely no longer work with documents
| conforming to the new DTD anyway.

The DTD isn't going to change without new public and system IDs. In fact,
I don't think it's going to change.

                                        Be seeing you,
                                          norm

- -- 
Norman.Walsh@Sun.COM    | The years teach us much which the days never
XML Standards Architect | knew.--Emerson
Web Tech. and Standards |
Sun Microsystems, Inc.  | 
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: Processed by Mailcrypt 3.5.7 <http://mailcrypt.sourceforge.net/>

iD8DBQE+T8T1OyltUcwYWjsRAqnJAJ46x5Yr0ot/Yns5v/QMz1ZcgMGXaQCdFk42
LeX7nvx+XOGxt1SgwhtWco0=
=MEMC
-----END PGP SIGNATURE-----