Hi Michael,
I think it would be quite inappropriate for any function or operator in XPath
to attach special meaning to attribute of a particular name, such as @href. The
only way it would make sense would be is if there’s a W3C defining the
semantics of the attribute - e.g. @xlink:href - but almost no-one uses that.
Well, HTML defines its own semantics for all elements and attributes.
Indeed, that is why XQuery does not allow a conformant implementation to add
its own operators.
Too late to care about that, when there are already JSONiq's constructors.
Cheers,
Benito
On 18.05.2015 17:36, Michael Kay wrote:
I think it would be quite inappropriate for any function or operator in XPath
to attach special meaning to attribute of a particular name, such as @href. The
only way it would make sense would be is if there’s a W3C defining the
semantics of the attribute - e.g. @xlink:href - but almost no-one uses that.
Because it would be a shame to add it in an implementation, and then get XQuery
4, where there is a ~ operator that does something completely different.
Indeed, that is why XQuery does not allow a conformant implementation to add
its own operators.
Michael Kay
Saxonica
_______________________________________________
[email protected]
http://x-query.com/mailman/listinfo/talk
_______________________________________________
[email protected]
http://x-query.com/mailman/listinfo/talk
