WAI-2

Greetings Al, thankyou for your comments on behalf of the WAI PF folks on 
the content selection last call [1]. As part of this you include "Model 
best practice in examples" which states:

2. Please write the examples to model best practice.

In particular:

When setting 'class' attributes, set semantic values, not
presentation-effect-soundalike values [1]. Use Attribute Value
Templates to insert tokens into the list in the 'class' attribute
value, don't set the value and obliterate pre-existing information.

Examples should favor using content properties in these expressions
rather than just literal thresholds compared with delivery context
properties. The 'metadata for content adaptation' workshop [2] may
suggest common and educative examples of content properties to touch
on. Also the IMS Accessibility Profile [3].

Exemplify the full visibility of the expression space; do not only or
over-use the convenience functions.

Some examples should use delivery-context properties that reflect
user preferences or settings as opposed to just hardware properties.
See the IMS profile for good choices.


The DIWG assigned this comment the identifier WAI-2.

This mail documents DIWG's response to your comments.

DIWG Response
=============

In summary, DIWG agrees with this comment. The following response 
indicates the changes we plan to make. We'll respond more fully with 
details of the actual changes once they have been determined.

The example in section 7.1 is valid from a device independence standpoint. 
We need to retain it because it is relevant and represents and example of 
the simplest kind of use case. However, we will add examples that 
illustrate the additional use case of adding to a list of classes. We 
would point out that changing a class name in itself does not necessarily 
militate against good accessibility practice. An author might do that 
explicitly in order to provide a better overall experience for people 
with, for example, lower visual acuity.

The selection of the particular names for the classes in the example is 
unfortunate. It is certainly not meant to indicate the content of the CSS. 
This is the case which Tantek Celic correctly argues against in the cited 
paper. The names were meant to indicate that the author considered this to 
be a class suitable for use on a device with certain types of capability. 
In this particular case, grey referred to the device capability not the 
content of the stylesheet. In any case, we will clarify this and will use 
names less open to misinterpretation. 

In addition, to the explicit changes in the current document we are 
preparing a primer document that will provide more extensive examples of 
the use of DISelect.

[1] 
http://lists.w3.org/Archives/Public/public-diselect-editors/2005AprJun/0013.html


Regards, Roland