- From: Marcos Caceres <w3c@marcosc.com>
- Date: Thu, 8 Mar 2012 07:56:24 +0000
- To: David Lee <David.Lee@marklogic.com>
- Cc: George Cristian Bina <george@oxygenxml.com>, Jeni Tennison <jeni@jenitennison.com>, Robin Berjon <robin@berjon.com>, Noah Mendelsohn <nrm@arcanedomain.com>, "public-xml-er@w3.org Community Group" <public-xml-er@w3.org>
On Thursday, 8 March 2012 at 02:42, David Lee wrote: > Q: when you talk about "browser use case" are you talking about requiring the browsers code to change ? or is this something that can be implemented in JavaScript or as an addoon. Won't hurt to do a proof of concept in JS. Would show what is possible and various applications. > Why I ask is that if the browsers need to change I'm pretty certain this is a dead end without browser vendors being involved in this discussion. Right. > But if its something that can plugin to existing browsers then we don't need them :) Well, you would need to get this included into something like JQuery's core to have any relevance. Otherwise, yeah: you is gonna need them. In any case, it's too early to be having this discussion, but it would probably not hurt to do a litmus test on browser makers about their level of interest and asking them to actively contribute (we have Anne here already, who works for one and is fairly influential amongst the key players - which is a great start in lending this effort any sort of credibility).
Received on Thursday, 8 March 2012 07:56:55 UTC