Return-Path: Delivered-To: apmail-jakarta-avalon-dev-archive@apache.org Received: (qmail 48144 invoked from network); 1 Sep 2002 12:37:25 -0000 Received: from unknown (HELO nagoya.betaversion.org) (192.18.49.131) by daedalus.apache.org with SMTP; 1 Sep 2002 12:37:25 -0000 Received: (qmail 16319 invoked by uid 97); 1 Sep 2002 12:37:56 -0000 Delivered-To: qmlist-jakarta-archive-avalon-dev@jakarta.apache.org Received: (qmail 16292 invoked by uid 97); 1 Sep 2002 12:37:55 -0000 Mailing-List: contact avalon-dev-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Avalon Developers List" Reply-To: "Avalon Developers List" Delivered-To: mailing list avalon-dev@jakarta.apache.org Received: (qmail 16280 invoked by uid 98); 1 Sep 2002 12:37:55 -0000 X-Antivirus: nagoya (v4218 created Aug 14 2002) Message-ID: <3D7209D2.7040205@apache.org> Date: Sun, 01 Sep 2002 14:36:34 +0200 From: Nicola Ken Barozzi Reply-To: nicolaken@apache.org User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.1) Gecko/20020826 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Avalon Developers List Subject: Re: DTD locations? References: <200209011605.51547.peter@apache.org> <3D71FC79.4080101@apache.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N Stephen McConnell wrote: > > > Today every DTD is relative to package. Which is PITA for some dtds. > Isn't is the packages responsibility to publish it? yes... > E.g. > http://jakarta.apache.org/avalon/pheonix/dtd/... for something related > to Phoneix, or http://jakarta.apache.org/avalon/excalibur/meta/dtd/ for > soemthing relative to the Excalibur Meta Model Project. There isn't any > requirement for a pool of DTDs as such. There is. As I have clearly showed, there is no thechnical reason why general DTDs such as the meta descriptors cannot be standardized upon. If a DTD is generic enough, it should be standard. Keeping all DTDs in one place ensures that others will see them promptly and collaborate on them. So I'm +1 to have all DTDs that are common in http://jakarta.apache.org/avalon/dtds/Foo.dtd All DTDs that pertain *solely* to specific implementations go in http://jakarta.apache.org/avalon/dtds/imp-name/Foo.dtd For example, the xinfo DTD will go in avalon/dtd, while the extension dtd goes into avalon/extension/xt.dtd > Peter Donald wrote: > >> Hi, >> >> We got any standard for locating DTDs? Currently I have been storing >> them at locations like >> >> http://jakarta.apache.org/avalon/Foo.dtd >> http://jakarta.apache.org/phoenix/Bar.dtd >> etc. >> >> However I expect to see more of these little dtds arise over time. >> Phoenix alone may be looking a separate DTDs for * 2 different >> component models >> * role descriptors >> * manifest descriptors >> * assembly descriptors >> * classloader descriptors >> * management descriptors >> * security descriptors? >> >> Is there a preferred location for all of these? Is >> http://jakarta.apache.org/avalon/Foo.dtd good enough and we live with >> the fact that there may be 15-20 sitting there. Or do we chuck them in >> something like >> >> http://jakarta.apache.org/avalon/dtds/Foo.dtd -- Nicola Ken Barozzi nicolaken@apache.org - verba volant, scripta manent - (discussions get forgotten, just code remains) --------------------------------------------------------------------- -- To unsubscribe, e-mail: For additional commands, e-mail: