[XSL-LIST Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message] Re: vendor neutral XSL extension namespace ?
James Clark wrote: > > I think this is much more along the right lines, but it's not clear to > me how name clashes would be managed. Suppose one vendor wants a "group" > extension element that works a bit like xsl:for-each, and another vendor > wants a "group" extension element that works a bit like xsl:sort. Or > suppose one vendor wants an "intersection" extension function that > accepts 2 arguments, and another vendor wants an "intersection" > extension function that accepts an arbitrary number of arguments. I would say, first come, first serve. If you get stuck with "intersection_2", that's tough luck. If you want perfect control over naming, you need to use a proprietary namespace. Paul Prescod - ISOGEN Consulting Engineer speaking for himself "Chaos is the Engine" - Len Bullard XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
|
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
|