Re: WAI class use, attribute quoting, and name capitalization

What would you think of using RDF to indicate

1. that the class is informationally relevent for the user  (i.e. more than 
just appearance)
2. A description of what the class means.

If we want to push this much further it's a matter for PF.

Although it is a candidate for inclusion in EARL.

I had once suggested adding at "alt" attribute to style sheets to convey 
the meaning of a class, but it ran afoul of the philosophy that style 
sheets should contain no content.

At 03:28 PM 4/2/01 +0100, Sean B. Palmer wrote:

>Oh please no! Using classes to identify semantics when there is no
>strict mechanism for doing so? Classes may well be there to group
>elements of a certain type, but this is a very short first party
>assertion in that it groups elements of a certain type without
>providing any reason of why these elements are grouped. If the class
>system is used otherwise, then you are extending the XHTML 1.0
>specification; you should be using Modularization of XHTML [1]
>instead. Pragmatically, given the limitations of XHTML 1.0 in
>providing annotations (or even links to annotations), there's not
>really much we can do for classes, except perhaps to use URIs as class
>attribute values [2].
>Kindest Regards,
>Sean B. Palmer
>@prefix : <> .
>:Sean :hasHomepage <> .

Leonard R. Kasday, Ph.D.
Institute on Disabilities/UAP and Dept. of Electrical Engineering at Temple 
(215) 204-2247 (voice)                 (800) 750-7428 (TTY)

Chair, W3C Web Accessibility Initiative Evaluation and Repair Tools Group

The WAVE web page accessibility evaluation assistant:

Received on Monday, 2 April 2001 11:00:10 UTC