Return-Path: Delivered-To: apmail-forrest-dev-archive@www.apache.org Received: (qmail 2977 invoked from network); 29 Jun 2005 06:43:57 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 29 Jun 2005 06:43:57 -0000 Received: (qmail 71450 invoked by uid 500); 29 Jun 2005 06:43:56 -0000 Delivered-To: apmail-forrest-dev-archive@forrest.apache.org Received: (qmail 71389 invoked by uid 500); 29 Jun 2005 06:43:55 -0000 Mailing-List: contact dev-help@forrest.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: Reply-To: dev@forrest.apache.org List-Id: Delivered-To: mailing list dev@forrest.apache.org Received: (qmail 71370 invoked by uid 99); 29 Jun 2005 06:43:55 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 28 Jun 2005 23:43:55 -0700 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received-SPF: pass (asf.osuosl.org: domain of cjxaf-forrest-dev-1@m.gmane.org designates 80.91.229.2 as permitted sender) Received: from [80.91.229.2] (HELO ciao.gmane.org) (80.91.229.2) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 28 Jun 2005 23:43:54 -0700 Received: from list by ciao.gmane.org with local (Exim 4.43) id 1DnWB8-0006Mz-1i for dev@forrest.apache.org; Wed, 29 Jun 2005 08:36:10 +0200 Received: from host190-154.pool80204.interbusiness.it ([80.204.154.190]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Wed, 29 Jun 2005 08:36:10 +0200 Received: from nicolaken by host190-154.pool80204.interbusiness.it with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Wed, 29 Jun 2005 08:36:10 +0200 X-Injected-Via-Gmane: http://gmane.org/ To: dev@forrest.apache.org From: Nicola Ken Barozzi Subject: Re: Eclipse based site.xml editor (Re: Requesting Comments on Eclipse Plugin Deliverables) Date: Wed, 29 Jun 2005 08:43:02 +0200 Lines: 51 Message-ID: References: <42BFE47D.2040709@apache.org> <42C00856.1010108@peppersauce.org> <1119884730.9094.40.camel@localhost.localdomain> <20050628004614.GA5548@igg.indexgeo.com.au> <42C1103A.8090206@apache.org> <42C13D60.7000400@peppersauce.org> <42C14304.8050009@apache.org> <42C1800C.3000000@peppersauce.org> <42C184DF.7080407@apache.org> <42C19199.7020407@apache.org> <42C19304.7000503@apache.org> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Complaints-To: usenet@sea.gmane.org X-Gmane-NNTP-Posting-Host: host190-154.pool80204.interbusiness.it User-Agent: Mozilla Thunderbird 1.0.2 (Windows/20050317) X-Accept-Language: en-us, en In-Reply-To: <42C19304.7000503@apache.org> Sender: news X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N Ross Gardler wrote: > Gregor J. Rothfuss wrote: > >> Ross Gardler wrote: >> >>> Well, in that case I would avoid EMF for this instance and we need >>> not consider whether site.xml is to have a DTD or not. Just a tree >>> editor with configurable properties on each node will do just fine. >> >> the completely free-form site.xml where each node can have pretty much >> any element name doesn't lend itself to a schema / DTD easily. maybe >> it would be useful to revisit that decision and switch to a system >> where you have >> >> >> >> this would also enforce that each node has a unique id and is >> therefore addressable by site:uniqueid >> >> WDYT? > > I think we discussed this to death already ;-) > > There are good reasons for us not doing that (all related to the site: > protocol if I remember correctly). There have been a few proposals for a > DTD but none have had a strong enough use case to warrant us disabling > the site: protocol. The current practice is that if we need a valid site > structure document then we simply create a internal plugin (like the > IMSManifest plugin) for it. > > Of course, no such decision is ever final. If someone wants to go > through the archives and make a new proposal we'll consider it. Ok, here it comes :-) One thing is the *internal* representation, that must be kept as now because of the way the site: protocol works. But this does not mean that we cannot decide to make the _default_ external representation be different. Personally, I would support we change the default external representation to something akin to what Gregor proposes, and in particular the same as the Lenya one. I would be even more supportive if Lenya and Cocoon adopt the Maven one, so that we would have a single format for all these projects. -- Nicola Ken Barozzi nicolaken@apache.org - verba volant, scripta manent - (discussions get forgotten, just code remains) ---------------------------------------------------------------------