- From: Al Gilman <Alfred.S.Gilman@IEEE.org>
- Date: Fri, 15 Apr 2005 11:49:55 -0400
- To: Jon Gunderson <jongund@uiuc.edu>, W3C WAI-XTECH <wai-xtech@w3.org>
- Cc: Hadi Bargi Rangin <hadi@uiuc.edu>, Jon Gunderson <jongund@uiuc.edu>, John M Slatin <john_slatin@austin.utexas.edu>, Richard Schwerdtfeger <schwer@us.ibm.com>
At 9:42 AM -0500 4/15/05, Jon Gunderson wrote: >Friday, 15 April > >2:30pm-3:30pm/18:30-19:30 UTC > >Zakim Bridge +1.617.761.6200 <tel:+1.617.761.6200>, >conference 8273 ("UAPF") > >IRC >server: irc.w3.org >port: 6665 >channel: #pf > >Agenda >1. Review current list of roles and expected behaviors .. two levels of understanding: - standard terms in standard syntax - KR in more general RDF (including the definitions of the standard terms) .. two levels of adaptation - working within CSS and ECMASCRIPT capabilities against stable content tree - page-morphers, e.g. DI servers and middleware transcoding aided by KR in RDF >2. Use of HREF to point to element IDs Do we need bug-aware workarounds? http://www.w3.org/mid/OF15B624EA.3FD6589E-ON85256FDC.0059D480-85256FDC.005A17D7@notesdev.ibm.com Additional topics we may wish to discuss: [process , early in call] scribe chair [content] - symbols to use as 'rel' values http://lists.w3.org/Archives/Member/w3c-wai-pf/2005AprJun/0021.html * back-burner issues: - appropriate use of link.rel vs. any.class (knowledge representation aspect, ontology work) [from Al] I am convinced that "the class marking is for style" is not a popular conception that we can let stand. What I mean is, we have to be getting people to put in the 'class' attribute, symbols that connote *content* semantics that is used to chose among styles, but is delivery-context, or specific styleSheet -agnostic. And to get there we probably have to demand that CSS processors honor the use of tuple-space logic in style selection. Not one class, one style. This will come up again as we look for how to inject subclasses of standard-'role' classes into down-level syntaxes to connect with browsers which are intermediate between IE on the one hand (lagging in stds uptake) and Firefox (leading in stds uptake). Browsers with an established customer base in the embedded (set top box) market are of particular interest, for example for altered text effects in the rendering of captions in digital media. - authority level of technology-specific guidance [from WAI CG] [process, late in call] ** how to be done? *who - identify other stakeholders .. groups with similar demands Device Independence, ... .. groups with related prior art IMS, UBAccess, IBM/Lotus/Noah_Mendelsson(partialUnderstanding), SW_BestPractices, ... - tech transfer targets = who has to buy it for it to deploy W3C/HTML-WG, WHAT-WG, W3C/WAI/WCAG, ...? *what - allocation of topics to deliverables - note deferred issue in CG re "how authoritative?" >Jon Gunderson, Ph.D., ATP >Director of IT Accessibility Services >Campus Information Technologies and Educational Services (CITES) >and >Coordinator of Assistive Communication and Information Technology >Disability Resources and Education Services (DRES) > >Voice: (217) 244-5870 >Fax: (217) 333-0248 > >E-mail: jongund@uiuc.edu > >WWW: http://cita.rehab.uiuc.edu/ >WWW: https://netfiles.uiuc.edu/jongund/www/
Received on Friday, 15 April 2005 15:50:16 UTC