& XSLT http://bugs.webkit.org/show_bug.cgi?id=4079

In particular the following series of questions posed in January of 2006  
seem to be what's holding up providing support,

---
Patch looks short and sweet, but before landing we should maybe look into  
the
following:

- what other browsers support EXSLT?
- is EXSLT relatively stable as a spec and implementation  (so we won't be
creating future possible compat
issues)?
- is libexslt a high-quality implementation that is reasonably robust?

I think we should do some minimum level of due diligence before adding a  
new
technology and a new
dependency.

Comment #6 From Darin Adler 2006-01-13 03:27 PDT [reply]
Also:

     4) Does registering exslt have an effect on other clients in-process  
who are also using libxslt? Good or
bad?

Comment #7 From Eric Seidel 2006-01-15 00:24 PDT [reply]
(From update of attachment 5630 [edit])
Removing this from the commit queue until mjs's & darin's comments are
addressed.
---

While it's easy enough to point out the obvious (e.g. yes, libexslt is a  
high quality implemenation of EXSLT), I would rather the answers to each  
of these questions came from someone more experienced and better versed  
with the ins and outs of lib(e)xslt.  Also, the question,

"- is EXSLT relatively stable as a spec and implementation  (so we won't  
be creating future possible compat issues)?"

Should really be answered by one of the founding members of the EXSLT  
project and/or someone like Dr. Kay who has extensive experience with  
implementing support in a real-world processor.

-- 
/M:D

M. David Peterson
http://mdavid.name | http://www.oreillynet.com/pub/au/2354 |  
http://dev.aol.com/blog/3155
_______________________________________________
exslt mailing list
list@[...].org
http://www.exslt.org/list