Return-Path: Delivered-To: apmail-xml-forrest-dev-archive@www.apache.org Received: (qmail 39863 invoked from network); 5 May 2004 03:22:41 -0000 Received: from daedalus.apache.org (HELO mail.apache.org) (208.185.179.12) by minotaur-2.apache.org with SMTP; 5 May 2004 03:22:41 -0000 Received: (qmail 94602 invoked by uid 500); 5 May 2004 03:22:21 -0000 Delivered-To: apmail-xml-forrest-dev-archive@xml.apache.org Received: (qmail 94394 invoked by uid 500); 5 May 2004 03:22:20 -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 94375 invoked from network); 5 May 2004 03:22:20 -0000 Received: from unknown (HELO indexgeo.net) (65.77.211.93) by daedalus.apache.org with SMTP; 5 May 2004 03:22:20 -0000 Received: from [192.168.1.100] (dsl-109.227.240.220.dsl.comindico.com.au [220.240.227.109]) (authenticated bits=0) by www2.kc.aoindustries.com (8.12.9-20030917/8.12.9) with ESMTP id i453MRKc021467 for ; Tue, 4 May 2004 22:22:29 -0500 Subject: Re: [question] Why is group-logo required in the skinconf? From: David Crossley To: forrest-dev@xml.apache.org In-Reply-To: <000001c4324d$a0a2c930$6401a8c0@prometheus> References: <000001c4324d$a0a2c930$6401a8c0@prometheus> Content-Type: text/plain Organization: Message-Id: <1083727346.2082.46.camel@ighp> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.2.2 (1.2.2-5) Date: 05 May 2004 13:22:26 +1000 Content-Transfer-Encoding: 7bit X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N Brian S. Hayes wrote: > Why is the group-logo required in the skin configuration > (skinconfig-v06.dtd)? The comment in the default skinconf.xml states > "optional group logo." Based on this comment, I would think that you could > safely delete or comment out, the following elements: group-name, > group-description, group-url, and group-logo. As it is now, you cannot > comment out group-logo (if you do, validation will fail). > > I looked through about six or seven emails (of many) in the archives; but, I > did not see the reasoning. You are right. Thanks, fixed now. This DTD was recently created by extracting the internal DTD from the skinconf.xml and that error was introduced. I also noticed that the parts of the project-logo were once mandatory and are now optional. Not sure why. --David