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 85063 invoked from network); 25 Jan 2000 14:48:01 -0000 Received: from pop.systemy.it (194.20.140.28) by 63.211.145.10 with SMTP; 25 Jan 2000 14:48:01 -0000 Received: from apache.org (pv17-pri.systemy.it [194.21.255.17]) by pop.systemy.it (8.8.8/8.8.3) with ESMTP id PAA00662 for ; Tue, 25 Jan 2000 15:47:58 +0100 Message-ID: <388D8F99.32053C0B@apache.org> Date: Tue, 25 Jan 2000 12:57:13 +0100 From: Stefano Mazzocchi Organization: Apache Software Foundation X-Mailer: Mozilla 4.7 [en] (Win98; I) X-Accept-Language: en,it MIME-Version: 1.0 To: cocoon-dev@xml.apache.org Subject: Re: Cocoon Architecture [was Re: [Moving on] SAX vs. DOM part II]-Reply References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit John Morrison wrote: > > > designing a DTD is not easier than designing an API. > > Just to add my 2p worth, a DTD _is_ an API. It defines how the > data/object is accessed and iterfaces are the glue in all good OO > projects. So, IMHO, a DTD is the first thing that should be written and the > last thing to change. Totally agreed. A DTD and an API are the same thing: an interface between two worlds, a contract between two actors. -- Stefano Mazzocchi One must still have chaos in oneself to be able to give birth to a dancing star. Friedrich Nietzsche -------------------------------------------------------------------- Come to the first official Apache Software Foundation Conference! ------------------------- http://ApacheCon.Com ---------------------