- From: Jim Ley <jim.ley@gmail.com>
- Date: Mon, 19 Jul 2004 22:23:40 +0100
- To: Richard Schwerdtfeger <schwer@us.ibm.com>
- Cc: Becky Gibson <gibsonb@us.ibm.com>, Jon Gunderson <jongund@uiuc.edu>, Liddy Nevile <liddy.nevile@motile.net>, Lisa Seeman <lisa@ubaccess.com>, w3c-wai-gl@w3.org, w3c-wai-pf@w3.org, w3c-wai-pf-request@w3.org, wai-gl@w3c.org
Richard Schwerdtfeger <schwer@us.ibm.com> >Browsers need to map RDF to an API to describe how to interact > with an object. This requires a good RDF parser. Fortunately there are a lot about, and if worse comes to the worst there are acceptable ones implementable in javascript. >Furthermore, it is becoming less likely that transcoding >will be done in the middleware to process it since more >often than not the UI will be constructed on the client. Which means an RDF aware AT will have a lot better chance than they would with a pure javascript solution such as I end up developing all too much in the intranet world. Jim.
Received on Monday, 19 July 2004 17:24:20 UTC