OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help



   Re: XLink transformations

[ Lists Home | Date Index | Thread Index ]
  • From: Martin Bryan <mtbryan@sgml.u-net.com>
  • To: Ben Trafford <ben@legendary.org>, xml-dev@xml.org
  • Date: Tue, 18 Jul 2000 08:26:40 +0100


>          There are interesting issues around recursion of links (what 
> happens if I call a document that calls a document that calls a document, 
> and so forth) and what stylesheet properties to include (what happens when 
> I call a document with its own stylesheet, does mine override it? What 
> happens when the two documents share the same element names?). I've 
> resolved the former issue with a simple error catching if too much 
> recursion happens (and recursion levels can be set as a variable in the 
> tool), and the latter using a fairly complicated scheme where onLoad 
> documents are brought in with their stylesheet declaration and some nifty 
> namespace magic.

Its interesting that you've raised this issue with the XLink group as I've just raised a similar issue with the XInclude group (what happens if the included object has an attached stylesheet - what is its scope?). They pointed out to me that xsl-stylesheet PIs are only valid if the occur in the prolog, so any included stylesheet calls are invalid. Presumably the same applies to documents that are linked to another document as the PI therefore does not get placed in the combined tree at a valid point. The question I raised was whether it shouldn't be a requirement that PIs that are known to be invalid in context be stripped from the inclusion tree.

Martin Bryan


News | XML in Industry | Calendar | XML Registry
Marketplace | Resources | MyXML.org | Sponsors | Privacy Statement

Copyright 2001 XML.org. This site is hosted by OASIS