This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
It would be helpful if constraints were enumerated into their various cases via document headings as much as possible. One case where additional splitting into sections would be helpful is "Schema Component Constraint: Derivation Valid (Extension) (s3.4.6)". This could be split into: "Schema Component Constraint: Derivation Valid (Extension, Complex base)" consisting of the clause 1 text, and "Schema Component Constraint: Derivation Valid (Extension, Simple base)" consisting of the clause 2 text. I think this would make it much easier to find what you are looking for. They may be other cases where such splits are beneficial. If appropriate, I can look through the spec and make suggestions.
There appear to be 5 constraints that are organized in this fashion and might be split in the way described. The editorial team is not certain that this is the best or most general way to clarify the constraints, but will consider the suggestion during their work, and will provide wording to the WG if they see fit.
In an effort to make better use of Bugzilla, we are going to use the 'severity' field to classify issues by perceived difficulty. This bug is getting severity=minor to reflect the existing whiteboard note 'easy'.
In August and September 2009 the XML Schema working group performed triage on the remaining open issues in a WBS poll [1], whose results are summarized at [2] and accepted formally at [3]. In the course of that triage we decided, with some regret, to close this issue without further action. We just aren't going to get this done in the time available to us, and we do not believe the issue is critical enough to warrant delaying the spec to address it. The editors agree that in principle it's a good idea; we just didn't get it done. Pete, as the originator of the issue, you are requested to consider whether you are content with this disposition of the issue or not. If you are willing to live with it, please so indicate by closing the issue. You can reopen the issue to indicate the opposite, that you are not willing to acquiesce in this disposition and wish to push back. If we don't hear from you in the next two weeks we will assume that you are content. [1] http://www.w3.org/2002/09/wbs/19482/200908CRissues/ [2] http://lists.w3.org/Archives/Member/w3c-xml-schema-wg/2009Sep/0005.html [3] http://lists.w3.org/Archives/Member/w3c-xml-schema-ig/2009Sep/att-0005/2009-09-11telcon.html#item04 (all links member-only)