Mailing-List: contact forrest-dev-help@xml.apache.org; run by ezmlm
Precedence: bulk
Reply-To: forrest-dev@xml.apache.org
Message-ID: <403ADC0D.7040001@apache.org>
Date: Tue, 24 Feb 2004 01:07:25 -0400
From: Ross Gardler <rgardler@apache.org>
Organization: saafe.org
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US;
 rv:1.4) Gecko/20030624 Netscape/7.1
MIME-Version: 1.0
To: forrest-dev@xml.apache.org
Subject: Re: Philosophy: Why id but no class?
References: <403ACACF.5040208@bl.com>
In-Reply-To: <403ACACF.5040208@bl.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit

Moshe Yudkowsky wrote:
> The DTD for documents includes the "id" attribute, but does not allow 
> "class" attributes. I was wondering why this is the case; I'd think that 
> one is just as "dangerous" to the unity of the UI as the other, and 
> certainly I know I find find class important for certain table I have in 
> mind.

A future version of Forrest will be moving to a subset of XHTML2 as the 
intermediate format (replacing Document V1.2, which will become a source 
format to maintain backward compatability). When this happens we will 
have class on all elements.

In order to facilitate this we are migrating Document 1.2 towards XHTML, 
the addition of the class attribute to all elements os one of the things 
we have agreed is necessary. Feel free to provide a patch for some or 
all elements and skins if you have the itch right now.

Ross