W3C home > Mailing lists > Public > w3c-wai-gl@w3.org > April to June 2006

#LC-486 Proposed Resolution

From: Gregg Vanderheiden <gv@trace.wisc.edu>
Date: Tue, 16 May 2006 15:04:10 -0500
To: <w3c-wai-gl@w3.org>
Message-ID: <006a01c67923$e8cbe290$ee8cfea9@NC6000BAK>
#LC-486

Chris Ridpath  5/3/2006  

W2       4.1.1                 

TE        

 


Comment 


The term  "parsed unambiguously" is ambiguous.

     Parsing requires a set of rules and without those rules the parsing
result may be meaningless.  For example, an HTML file may be parsed using
the rule "by line". It may also be parsed using the rule "by sentence and
word". This parsing will produce an unambiguous tree structure but has no
effect on accessibility. I believe the intent of the SC is to include the
set of rules (e.g. DTD or schema) that has an effect on accessibility."

 


Proposed Change


"Include text that specifies the set of rules needed to parse the document.
Example:

  "Web units or authored components can be parsed unambiguously using the
specification that affects accessibility...". In the techniques document you
can specify the appropriate rules such as in HTML use one of the standard
DTDs."      

 

 


Proposed Resolution - from Team A


Accept partial

If the DTD would be required to parse unambiguously, then it is already
required by our current language.  If it is not, then it would not be
required and our language does not require it.     

No change to document required. 


Gregg

------------------------

Gregg C Vanderheiden Ph.D. 
Professor - Depts of Ind. Engr. & BioMed Engr.
Director - Trace R & D Center 
University of Wisconsin-Madison 
< <http://trace.wisc.edu/> http://trace.wisc.edu/> FAX 608/262-8848  

The Player for my DSS sound file is at  <http://tinyurl.com/dho6b>
http://tinyurl.com/dho6b 

 <http://trace.wisc.edu:8080/mailman/listinfo/>  

 

 
Received on Tuesday, 16 May 2006 20:29:11 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 7 December 2009 10:47:46 GMT