Re: XSLT V 1.1

----- Original Message ----- 

From: Eckenberger Axel <Extern.Eckenberger@xxxxxxxx>

> > 1. Provide XSL stylesheet with URI of 'XML' and 'XSL'.
> > 2. Resolve all URI's in document() relatively to 'XML'
> > and 'xsl:import' 'xsl:include' relatively to 'XSL'
> > 3. For other (weird) cases - calculate the desired
> > URI by yourself.
> > 
> > Yes, (3) requires XSL Engine  to provide 2
> > parameters to each stylesheet. Like :
> > "current-xsl" and "current-xml".
> > 
> > Or "$argv0" and "$argv1".  Or add 2 more functions,
> > like get-xsl-uri() and get-xml-uri().
> > 
> > 2 more parameters will be better than 2 more functions,
> > from my point of view and will be better than current
> > document().
> 
> The problem is that you look at the topic from a point of view where you
> have files, but if you use XML within components (via the DOM) you might not
> have them and IMHO this is not a 'weied' case. I agree that there should be
> a way of determinig the URI for a node (and a way of determining whether
> ther is _no_ URI, see above). 

This all becomes very hypotetical. When you have XML and XSL 'without files' 
( 'without URI' ) how can document() with two parameters help you?

If URI of XML is provided - use it to resolve the relative paths. If URI
does not exist - don't use it. 

> Hovever, I do not agree with you that it
> should be the document function's default behaviour to resolve relative
> paths relative to the xml document.

No problem. 

Rgds.Paul.



 XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list