[Bug 16161] New: disallowedSubst00503m3,4,5 should be invalid for XSD 1.1

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
9 messages Options
Reply | Threaded
Open this post in threaded view
|

[Bug 16161] New: disallowedSubst00503m3,4,5 should be invalid for XSD 1.1

Bugzilla from bugzilla@jessica.w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=16161

           Summary: disallowedSubst00503m3,4,5 should be invalid for XSD
                    1.1
           Product: XML Schema Test Suite
           Version: 2006-11-06
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Sun Tests
        AssignedTo: [hidden email]
        ReportedBy: [hidden email]
         QAContact: [hidden email]


In my opinion the expected result of the test cases disallowedSubst00503m3,
disallowedSubst00503m4 and disallowedSubst00503m5 of set ElemDecl should be
invalid for XSD 1.1 because they violate clause 4 of Schema Component
Constraint: Element Declaration Properties Correct.

As described in http://www.w3.org/TR/xmlschema11-1/#key-val-sub-type a complex
type definition S is validly substitutable for another complex type definition
T if: "S is validly derived from T subject to the blocking keywords in the
union of K and T. {prohibited substitutions}, as defined in Type Derivation OK
(Complex) (ยง3.4.6.5)"

So in difference to XSD 1.0 this also considers the prohibited substitutions of
T (i.e. the value of the block attribute of the complex type definition "Type"
in the concrete examples).

--
Configure bugmail: https://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
Reply | Threaded
Open this post in threaded view
|

[Bug 16161] disallowedSubst00503m3,4,5 should be invalid for XSD 1.1

Bugzilla from bugzilla@jessica.w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=16161

David Ezell <[hidden email]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Keywords|                            |needsAgreement
                 CC|                            |[hidden email]

--- Comment #1 from David Ezell <[hidden email]> 2012-04-13 15:52:42 UTC ---
Needs further research.
Once the test suite is in its new location this research will be easier.

--
Configure bugmail: https://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.

Reply | Threaded
Open this post in threaded view
|

[Bug 16161] disallowedSubst00503m3,4,5 should be invalid for XSD 1.1

Bugzilla from bugzilla@jessica.w3.org
In reply to this post by Bugzilla from bugzilla@jessica.w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=16161

Michael Kay <[hidden email]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[hidden email]

--- Comment #2 from Michael Kay <[hidden email]> 2012-04-13 17:04:32 UTC ---
I agree with Andreas. The spec has been deliberately changed. In XSD 1.0 you
were allowed to say that Member1 is in the substitution group of Head, but
saying this had no effect, so the instance is invalid. In XSD 1.1 we've changed
it so instead of being ineffective, it's an error. (Saxon issues a warning at
schema processing time; the code that issues this warning carries a comment
which could be interpreted as slanderous.)

--
Configure bugmail: https://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.

Reply | Threaded
Open this post in threaded view
|

[Bug 16161] disallowedSubst00503m3,4,5 should be invalid for XSD 1.1

Bugzilla from bugzilla@jessica.w3.org
In reply to this post by Bugzilla from bugzilla@jessica.w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=16161

--- Comment #3 from Michael Kay <[hidden email]> 2012-04-20 22:41:28 UTC ---
As far as I can see the same reasoning also makes the following invalid:

disallowedSubst00105m
disallowedSubst00106m2
disallowedSubst00501m2
disallowedSubst00502m3
disallowedSubst00502m4

--
Configure bugmail: https://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.

Reply | Threaded
Open this post in threaded view
|

[Bug 16161] disallowedSubst00503m3,4,5 should be invalid for XSD 1.1

Bugzilla from bugzilla@jessica.w3.org
In reply to this post by Bugzilla from bugzilla@jessica.w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=16161

--- Comment #4 from Michael Kay <[hidden email]> 2012-04-20 22:53:50 UTC ---
To try and sum up my reading of the current rules in ordinary English:

(a) if you declare an element M as being in the substitution group of H, and H
blocks substitution, that's not in itself an error, it just means M can't be
substituted for H.

(b) however, if the type of M is not substitutable for the type of H, perhaps
because either H or the type of H blocks substitution (or
restriction|extension, if the type of M is a restriction|extension), that is an
error - it makes the schema invalid. This is the case that has changed since
1.0.

I suppose it's pointless to ask why the distinction?

--
Configure bugmail: https://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.

Reply | Threaded
Open this post in threaded view
|

[Bug 16161] disallowedSubst00503m3,4,5 should be invalid for XSD 1.1

Bugzilla from bugzilla@jessica.w3.org
In reply to this post by Bugzilla from bugzilla@jessica.w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=16161

--- Comment #5 from Michael Kay <[hidden email]> 2012-04-25 20:17:05 UTC ---
Other affected tests in the Microsoft ElementDecl test set:

elemT062
elemT063
elemT064
elemT065
elemT066
elemT077

--
Configure bugmail: https://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.

Reply | Threaded
Open this post in threaded view
|

[Bug 16161] disallowedSubst00503m3,4,5 should be invalid for XSD 1.1

Bugzilla from bugzilla@jessica.w3.org
In reply to this post by Bugzilla from bugzilla@jessica.w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=16161

--- Comment #6 from Michael Kay <[hidden email]> 2012-04-26 14:33:19 UTC ---
Test msData/additional/addB114.xsd has the same problem.

--
Configure bugmail: https://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.

Reply | Threaded
Open this post in threaded view
|

[Bug 16161] disallowedSubst00503m3,4,5 should be invalid for XSD 1.1

Bugzilla from bugzilla@jessica.w3.org
In reply to this post by Bugzilla from bugzilla@jessica.w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=16161

David Ezell <[hidden email]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Keywords|needsAgreement              |decided

--- Comment #7 from David Ezell <[hidden email]> 2012-05-04 16:22:58 UTC ---
Resolved: change the outcome of the listed tests to invalid for 1.1.

--
Configure bugmail: https://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.

Reply | Threaded
Open this post in threaded view
|

[Bug 16161] disallowedSubst00503m3,4,5 should be invalid for XSD 1.1

Bugzilla from bugzilla@jessica.w3.org
In reply to this post by Bugzilla from bugzilla@jessica.w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=16161

[hidden email] changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 OS|All                         |Windows 3.1

--
You are receiving this mail because:
You are the QA Contact for the bug.