- From: Vasil Rangelov <boen.robot@gmail.com>
- Date: Sun, 21 Oct 2007 14:23:59 +0300
- To: <public-xml-processing-model-comments@w3.org>
I'm not sure about the story with XSLT on that as I came late into the game, but as far as I'm aware, there has never been a standard API with which XSLT transformations should be invoked. With XSLT being implemented on the client side though, this always causes problems because of browsers having different APIs. I don't think XProc should repeat this same mistake. The WG should embrace the fact XProc MAY be implemented on the client side (though I guess that browser vendors won't be particularly encouraged for that) and create another specification (or contact the Web API WG... I'm not sure how things are made around W3C) that defines a standard API for invoking XProc pipelines. That specification should also define ECMAScript (i.e. JavaScript) bindings, encouraging ECMAScript engine vendors (i.e. browser vendors) to implement that API instead of creating their own. The XProc specification should of course remain as is now i.e. not to force implementers to use that standard API, though a reference to it could be made. Regards, Vasil Rangelov
Received on Sunday, 21 October 2007 11:24:12 UTC