I took your argument to presume an implication that if a technology isn't used directly by web authors at a notciable level, then there is no benefit to those authors by implementing it.
Yes, I thought of this the other day, and finally saw what you meant (duh). If you believe "developers" (form schema/back-end designers) will be the only ones writing XPath, and "web content authors" won't have to learn it, then we agree.
I'm still not sure XPath is best for "developers", but maybe it's no worse -- a lot of back end developers prefer their "home" or "favorite" language, or family of languages, so much of the competitive advantage in server-side settings is to cater to many languages.
I'm also not sure that XForms separates duties in ways that reliably relieve the "web content authors" from having to learn XPath. That's the goal, but can it be achieved in practice?
/be _______________________________________________ mozilla-layout mailing list [EMAIL PROTECTED] http://mail.mozilla.org/listinfo/mozilla-layout
