Lists Home |
Date Index |
David Carlisle <firstname.lastname@example.org> writes:
> > 1) I was overly terse above, and at least one other respondent has not
> > unreasonably misunderstood -- I should have said "any sensible use of
> > QNames _in content_ . . ." (as opposed to for element and attribute
> > names).
> But as others have said, Schema types don't help in many common uses of
> Qnames in content (Xpath expressions for example). Is XPath a sensible use?
XPath is a nifty design which precisely identified the sweet spot
with respect to expressiveness, formality and terseness/usability.
The fact that it's a compact representation of a structured object
which _could_ have been verbosely expressed using XML is a fact of
I think it made sense for XPath to use a compact representation, and I
think it made sense to use the QName syntax within it. (I _don't_
think it made sense to treat unprefixed names as unqualfied, but
that's another story). So use, XPath is a sensible use. And no, XML
Schema doesn't immediately give you everything you need to find the
QNames lurking within XPath expressions. XPath is worth it, despite
this, in my view.
Henry S. Thompson, HCRC Language Technology Group, University of Edinburgh
W3C Fellow 1999--2001, part-time member of W3C Team
2 Buccleuch Place, Edinburgh EH8 9LW, SCOTLAND -- (44) 131 650-4440
Fax: (44) 131 650-4587, e-mail: email@example.com