- From: <bugzilla@wiggum.w3.org>
- Date: Thu, 11 Oct 2007 01:16:33 +0000
- To: public-qt-comments@w3.org
- CC:
http://www.w3.org/Bugs/Public/show_bug.cgi?id=5180 Summary: revalidating something that isn't an XDM instance Product: XPath / XQuery / XSLT Version: Last Call drafts Platform: All OS/Version: All Status: NEW Severity: normal Priority: P2 Component: Update Facility AssignedTo: andrew.eisenberg@us.ibm.com ReportedBy: jmdyck@ibiblio.org QAContact: public-qt-comments@w3.org In 3.2.2 upd:applyUpdates, the step that does revalidation precedes the step that checks whether the result violates any constraints of the Data Model. Thus, the argument to upd:revalidate might be an object that violates those constraints. But presumably it's meaningless to do revalidation on such an object. So perhaps the order of those two steps should be swapped.
Received on Thursday, 11 October 2007 01:16:48 UTC