Re: class inheretance (Was: Future of HTML)

Liam Quinn (liam@htmlhelp.com)
Thu, 26 Mar 1998 22:00:43 -0500


Message-Id: <3.0.5.32.19980326220043.00ad63c0@undergrad.math.uwaterloo.ca>
Date: Thu, 26 Mar 1998 22:00:43 -0500
To: Dataweaver <traveler@io.com>
From: Liam Quinn <liam@htmlhelp.com>
Cc: www-html@w3.org
In-Reply-To: <Pine.BSI.3.96.980326181111.19039C-100000@xanadu.io.com>
Subject: Re: class inheretance (Was: Future of HTML)

At 06:39 PM 26/03/98 -0600, Dataweaver wrote:
>This is strictly hypothetical, and I'm not at all sure that it would be
>either practical or desirable to implement, but I'm thinking along the
>lines of a new element, intended strictly for use in the header, with the
>sole purpose of specifying relationships among various classes in the
>document (I do _not_ like this approach, but I can't think of a better one
>right now; if anyone else can, I'm all ears...).  Something along the
>lines of:
>
><RELATION class="date" parent="datetime">
><RELATION class="time" parent="datetime">
>
>At that point, anything that acts on elements with the "datetime" class
>would also act on elements with either the "date" class or the "time"
>class, or both, while anything that acts specifically on elements with the
>"date" class would have no effect on elements with the "datetime" class or
>the "time" class (assuming that they also don't have the "date" class, of
>course...).  

Wouldn't normal HTML classes do the job?

<SPAN CLASS=date>A date</SPAN>
<SPAN CLASS=time>A time</SPAN>
<SPAN CLASS="date time">A date and a time</SPAN>

Remember that the CLASS attribute can take multiple classes.

--
Liam Quinn
Web Design Group            Enhanced Designs, Web Site Development
http://www.htmlhelp.com/    http://enhanced-designs.com/