W3C home > Mailing lists > Public > www-xml-schema-comments@w3.org > October to December 2006

[Bug 3997] R-237: Possible errors in the S4S

From: <bugzilla@wiggum.w3.org>
Date: Wed, 22 Nov 2006 04:23:41 +0000
CC:
To: www-xml-schema-comments@w3.org
Message-Id: <E1Gmje9-0003Il-1u@wiggum.w3.org>

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

           Summary: R-237: Possible errors in the S4S
           Product: XML Schema
           Version: 1.0 only
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Structures: XSD Part 1
        AssignedTo: cmsmcq@w3.org
        ReportedBy: sandygao@ca.ibm.com
         QAContact: www-xml-schema-comments@w3.org
 BugsThisDependsOn: 2229


The following are a few things that look like errors in the current schema-for-
schema posted on http://www.w3.org/2001/XMLSchema.xsd 

Some of them have been discussed here in the past or even mentioned in the 
errata, but don't seem to be reflected in the posted xsd.... They are all minor 
things, but they all do get in the way of actually using the schema-for-schema 
to validate schemas. Here is my list of changes: 

1. finalDefault needs to permit "list" and "union" 
2. the type of the <element> element in an <all> group needs to be given a name 
so that it is legal to use the type in both a base type and a restriction when 
using the allModel (otherwise it breaks one of the particle-valid (restriction) 
rules). 
3. The regular expressions that describe integrity constraint xpaths need to be 
modified to permit whitespaces in certain places, as discussed in one of the 
errata. 

See:
http://lists.w3.org/Archives/Public/www-xml-schema-comments/2003JulSep/0087.html
Received on Wednesday, 22 November 2006 04:23:49 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Sunday, 6 December 2009 18:13:11 GMT