W3C home > Mailing lists > Public > public-qt-comments@w3.org > February 2008

[Bug 5493] [UPD] Default revalidation mode

From: <bugzilla@wiggum.w3.org>
Date: Tue, 19 Feb 2008 19:43:12 +0000
To: public-qt-comments@w3.org
Message-Id: <E1JRYMy-0005Uf-MJ@wiggum.w3.org>


           Summary: [UPD] Default revalidation mode
           Product: XPath / XQuery / XSLT
           Version: Last Call drafts
          Platform: PC
        OS/Version: Windows XP
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Update Facility
        AssignedTo: andrew.eisenberg@us.ibm.com
        ReportedBy: andrew.eisenberg@us.ibm.com
         QAContact: public-qt-comments@w3.org
                CC: john.snelson@oracle.com

One of the XML Query WG members is concerned about the default revalidation
mode. I'll copy, in part, this person's comment:

XQuery Update specifies that the default revalidation mode is "strict".
Although this is implementation defined, I have two observations to make:

1) This has confused quite a few users who don't understand why they are
getting revalidation errors about not being able to find a schema element.

2) The XQuery Update Test Suite doesn't pass without a default revalidation
mode of "lax".

Given that the experience we have with writing update queries suggests that
"strict" is an unhelpful default value for revalidation mode, do we want to
change the default mode to "lax"?
Received on Tuesday, 19 February 2008 19:43:52 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 15:45:35 UTC