This is the mail archive of the xsl-list@mulberrytech.com mailing list .
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
Other format: | [Raw text] |
--- David Carlisle <davidc@nag.co.uk> wrote: > > > p.s. What is strange is that SAXON obviously knows the file names > it > > is processing, > > It isn't obvious that the XML it is processing has a name. Both the > source XML and the stylesheet might come from standard input > stream, or > from a stream of sax events or.... Dear David C., Even given what you have said, isn't it true that I must call up a file name whether it be from the command line, or with xsl:import or xsl:include, etc.? And if so, then why not capture those ?.xsl names for the comment either at their location or globally? Again, SAXON has the name/path anyway. > Every Xpath node does however have a base URI associated, but XSLT > gives > no standard access to that information. saxon has a saxon:systemId > extension to get at it though.... ??? <saxon:systemID select="document('')"/> Sincerely, Mike Ferrando Washington, DC __________________________________________________ Do You Yahoo!? Yahoo! Health - your guide to health and wellness http://health.yahoo.com XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |