Altova Mailing List Archives


Re: [xsl] stylesheet expansion

From: Colin Paul Adams <colin@------------------>
To:
Date: 12/10/2007 6:23:00 AM
>>>>> "Abel" == Abel Braaksma <abel.online@xxxxxxxxx> writes:

    Abel> <xsl:import
    Abel> href="http://otherhost-to-same-location/multiple-stylesheets-in-one.xslt#include-me"
    Abel> />

    Abel> but I don't know (not tested), if the #-syntax is supported
    Abel> this way (I remember a few W3C notes on the subject, but I
    Abel> can't recall whether it is legal and whether only the node
    Abel> with "include-me" will get selected).

Whether fragment identifiers are supported is implementation dependent.
As too, which media types are supported.

For the really pedantic, note that there isn't strictly any
circumstances under which any appropriate media-type/fragment
identifier combination would be legitimate, due to RFC 3023 not having
been updated.

In practice, one uses the XPointer framework, and ignores the
conformance nicety (Gestalt actually has options to override this
behaviour, so as to override the objection of even the most
died-in-the-wool pedant (such as the author), but no-one would use it
in practice).

So, in practice, you could get away with using this approach (by
aliasing two different URIs to refer to the same resource, thus
defeating the processor check), but it sounds highly cumbersome to me.

Compiled transformations sounds like a better solution.
-- 
Colin Adams
Preston Lancashire

Disclaimer

These Archives are provided for informational purposes only and have been generated directly from the Altova mailing list archive system and are comprised of the lists set forth on www.altova.com/list/index.html. Therefore, Altova does not warrant or guarantee the accuracy, reliability, completeness, usefulness, non-infringement of intellectual property rights, or quality of any content on the Altova Mailing List Archive(s), regardless of who originates that content. You expressly understand and agree that you bear all risks associated with using or relying on that content. Altova will not be liable or responsible in any way for any content posted including, but not limited to, any errors or omissions in content, or for any losses or damage of any kind incurred as a result of the use of or reliance on any content. This disclaimer and limitation on liability is in addition to the disclaimers and limitations contained in the Website Terms of Use and elsewhere on the site.