Comments on XSL extensions


Thank you for your comments on XSL sent to XSL-Editors at:

The XSL FO Subgroup discussed most of your comments at our
recent meeting.  I have been tasked with requesting clarification
of one of your comments.

One of your requested extensions is as follows:


The axf:base-uri specifies the location which becomes the base 
of relative URI.

Value: <uri-specification>
Initial: empty string
Applies to: all formatting objects
Inherited: yes
Percentages: N/A

The axf:base-uri is applied to all relative URI in a document. When making 
links using fo:basic-link and specify relative URI, the location that is 
specified using axf:base-uri is interpreted to be base URI. If this property 
is omitted or this has empty string, the base location is interpreted as 
current XML file.

The standard way to affect the base URI (as defined by RFC 2396 [1]) would
be to incorporate recognition and use of xml:base [2] in XSL-FO processors.

The base URI so determined would then affect all attributes of typw <uri-specification>).  

But we are not sure that is what you really want.

For example, the actual request is to affect the external-destination of 
fo:basic-link, but we don't see how this can be made to work.  When a
link is activated, the current document is presumably the PDF rendering
which is a resource that has no particular relationship to the FO result
document that was the current XML document when the base URI was determined.
That is, if I processed XML plus XSL to produce PDF on my machine and then
sent you that PDF (or put the PDF up on the internet), having some path
in that PDF whose base URI points to someplace on my machine would not work.

Can you please elaborate, given user scenarios, the situation you are
hoping to address with axf:base-uri.


Paul Grosso
for the XSL FO subgroup

Received on Monday, 22 March 2004 18:04:50 UTC