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 4287 - [UPD] Revalidation mode limits
Summary: [UPD] Revalidation mode limits
Status: CLOSED FIXED
Alias: None
Product: XPath / XQuery / XSLT
Classification: Unclassified
Component: Update Facility (show other bugs)
Version: Working drafts
Hardware: PC Windows XP
: 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-01-30 20:46 UTC by John Snelson
Modified: 2007-01-31 00:19 UTC (History)
0 users

See Also:


Attachments

Description John Snelson 2007-01-30 20:46:27 UTC
In section 2.2, the XQuery Update specification states that the revalidation mode can be overwritten by a query -

  "but a revalidation declaration may not specify a mode that is less strict than the implementation-defined default."

I understand that this addresses the needs of such systems that require their data to conform to a schema. However, this doesn't address systems where either validation is not supported (it is an optional XQuery feature), or the data model does not support PSVI. In these cases, the implementation would not want the revalidation mode to be set /more strict/ than the implementation defined default.

I think that the specification should be rewritten to state that support for each revalidation mode is implementation defined.
Comment 1 Don Chamberlin 2007-01-30 23:34:59 UTC
John,
Thanks for your comment. The working group considered your suggestion
on Jan. 30, 2007 and agreed to make support for each of the three 
revalidation modes implementation-defined. This change will be reflected
in the next working draft of the update specification.
Regards,
Don Chamberlin (for the Query Working Group)