[Bug 5579] [UPD] In-situ validation

http://www.w3.org/Bugs/Public/show_bug.cgi?id=5579





--- Comment #2 from Michael Kay <mike@saxonica.com>  2009-03-31 22:49:20 ---
The first justification for the proposal is that we already provide the
facility of in-situ validation, we just don't provide any sensible surface
syntax for it: you invoke it, for example, by doing a rename on a node with the
new name being the same as the old. Since implementations have to provide the
capability, it makes sense to make it accessible to users. This is a
justification based on orthogonality of design, not on specific use cases.

Clearly, as with all updates, use cases depend on the context in which updates
are run: we don't provide any way of taking advantage of the fact that a rename
was done without change of identity, but we assume that updates will occur in
an environment where this is significant to applications. The same applies to
validation. 


-- 
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.

Received on Tuesday, 31 March 2009 22:49:33 UTC