- From: Ashok Malhotra <ashokma@microsoft.com>
- Date: Wed, 15 Oct 2003 08:12:11 -0700
- To: "Charles McCathieNevile" <charles@sidar.org>, <tvraman@almaden.ibm.com>
- Cc: <public-qt-comments@w3.org>, <w3c-wai-pf@w3.org>
Charles, Raman: Thank you for your comments. We have added an indented table that reproduces the information in the figure. We have also, as you requested, retained the indented lists of types that precede some of the sections. I trust you will find this addresses your concerns. Please comment on the next version of the document if you have further suggestions for improvement. All the best, Ashok > -----Original Message----- > From: public-qt-comments-request@w3.org [mailto:public-qt-comments- > request@w3.org] On Behalf Of Charles McCathieNevile > Sent: Friday, June 13, 2003 10:23 AM > To: tvraman@almaden.ibm.com > Cc: public-qt-comments@w3.org; w3c-wai-pf@w3.org > Subject: Re: XPath/Xquery Operations And Function Specification: > > > Err presumably you mean draft comment. > > Anyway, yes, it seems a pretty obviously sensible one for us to make > officially. > > chaals > > On Friday, Jun 13, 2003, at 19:20 Europe/Zurich, T. V. Raman wrote: > > > > > I sent this privately to one of the editors, but am sending it > > here as an official last call comment from the WAI so it gets > > addressed. > > > > > > Also, in his reply Ashok indicated to me that the group was > > thinking of getting rid of the nested HTML lists that show type > > hierarchy relations in later sections, please do not do this as > > it would make your specification document even more inaccessible. > > > > Finally WAI --we may want to point the QA group at these kinds of > > issues where type hierarchy and other technical information get > > buried in a diagram in a specification document, I think that is > > just a bad idea in general. > > > > > > > > Details: > > > > section 1.2 contains a diagram for the type hierarchy --but fails > > to spell out the hierarchy outside of the diagram. > > > > It does pretend to be a good access citizen in that it explains > > the notation used in the diagram; however this is inadequate for > > someone wishing to get at the content. > > > > Could you: > > > > A) provide me witht he missing content, > > and > > B) ensure that the next working draft fixes the problem? > > > > What I'm looking for is a textual summary of the type hierarchy > > --set of nested html lists would do fine. > > > > > > > > --Raman > > > > -- > > Best Regards, > > --raman > > ------------------------------------------------------------ > > T. V. Raman: PhD (Cornell University) > > IBM Research: Human Language Technologies > > Architect: Conversational And Multimodal WWW Standards > > Phone: 1 (408) 927 2608 T-Line 457-2608 > > Fax: 1 (408) 927 3012 Cell: 1 650 799 5724 > > Email: tvraman@us.ibm.com > > WWW: http://www.almaden.ibm.com/cs/people/tvraman > > AIM: TVRaman > > GPG: > > http://www.almaden.ibm.com/cs/people/tvraman/raman-almaden.asc > > Snail: IBM Almaden Research Center, > > 650 Harry Road > > San Jose 95120 > > > > > -- > Charles McCathieNevile Fundación Sidar > charles@sidar.org http://www.sidar.org > >
Received on Wednesday, 15 October 2003 11:13:31 UTC