Cart
[Home] [By Thread] [By Date] [Recent Entries]
I don't necessarily think that removing namespaces is the answer. Reforming them is. I think that XQuery is one of the first languages that I've seen where namespace usage begins to approach that used by other programming language, and even there it's primarily because XQuery can be used in an object like context. In general people don't like namespaces because namespaces have a tendency to reflect authority, rather than library organization. Similarly, I think the XPath fails on this same regard. From a programmer's standpoint: /bookstore:bookSet/bookstore:book/bookstore:author seems unduly redundant, and they'd be right; why can't we say
bookstore:/bookSet/book/author or even com.mycompany.bookstore:/bookSet/book/author
THAT feels a lot more like most programmers are user to.
I worry that in the rush to "simplify" XML people are interpreting the problem with namespaces as being that programmers are too stupid to use them. I have to wonder if instead, we've created a namespace notation that is counterintuitive to the way that programmers handle their own namespace issues (and anyone doing OOP deals with namespaces in some fashion or another).
Kurt Cagle XML Architect Lockheed / US National Archives ERA Project On Sun, Dec 19, 2010 at 10:07 PM, Liam R E Quin <liam@w...> wrote: On Sun, 2010-12-19 at 21:05 -0500, Amelia A Lewis wrote:
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] |
