Lists Home |
Date Index |
> I think the benefits are:
Thank you Michael for this well articulate answer. It makes perfect
Yes, some of the benefits can be achieved by XQueryX, some not.
>> And why don't you get the same benefits from XQueryX (the pure XML
>> variant of XQuery) ?
> Because no one would ever want to author or edit or maintain a query
> that particular language - it's far too low-level.
Sure, but that's not the point. That's why XQuery has two equivalent
one to please human programers, and one optimized for automatic
Those two sets of requirements are too different from each other,
If you try to satisfy both requirements with a unique syntax,
will be some requirements that will not be fully satisfied.
For example, one cannot query (for example for security reasons) if a
certain XSLT stylesheet
accesses the salary attribute of employee elements using only
an XML processor. In addition, one need to parse the attribute values
to get that information.
Moreover, by using an XML syntax I am sure XSLT scared certain
You don't hear from them I think because you mostly hear from people
who *like* XSLT.
I think you don't talk to a good statistical sample of the programmer
population (but I don't
have of course evidence to support that).
And no, a angle brackets free syntax build by a single person in a
corner will not attract me.
I have no guarantee that this syntax will still be there, and continued
if the guy decides
to quit. One cannot program using a syntax unless there is some
assurance of continuity.