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

[Bug 7818] New: Statement on wildcard unions misleading.

From: <bugzilla@wiggum.w3.org>
Date: Tue, 06 Oct 2009 14:18:58 +0000
To: www-xml-schema-comments@w3.org
Message-ID: <bug-7818-703@http.www.w3.org/Bugs/Public/>
http://www.w3.org/Bugs/Public/show_bug.cgi?id=7818

           Summary: Statement on wildcard unions misleading.
           Product: XML Schema
           Version: 1.1 only
          Platform: PC
        OS/Version: Windows XP
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Structures: XSD Part 1
        AssignedTo: David_E3@VERIFONE.com
        ReportedBy: kbraun@obj-sys.com
         QAContact: www-xml-schema-comments@w3.org
                CC: cmsmcq@blackmesatech.com


In the "changes since":

"All wildcard unions are now expressible, and wildcard union is used to combine
 multiple attribute wildcards, rather than wildcard intersection; this change
resolves issue 6163 3.10.6.3 Attribute Wildcard Union."

I cannot find anyplace where the use of wildcard union has replaced the use of
wildcard intersection.  I only see one place where wildcard union is used,
which is 3.4.2.5, and the corresponding section in 1.0 also used union.

If there is a rule where wildcard union has replaced wildcard intersection, it
would be helpful to identify it.  If the statement is not intended to imply
that such a replacement has occurred, I suggest changing it to:

"All wildcard unions are now expressible; this change resolves issue 6163
3.10.6.3 Attribute Wildcard Union."


-- 
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
Received on Tuesday, 6 October 2009 14:19:00 GMT

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