W3C home > Mailing lists > Public > xsl-editors@w3.org > January to March 2005

RE: FW: Action: Replies to Glen Mazza's comments on Bookmarks

From: Glen Mazza <grm7793@yahoo.com>
Date: Sat, 5 Feb 2005 11:17:10 -0800 (PST)
Message-ID: <20050205191710.30853.qmail@web80506.mail.yahoo.com>
To: XSL Editors List <xsl-editors@w3.org>

--- Paul Grosso <pgrosso@arbortext.com> wrote:
> The external-destination property is a URI
> reference, 
> and its fragment identifier is supposed to be used
> to 
> indicate a sub-resource.  This is clearly specified
> in the description of external-destination and is
> completely appropriate for its use on fo:basic-link;
> we don't need any additional property.
> I don't know how fragment identifiers would work for
> PDF bookmarks--I have not really researched or
> thought 
> it through yet--but offhand I'd say that if the
> value
> of the "external destination" (by whatever name) for
> a bookmark should be a URI reference, then the
> fragment
> identifier concept should work, and if the value of 
> the "external destination" on a bookmark cannot be
> seen 
> as being a URI reference, then we probably can't be
> using
> external-destination at all for fo:bookmark.
> paul

Sorry--I had completely forgotten about fragment
identifiers to get to subresources while writing this.

While the internal implemention of PDF bookmarks does
not appear to support URI resources with fragment
identifiers directly[1], the value of the
external-destination can be parsed by the XSL
processor to determine resource and sub-resource, and
the renderer can use those separated fields in
constructing the bookmark.  I.e., we should be fine
with external-destinations on bookmarks.


[1] File Specification Strings, Section 3.10.1 of PDF
1.5 Reference:

"In the case of a URL-based file system, the rules of
Internet RFC 1808, Relative Uniform Resource Locators
(see the Bibliography), are used to compute an
URL from a relative file specification and the
specification of the PDF file....In addition, such
URL-based relative file specifications are limited to
paths as defined in RFC 1808; the scheme, network
location/login, fragment identifier, query
information, and parameter sections are not allowed."
Received on Saturday, 5 February 2005 19:17:42 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:44:24 UTC