Return-Path: Mailing-List: contact cocoon-dev-help@xml.apache.org; run by ezmlm Delivered-To: mailing list cocoon-dev@xml.apache.org Received: (qmail 53590 invoked from network); 3 Aug 2000 23:20:22 -0000 Received: from snoopy.apana.org.au (202.12.87.129) by locus.apache.org with SMTP; 3 Aug 2000 23:20:22 -0000 Received: by snoopy.apana.org.au (Postfix, from userid 1003) id 8619B30079; Fri, 4 Aug 2000 09:20:15 +1000 (EST) To: Cocoon dev Subject: Re: [Cocoon Devel]DTD PUBLIC ID resolution References: From: Brian May X-Home-Page: http://snoopy.apana.org.au/~bam/ Date: 04 Aug 2000 09:20:15 +1000 In-Reply-To: Hans Ulrich Niedermann's message of "25 Jul 2000 16:43:46 +0200" Message-ID: <84em46exu8.fsf@snoopy.apana.org.au> Lines: 30 User-Agent: Gnus/5.0807 (Gnus v5.8.7) XEmacs/21.1 (Capitol Reef) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Spam-Rating: locus.apache.org 1.6.2 0/1000/N >>>>> "Hans" == Hans Ulrich Niedermann writes: Hans> Hi, I'd like to have a mechanism that maps some known PUBLIC Hans> IDs from the declaration to the corresponding Hans> local URIs (similar to SGML catalog files). This would allow I am not familiar with SGML catalog files, so may have misunderstood something... Hans> one to write XML files with the "canonical" URI for the used Hans> DTDs and still use a local copy for validation and default Hans> value gathering, which increases both reliability and speed. Is it or ??? Hans> Do you think such a mechanism makes sense? Has anybody seen Hans> such a thing implemented yet? Where could/should such a Hans> thing be hooked into the C2 processing chain? Where and how Hans> should the configuration, i.e. the mapping from PUBLIC to Hans> SYSTEM be stored? Personally, I have modified the DOCTYPE specs to point to the local copy of the DTD, using a relative path. Probably not a good idea for distributing copies of the XML document elsewhere.... Are there any other advantages? -- Brian May