W3C home > Mailing lists > Public > w3c-wai-ua@w3.org > October to December 1999

Re: WD-WAI-USERAGENT-19991105 review

From: Håkon Wium Lie <howcome@opera.com>
Date: Mon, 6 Dec 1999 01:18:20 +0100 (Romance Standard Time)
Message-ID: <14411.204.130000.121739@ETTE>
To: Ian Jacobs <ij@w3.org>
Cc: w3c-wai-ua@w3.org
Also sprach Ian Jacobs:

 > > I would suggest reversing the priorties here -- it's more important
 > > that the UA supports (say) single-key functionality than that it
 > > supports an API for changing the UI.
 > 
 > Added as issue 155.
 > http://cmos-eng.rehab.uiuc.edu/ua-issues/issues-linear.html#155

Thanks!

 > >  > 5.6 Conform to W3C Document Object Model specifications and export
 > >  > interfaces defined by those specifications. [Priority 1]
 > > 
 > > Adding support for DOM effectively turns a browser into an editor.
 > > This is often beneficial, but in memory-constrained enviroments it is
 > > often impossible. By making this Priority 1, a whole segment of UAs
 > > will fail conformance and might therefore pay less attention to the
 > > Guidelines in general. I suggest changing it to Priority 2 and limit
 > > the requirement fo the read (i.e. not write) portions of the DOM.
 > 
 > Added as issue 156
 > http://cmos-eng.rehab.uiuc.edu/ua-issues/issues-linear.html#156

Thanks!

 > >  > 6.2 Conform to W3C specifications when they
 > >  > are appropriate for a task. [Priority 2]
 > >  > For instance, for markup, implement [HTML40] or [XML]. For style
 > >  > sheets, implement [CSS1], [CSS2], or XSL.
 > > 
 > > XSL is not a W3C Recommendation and although it may turn into one some
 > > day, it is bad practice to include forward references in a
 > > specification. 
 > 
 > We have an XSLT reference in our list of references, but not reference
 > to XSL.

Right, but you mention "XSL" in the text. I suggest removing that.

 > I'd recommend that we include a reference to XSL (not XSLT)
 > but clearly indicate that XSL style is only a Working Draft.

I disagree, I don't think the normative text should contain references
to non-normative specifications. 

An underlying issue here is the accessibility problems associated with
XSL [1].

[1] http://www.opera.com/people/howcome/1999/foch.html

Regards,

-h&kon

Chief Technology Officer                                Opera Software
Håkon Wium Lie                     http://www.opera.com/people/howcome
howcome@opera.com                                gets you there faster
Received on Sunday, 5 December 1999 19:18:51 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 14:49:25 UTC