Home. 
.

transparent

transparent

transparent

Altova Mailing List Archives


Re: [xml-dev] find with XPath over file system

From: Oleg Paraschenko <usenet@---------.--->
To: Eric van der Vlist <vdv@--------.--->
Date: 2/1/2005 12:32:00 PM
Hi Eric,

On Fri, 28 Jan 2005 18:29:51 +0100
Eric van der Vlist <vdv@d...> wrote:

> Hi Oleg,
> 
> ...
> 
> I like the way you've preferred to match the /bin directory on the
> /bin XPath instead of using some kind of /directory[@name="bin"]
> convention...

  Many XPath tutorials say that "the basic XPath syntax is similar to
filesystem addressing." I decided it was good to keep the analogue.

> 
> However, I am wondering how you deal with filenames that are no valid
> XML names (or that contain colons)...
> 
> Can you elaborate on that point?

  The underlying library allows to have anything as XML name, so there
are no problems with the virtual XML tree. More, the name of a file is
duplicated in the "name" attribute, so you can put a test for name into
a predicate: /*[@name='lost+found'].

> 
> Thanks,
> 
> Eric
> 



-- 
Oleg


transparent
Print
Mail
Like It
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.

.
.

transparent

transparent