RE: 2.4.2 Issues

<john>
Anyone want to take an action to review the definition of "perceivable
unit" and send a note to the list by Monday (6 February)?
</john>

This is in respect to the proposal to change to the text of SC 2.4.2 and 
to use perceivable unit rather then delivery unit.  I don't think 
perceivable unit is what we want here.  A delivery unit may be rendered as 
multiple perceivable units but the URI is to the delivery unit.  It is the 
delivery units which must be located. 

I also have a tweak to the proposal.  I find it odd to talk about locating 
delivery units and then referring to content of delivery units.   Here is 
the current, David's proposal, and then two slightly different proposals 
from me.  My preference is for the second proposal. 
<current>
> 2.4.2 More than one way is available to locate content within a set of 
delivery units where content is not the result of, or a step in, a process 
or task. </current>

> <proposed>
> 2.4.2 More than one way is available to locate each delivery unit within 
a set of delivery units where the content of the delivery unit is not the 
result of, or a step in, a process or task.
> </proposed>

<becky proposal 1>
2.4.2 More than one way is available to locate each delivery unit within a 
set of delivery units when the delivery unit is not the result of, or  a 
step in, a process or task.
</becky proposal 1>

This proposal uses an exception - which I think is more consistent with 
other SC.
<becky proposal 2>
2.4.2 More than one was is available to locate each delivery unit within a 
set of delivery units except when the delivery unit is the result of, or a 
step in, a process or task.
</becky proposal 2>

Becky Gibson
Web Accessibility Architect
                                                       
IBM Emerging Internet Technologies
5 Technology Park Drive
Westford, MA 01886
Voice: 978 399-6101; t/l 333-6101
Email: gibsonb@us.ibm.com

Received on Thursday, 2 February 2006 19:49:02 UTC