Re: XPath 2.0: on bindings to atomic values and the result of the element()/attribute() functions

>
> This one is a bit more difficult, I see the use case of using insert or
> setvalue on the resulting nodes, but I also see users not understanding why
> there values in controls are reset on 'arbitrary' moments in time (in fact
> it will be when the function is re-evaluated, but this might not be on
> every refresh in some implementations).
>

>  After some more thought I'm no longer strongly against making the
> resulting nodes of the element() and attribute() functions read/write.
> But if we make the resulting nodes read/write, we should at least add a
> note in the spec to warn implementers for this behavior. Maybe even
> encourage implementers to 'log a warning' if a form control is bound to a
> resulting node or a descendant of it.
>

Just adding an example of what NOT to do with element() is probably enough.

-Erik