This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 5180 - [UPD] revalidating something that isn't an XDM instance
Summary: [UPD] revalidating something that isn't an XDM instance
Status: CLOSED FIXED
Alias: None
Product: XPath / XQuery / XSLT
Classification: Unclassified
Component: Update Facility (show other bugs)
Version: Last Call drafts
Hardware: All All
: P2 normal
Target Milestone: ---
Assignee: Andrew Eisenberg
QA Contact: Mailing list for public feedback on specs from XSL and XML Query WGs
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-10-11 01:16 UTC by Michael Dyck
Modified: 2007-11-13 19:02 UTC (History)
0 users

See Also:

Attachments

Description Michael Dyck 2007-10-11 01:16:32 UTC 
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.
Comment 1 Don Chamberlin 2007-11-13 19:02:27 UTC 
Michael,
On 13 Nov. 2007 the working group discussed and agreed with your proposed change, and it has been applied to the working draft. Since you were present at the discussion, I am marking this bug report as Fixed and Closed.
Regards,
Don Chamberlin (for the Query Working Group)