UA as an ERT tool (was Re: minutes from today's meeting)

aloha, y'all!

in the minutes from this morning's telecon, it was stated:

DB you can consider UA's testing tools. in the future they may be doing more.
LK the ideal: techniques part of authoring tools and browsers.
WL can we suggest something to UA for UA's to perform validity checks for 
the user?
LK i don't think that has been part of the UA philosophy.

Action DB take issue to UA - should they be considering ERT techniques in 
their guidelines? have they already? include in techniques document?

the User Agent Working group has consistently taken the stance that User 
Agents are _not_ expected to fix invalid or inaccessible HTML -- that 
burden has been placed squarely upon the author's shoulders, and the Web 
Content, Authoring Tool, and ERT documents are all intended to ensure that 
the content that is exposed to the user via a user agent is (a) valid and 
(b) accessible

that being said, a simple warning, such as that which Lynx issues when it 
encounters invalid HTML

Warning! Bad HTML! Use -trace to diagnose

would be a beneficial feature for a User Agent, but as far as expecting a 
user agent to perform repairs or even an analysis of the page, isn't 
something that the User Agent Guidelines currently address, nor is it 
something that the WG expects as part of the functionality of a user agent 
qua user agent...

a user agent that also functions as an editing tool, such as Amaya, 
however, would be required to perform evaluation and repair, but only in 
editing mode...

finally, Lynx can -- by using the -trace command line switch -- be used as 
a diagnostic tool -- for more info, consult:


ACCOUNTABILITY, n.  The mother of caution.
                         -- Ambrose Bierce, _The Devil's Dictionary_
Gregory J. Rosmaita      <>
Camera Obscura           <>
VICUG NYC                <>
Read 'Em & Speak         <>

Received on Monday, 3 April 2000 13:58:32 UTC