Another one, what if i want to assign to a variable all the occurrences
of a particular element and cast it as element()+ will i still be able
to access the information above and below the particular element, above
meaning preceding nodes and below meaning following node? And how do i
write that in xsl? Is this a correct way to achieve this?
<xsl:variable name="articles" as="element()+" select="for $file in
collection(iri-to-uri('XML files?select=*.xml')) then $file//article"/>
Thanks again,
-- Jeff
Jeff Sese wrote:
Yes i'm using a relative uri, and i found out that i need to escape
the string to %HH format for it to work.
Thanks Sir Mike!
-- Jeff
Michael Kay wrote:
If the directory is called "c:\XML files", then you should use
collection('file:///c:/XML%20files')
(It might work without escaping the space as %20, I'm not sure)
If you use a relative URI, then it will be taken as relative to the
URI of
the stylesheet.
Michael Kay
http://www.saxonica.com/.
-----Original Message-----
From: Jeff Sese [mailto:jsese(_at_)asiatype(_dot_)com] Sent: 18 September 2006
11:55
To: xsl-list(_at_)lists(_dot_)mulberrytech(_dot_)com
Subject: Re: [xsl] Referencing Multiple Documents in One Folder --
Repost
I'm trying to load a group of xml files that are found in a local
sub-directory where the xslt file is located, what i'm doing is:
<xsl:for-each select="collection('XML files')">
<xsl:copy-of select="."/>
</xsl:for-each>
But i'm getting an invalid URI error. I'm do not know much about
URIs and this is the first time that i'm trying to do this loop thru
a collection of document thing, i usually make a reference to a
single document with can be easily done using the document() function.
-- Jeff
Michael Kay wrote:
What do i need to pass as a parameter of the collection
function? Is
it a URI of an catalog xml file that list all the files i need to
loop through? or is it just the URI of the folder that
contains all
the xml files i need?
In Saxon, those are the two options supported by the default
collection URI resolver. You can use either approach, but I
think you
wanted the latter. If there's part of the documentation you don't
understand, please explain what part.
Michael Kay
http://www.saxonica.com/
--~------------------------------------------------------------------
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
To unsubscribe, go to: http://lists.mulberrytech.com/xsl-list/
or e-mail: <mailto:xsl-list-unsubscribe(_at_)lists(_dot_)mulberrytech(_dot_)com>
--~--
--~------------------------------------------------------------------
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
To unsubscribe, go to: http://lists.mulberrytech.com/xsl-list/
or e-mail: <mailto:xsl-list-unsubscribe(_at_)lists(_dot_)mulberrytech(_dot_)com>
--~--
--~------------------------------------------------------------------
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
To unsubscribe, go to: http://lists.mulberrytech.com/xsl-list/
or e-mail: <mailto:xsl-list-unsubscribe(_at_)lists(_dot_)mulberrytech(_dot_)com>
--~--
--~------------------------------------------------------------------
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
To unsubscribe, go to: http://lists.mulberrytech.com/xsl-list/
or e-mail: <mailto:xsl-list-unsubscribe(_at_)lists(_dot_)mulberrytech(_dot_)com>
--~--
--~------------------------------------------------------------------
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
To unsubscribe, go to: http://lists.mulberrytech.com/xsl-list/
or e-mail: <mailto:xsl-list-unsubscribe(_at_)lists(_dot_)mulberrytech(_dot_)com>
--~--