RE: XSLT for Mashups
> FWIW: We chose XSL over XQuery mainly for the ability to do > schema validation. We wanted third parties to add custom > tags (similar to extensions in XSL). Vendors could then > create schemas that would ensure the templates only contained > tags supported by that vendor. This raises the interesting idea that we could build into the language spec some kind of mechanism where the syntax of an XSLT language extension (i.e. extension instructions) is described in a standard way in some kind of schema, while still leaving the semantics to be defined by a third party and the binding mechanism to an implementation to be defined by implementors. Generally I think the XSL WG would not want to take on the job of defining extensions such as access to SQL or LDAP databases itself, but would welcome language extensions (within the standard extensibility framework) developed by third parties. That leaves many process issues open, but the bottom line is that not everything has to be done within W3C. Regards, Michael Kay http://www.saxonica.com/ http://twitter.com/michaelhkay
PURCHASE STYLUS STUDIO ONLINE TODAY!
Purchasing Stylus Studio from our online shop is Easy, Secure and Value Priced!
Download The World's Best XML IDE!
Accelerate XML development with our award-winning XML IDE - Download a free trial today!
Subscribe in XML format