XPath Ease of, and analogous development: was RE: [xs

Attempt to clean up the Subject since I started this tangent.

Aron Bock [aronbock@xxxxxxxxxxx]
>all right and regular expressions are easy, but I often seem to get
>stuck with XPath. Does anyone else feel like this?.....)

All the time, and I fully intend to wallow in my mudbath of ignorance
until
I finally do some reading.  Thus far, unfortunately, that's been both
cursory and desultory.

My take is that xpath's barrier to entry is low, so you can get along
quite
well for quite a while, until you need bigger artillery ... and then
find
there's a bigger instruction manual which goes with *that* machinery.

Still, it seems a simple enough mental model, and it's just a matter of
learning of and applying its semantics.

:->

--A

_________________________________________________________________
Express yourself instantly with MSN Messenger! Download today - it's
FREE!
http://messenger.msn.click-url.com/go/onm00200471ave/direct/01/


-----Original Message-----
From: Richard Lewis [mailto:richardlewis@xxxxxxxxxxxxxx]
Sent: Friday, May 20, 2005 1:25 PM
To: xsl-list@xxxxxxxxxxxxxxxxxxxxxx
Subject: RE:  relative path from one node to another (XSLT 2.0
solution)


On Fri, 20 May 2005 13:06:49 -0400, "Ross, Douglas" <DRoss@xxxxxxxxxx>
said:
> Richard,
>
> Did you just say RegEx is easy?! You are much smarter than you give
> yourself credit for. :) Xpath started to make a lot more sense to me
> when I implemented a simple XPath engine in ECMA Script for finding
> nodes in HTML clients. I finally understand axis, determinates and the
> current context node. Even with this understanding, I still find a lot
> of this stuff is magic! By the way, my new moto is "XML is all!"
>
I think the reason why regex came to mind was that development problems
with XPath and regex are quite similar, IMO. If you think about
development with a 'normal' (prepared to be flamed!) programming
language like C or Java, you can split things up into lots of little
expressions and produce lots of useful debugging output in order to get
your algorithms right, in fact, you can think in algorithms. Whereas
with XPath and regex you're wokring on a single expression to do a whole
job, almost to express an 'algorithm'; getting debugging output is more
long winded with XPath (and nearly impossible with regex). Of course
they differ in that a regex is dealing with plain text in an entirely
serial order whereas with XPath, you have to understand document
structure (which makes it, ultimately, much more powerful).

Richard