W3C home > Mailing lists > Public > public-qt-comments@w3.org > April 2005

RE: result-document href="http:// ....

From: Michael Kay <mhk@mhk.me.uk>
Date: Tue, 12 Apr 2005 08:31:52 +0100
To: "'Bernhard Zwischenbrugger'" <lbzwischenbrugger@fh-stpoelten.ac.at>, <public-qt-comments@w3.org>
Message-ID: <6089.30367.1120553703@automsgid.listhub.w3.org>

> I have a question about the URI in  results-document/@href
> Is this possible to submit the result tree to the internet?
> Here an example:
> ================
> This should connect to Google und format the Google result
> (you need your own key)
> <xsl:result-document href="http://api.google.com/search/beta2"
> format="toc-format" validation="strict">

The answer is that it's implementation-defined. There are two factors that
influence this:

(a) the URI given in the href attribute cannot necessarily be used to
retrieve a serialized representation of the result document. As far as the
specification is concerned, the only guarantee is that the application can
somehow use this URI as an identifier to obtain a representation of the
result tree.

(b) the implementation is allowed to restrict the set of URIs that may be
used in this attribute, for example it may support some URI schemes and not

In Saxon the only URI scheme that's supported natively is the "file:"
scheme; applications can implement an OutputURIResolver if they wish to
support other schemes. (I haven't yet found a way of invoking an HTTP PUT
request, but it can probably be done). Clearly for some schemes there will
be a need to provide authentication for security reasons.

Since this is an area that affects the interface between the XSLT
transformation and the invoking application, we've tried to define the spec
here in a fairly abstract and flexible way to leave room for implementations
to innovate based on how they see the user requirements.

Michael Kay

Received on Tuesday, 12 April 2005 07:31:58 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 15:45:23 UTC