FW: The next few weeks for me,

this is the mail I've talked about jump to the part from Tim Boland
Cheers
Helle

Helle Bjarnø
Visual Impairment Knowledge Centre
Rymarksvej 1, 2900 Hellerup, Denmark
Phone: +45 39 46 01 01
fax: +45 39 61 94 14
e-mail hbj@visinfo.dk
Direct phone: +45 39 46 01 04
www.visinfo.dk
www.euroaccessibility.org 


-----Original Message-----
From: Jan Richards [mailto:jan.richards@utoronto.ca] 
Sent: Sunday, November 14, 2004 7:11 AM
To: w3c-wai-au@w3.org
Subject: The next few weeks for me,


Hi,

Just a note that my parental leave will be starting early(!!!).

...so I won't be active on the list or calls for a few weeks.

Must sleep...:)
-Jan


-- 
Jan Richards, User Interface Design Specialist 
Adaptive Technology Resource Centre (ATRC), University of Toronto 

  Email: jan.richards@utoronto.ca 
  Web:   http://jan.atrc.utoronto.ca
  Phone: 416-946-7060 
  Fax:   416-971-2896


Quoting Tim Boland <frederick.boland@nist.gov>:

> 
> The following terms in the WAI Glossary, at:
> 
> http://www.w3.org/WAI/GL/Glossary/printable.html
> 
> (a) may have overlap with similar terms in the ATAG2.0 Glossary
>   (3 Nov 2004 draft) with respect to definitions, and (b) are
> defined by sources other than from ATAG:
> 
> 
> 1. "accessible" - WCAG10, WCAG20
> 2. "activate" - UAAG10(normative); "active element" - SVG10, "active 
> element" - UAAG10
> 3. "alert" - UAAG10(normative)
> 4. "alternative equivalents for content" - UAAG10; ("text equivalent" - 
> WCAG10, WCAG20?)
> 5. "attribute" - UAAG10(normative); "attribute" - WS-GLOSSARY
> 6. "audio description", "auditory description" - UAAG10; "audio 
> descriptions" - WCAG20?
> 7. "author styles" - UAAG10(normative)
> 8. "captions" - UAAG10(normative); "captions" - WCAG20?
> 9. "configure and control" - UAAG10(normative)
> 10. "content" - UAAG10(normative); "content" - WCAG20?
> 11. "device-independent" - WCAG10, WCAG20; "device independence" - 
> UAAG10(normative)
> 12. "document" - CC-PP; "document content, structure, and presentation" - 
> WCAG10, WCAG20
> 13. "documentation" - UAAG10(normative)
> 14. "element,element type" - UAAG10(normative); "element" - WCAG10,
WCAG20;
>   "element" - CSS10, CSS20; "element" - XML10, XHTML10
> 15. "end user" - WS-GLOSSARY
> 16. "equivalent" - WCAG10, WCAG20; "equivalent(alternatives)(for content)"

> - UAAG10
> 17. "informative" - UAAG10(normative)
> 18. "markup" - WCAG10, WCAG20
> 19. "normative" - UAAG10(normative)
> 20. "objects" - WCAG10, WCAG20
> 21. "prompt" - UAAG10(normative)
> 22. "property" - SVG10; "properties, values, defaults" - UAAG10(normative)
> 23. "repair content, repair text" - UAAG10(normative)
> 24. "transform gracefully" - WCAG10, WCAG20?; "transformation filter" - 
> WCAG10, WCAG20;
>   "transformation matrix" - SVG10
> 25. "user agent" - WCAG10, WCAG20; "user agent" - UAAG10(normative); "user

> agent" - P3P10
> 26. "view, viewport" - UAAG10(normative); "viewport" - SVG10
> 
> 
> NOTE: The UAAG terms with definitions are "normative" in most 
> instances.  Also, some of the
> terms and definitions in the WAI Glossary may be somewhat "dated" (dates
of
> 
> entry are
> explicitly given), so the terms and/or definitions may need updating or 
> obsoleting?
> 
> Terms (other than those listed previously) in the WAI Glossary either 
> already have ATAG as
>   a source, or are not found in the ATAG2.0 Glossary.  It might be worth 
> examining the
>   previously-listed terms with definitions to make sure we're consistent
if
> 
> we're supposed to
>   be, or maybe to reference these terms/definitions in certain instances
if
> 
> appropriate?
> If our terms/definitions are meant to be different, eventually we may want

> to contribute
>   our terms/definitions to the WAI Glossary?
> 
> I believe there is also a PFWG glossary, but I haven't looked at it yet if

> there is one..
> 
> 
> 
> 
> --------------------------------------------
> 
> 
> 
> 
> (extremely minor point) - the ordering of some of the terms in the current

> ATAG2.0 glossary
>   is not strictly alphabetic - examples:  "accessible web content" comes 
> before "accessible
>   authoring interface", and "transcript" comes before "techniques"
> 
> 
> 
> 
> ----------------------------------------------
> 
> 
> 
> 
> NOTE: I will be out of town and probably unavailable via email Sun Nov 14
-
> 
> Tues Nov 16,
>   so I must send regrets for the AUWG teleconference Monday Nov 15.
> 
> 
> 
> 
> Thanks and best wishes,
> Tim Boland NIST
> 
> 
> 
> PS - personal note: I think that using consistent terminology and 
> definitions across
>   the WAI working groups to the maximum extent possible and appropriate 
> reinforces again
>   to the public that "WAI has its act together".
>   
> 
> 
>

Received on Monday, 15 November 2004 15:54:54 UTC