Submitting XML Schema 1.1 to ISO - review of normative (and other) changes

Dear XML Core:
This email is in partial completion of our action regarding "Submitting XML Schema 1.1 to ISO."

ACTION to Loren and David:  Check if any changes are normative
and/or would require a change to the test suite (and that aren't
already supported by implementations).

In earlier meetings, we decided to use the errata page kindly left by Michael Sperberg-McQueen:
https://www.w3.org/XML/Group/2004/06/xmlschema-1/structures.errata-2012.html

I have extracted the text from the "Status of This Document" section (what and how) and added my $0.02 about whether I think a new test is required, whether the change is normative, and whether the change is breaking (even if it is normative).

As a group, you need to agree with me and we need to decide on work required to bring the matter forward.  Please review.

Best regards,
David Ezell

<snip/>

What

How

Test Required

Normative?

Comments

A wording proposal which resolves issue 16777 Is the content model for override a sequence or a choice?

by making the top-level group for the content model of the <override> element be a choice, not a sequence.

No

Debatable

I think 'no'.











A wording proposal which resolves issue 16778 S4S has test attribute as optional on assertion/assert

by marking the test attribute on assert and assertion as required.

No

No













A wording proposal which resolves issue 16781 DTD for Schemas has default value for mixed attribute on complexType

by removing the default attribute for the mixed attribute on complexType from the DTD for schema documents.

No

No













A wording proposal which resolves issue 16785 simpleContent summary leaves out explicitTimezone

by correcting the syntax summary for restriction of simple content in Mapping Rules for Complex Types with Simple Content (§3.4.2.2). (This change was originally made earlier, for issue 7985 explicitTimezone missing from production for simpleContent restriction but the correction seems to have been lost at some point.)

Maybe

Yes

Non breaking change.











A wording proposal which resolves issue 16786 S4S does not allow openContent without group in complex type restriction

by making the typeDefParticle model group optional in complex type restriction.

No

Yes

Non breaking change.











A wording proposal which resolves issue 16860 "Failure to resolve" in xs:include

by explicitly allowing processors to treat failure to resolve as an error for include and import. (The bug report mentions only include, but the situation is clearly analogous for import.)

Maybe

Not sure

Are any processing results normative?











A wording proposal which resolves issue 16808 Typo in 3.17.6.2

by correcting the typographic error reported there.

No

No













A wording proposal which resolves issue 16874 Change in meaning of final="#all" on elements between 1.0 and 1.1

by adding an entry to the change list recording the change made to resolve issue 3888 3.3.1 overconstraining exclusions wording?

No

No

Sounds editorial.


________________________________
This electronic message, including attachments, is intended only for the use of the individual or company named above or to which it is addressed. The information contained in this message shall be considered confidential and proprietary, and may include confidential work product. If you are not the intended recipient, please be aware that any unauthorized use, dissemination, distribution or copying of this message is strictly prohibited. If you have received this email in error, please notify the sender by replying to this message and deleting this email immediately.