5730 2008-06-06 13:17:34 +0000 Appendix C includes undefined constraints 2009-04-20 21:26:11 +0000 1 1 1 Unclassified XML Schema Structures: XSD Part 1 1.1 only PC Windows XP CLOSED WORKSFORME resolved P2 normal CR 1 sandygao cmsmcq cmsmcq David_E3 www-xml-schema-comments oldest_to_newest 20398 0 sandygao 2008-06-06 13:17:34 +0000 Appendix C lists all constraints defined in both Structures and Datatypes. There seem to be a few constraints listed there but not defined in either part. For example, there are entries like cvc-lexicalMapping-representation-valid Lexical Representation Valid against lexicalMappings facet and lexicalMapping-valid-restriction lexicalMappings valid restriction 24642 1 cmsmcq 2009-04-10 04:00:21 +0000 I think this phenomenon is limited to drafts prepared in the source directories. The parts of appendix C select all the constraint notes in the version of the datatypes spec corresponding to the structures spec being generated (status quo, diff against 1.0, diff against previous WD). In the source directories, this causes all the constraint notes in the source file datatypes.xml to be selected, which includes constraints long since deleted from the spec. In the publication directories, however, the source file containing all versions and the status quo source file containing only 'live' text are distinguished (as datatypes.source.xml and datatypes.xml respectively). It is for this reason (I believe) that the status quo document for structures does not contain the ghost constraints mentioned in comment 0. If I am right (others should certainly check this!) we should close this bug report as WORKSFORME. 24802 2 David_E3 2009-04-17 16:49:21 +0000 5730: Appendix C includes undefined constraints made in Bugzilla. Summary: glitch in editorial system; fixed. MSM's recommendation: Quick. Close as WORKSFORME (but someone needs to say they have confirmed that it's fixed.) 24869 3 sandygao 2009-04-20 21:25:58 +0000 During its 2009-04-17 telecon, the schema WG confirmed the observation made in comment #1 and decided to resolved this issue without any change. As the reporter of this issue, I'm marking it RESOLVED and CLOSED accordingly.