W3C home > Mailing lists > Public > w3c-wai-gl@w3.org > January to March 2004

RE: FW: UBER 3.1 proposal Improved

From: Gregg Vanderheiden <gv@trace.wisc.edu>
Date: Thu, 26 Feb 2004 10:00:59 -0600
To: 'Wendy A Chisholm' <wendy@w3.org>, w3c-wai-gl@w3.org
Message-id: <0HTP00J9V8HL1D@smtp3.doit.wisc.edu>

Yes -- for html that is the kind of thing.

It has to allow cascading -- which could be done by order. 

The other question would be whether the glossary had to be machine
readable...  (so the word could be found).



 
Gregg

 -- ------------------------------ 
Gregg C Vanderheiden Ph.D. 
Professor - Ind. Engr. & BioMed Engr.
Director - Trace R & D Center 
University of Wisconsin-Madison 


-----Original Message-----
From: Wendy A Chisholm [mailto:wendy@w3.org] 
Sent: Thursday, February 26, 2004 9:54 AM
To: Gregg Vanderheiden; w3c-wai-gl@w3.org
Subject: Re: FW: UBER 3.1 proposal Improved

At 01:20 AM 2/22/2004, Gregg Vanderheiden wrote:


>
>The following text  for levels 1 and 2  was the result of the working 
>group call last Thursday.
>
>

snip.

>One technique that is being explored is the use of the cascading 
>dictionaries directly associated with the content.
>
>NOTE:  This provision is dependent on the definition of a standard way to 
>associate dictionaries and the availability of on-line dictionaries.

Would the glossary link type satisfy this? 
http://www.w3.org/TR/html401/types.html#type-links
<link rel="glossary" href="glossary1.html"/>


-- 
wendy a chisholm
world wide web consortium
web accessibility initiative
http://www.w3.org/WAI/
/--  
Received on Thursday, 26 February 2004 11:00:58 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 5 February 2014 07:17:55 UTC