Return-Path: Delivered-To: apmail-xml-forrest-dev-archive@xml.apache.org Received: (qmail 18200 invoked by uid 500); 19 Dec 2002 12:56:04 -0000 Mailing-List: contact forrest-dev-help@xml.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: list-post: Reply-To: forrest-dev@xml.apache.org Delivered-To: mailing list forrest-dev@xml.apache.org Received: (qmail 18189 invoked from network); 19 Dec 2002 12:56:04 -0000 Received: from smtp04.iprimus.com.au (210.50.76.52) by daedalus.apache.org with SMTP; 19 Dec 2002 12:56:04 -0000 Received: from smtp02.iprimus.net.au (210.50.76.70) by smtp04.iprimus.com.au (6.7.010) id 3DF583C300140B03 for forrest-dev@xml.apache.org; Thu, 19 Dec 2002 23:56:00 +1100 Received: from localhost.localdomain ([211.26.4.7]) by smtp02.iprimus.net.au with Microsoft SMTPSVC(5.0.2195.5600); Thu, 19 Dec 2002 23:55:58 +1100 Received: from powerup.com.au (IDENT:KVJRHrgNsx8CXGIH5eT91/wjc+dfcROZ@localhost [127.0.0.1]) by localhost.localdomain (8.11.6/8.11.0) with ESMTP id gBJCuZN12491 for ; Thu, 19 Dec 2002 22:56:36 +1000 Message-ID: <3E01C203.60103@powerup.com.au> Date: Thu, 19 Dec 2002 22:56:35 +1000 From: "Peter B. West" User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.2.1) Gecko/20021130 X-Accept-Language: en-us, en MIME-Version: 1.0 To: forrest-dev@xml.apache.org Subject: Re: [PROPOSAL] DTD Versioning (Re: Should href be required on link) References: <20021215114537.GG2696@expresso.localdomain> <20021215130919.GH2696@expresso.localdomain> <1040287673.7076.7524.camel@ighp> <20021219091623.GD3095@expresso.localdomain> In-Reply-To: <20021219091623.GD3095@expresso.localdomain> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 19 Dec 2002 12:55:59.0425 (UTC) FILETIME=[FA60F310:01C2A75D] X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N Jeff Turner wrote: > On Thu, Dec 19, 2002 at 07:47:52PM +1100, David Crossley wrote: > >>Jeff Turner wrote: > > ... > >>>PUBLIC "-//APACHE//DTD Documentation//EN" "dtd/document-v11-3-1.dtd" >>>PUBLIC "-//APACHE//DTD Documentation V1//EN" "dtd/document-v11-3-1.dtd" >>>PUBLIC "-//APACHE//DTD Documentation V1.1//EN" "dtd/document-v11-3-1.dtd" >>>PUBLIC "-//APACHE//DTD Documentation V1.1.3//EN" "dtd/document-v11-3-1.dtd" >>>PUBLIC "-//APACHE//DTD Documentation V1.1.3.1//EN" "dtd/document-v11-3-1.dtd" > > ... > >>Great idea to use the OASIS catalog to manage this. >> >>How do we cope when it gets cumbersome? How many >>dtd revisions do we keep track of in the catalog >>and in cvs. >> >>Again, catalogs to the rescue. We could have a main catalog >>to declare the recent identifiers, then a separate catalog >>for the old stuff. This second one would not be used by >>default Forrest, but would be available to them if they >>need it. We already provide ways to load other catalogs. > > > Good idea. > > Might be best to wait for Steven to get back before trying this.. there > are some unresolved issues on how DTD changes are made. > > > --Jeff > > >>The secondary catalog could utilise Steven's idea of >>linking to cvs.apache.org for the systemIdentifiers. >> >>I know that we are using OASIS catalogs and entity resolver >>to avoid the dependency on a network connection to get the >>resource. However, these are way out-of-date DTDs that we >>are talking about. If users are concerned, then they can >>download a local copy of the old DTD and adjust their >>OASIS catalog. If the catalog requires a network connection, do you need it? When Keiron and Victor started using Forrest for FOP, they used view-cvs checkout URIs as the system ids to access particular versions. If the "old stuff" has system ids that directly access the files in cvs, won't the absence of a catalog public resolver trigger access through the system id? Peter -- Peter B. West pbwest@powerup.com.au http://www.powerup.com.au/~pbwest/ "Lord, to whom shall we go?"