This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
In the non-diff edition of Part 2 (20 June 2008), section 4.1.1 has two definitions of the {final} property of the simpleType component; in the diff edition, the first of these is marked as deleted text.
Thanks for the comment; will find the cause and fix.
This problem is still present in the Jan 2009 draft.
Short analysis: a typo was allowing the stylesheet templates which create the HTML display to believe that Simple Type Definition has a 'final' property (duly displayed) in addition to a 'final ' property inherited from Type Definition. This is now believed to be fixed in (a) the XML source and (b) the status-quo documents pointed to from the editorial pointers page at http://www.w3.org/XML/Group/2004/06/xsd-ed-pointers.html (member-only link). Calmer eyes than mine should verify that the problem has indeed been repaired before the issue is closed. ......................... Longer story (I apologize for the wordy exculpations which follow, but I feel the need for some record of how I spent the last hour and why a one-keystroke fix took so long to make. Otherwise it might be [even more] embarrassing.) The problem appears to have been caused by a stray blank in the name of the 'final' property on the (internal) XML representation of the type definition component. The display routines responsible for checking to see whether it had been overridden by the XML element representing Simple Type Definition components were deceived by this -- they had seen a local definition of a 'final' property, but not of a 'final ' property. Diagnosis was complicated by the fact that the same extra trailing blank was present in the deleted copy of the property description, so that the diff against 1.0 correctly showed two final properties, one ('final ') deleted and one ('final') added. This made it look as if there were a problem with the handling of diff markup in the component descriptions, or (oh, the horror) with the way the makefile handles the dependencies among the component definitions file and its various diff-processed derivates. Moral of the story: don't make typos?
>Moral of the story: don't make typos? One might ask whether the error couldn't have been caught by doing more aggressive schema validation of the source documents?
5782: Definition of simpleType.{final} Summary: in the LC draft, simpleType seems to have both a {final} and a {final } property. Fix has been reported in Bugzilla. (Silent repair of typo in XML source.)
The current SQ document generates corrrectly, so I am marking this bug FIXED. Mike Kay: I expect that you are satisfied, so please mark this bug CLOSED; but if you are not satisfied, please mark the bug REOPENED. The WG needs this response ASAP; preferably before the 24 Apr telecon.