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 3.10.1, Property Record: Namespace Constraint, there are two "{disallowed names}" properties prescribed. Also, in the {namespaces} definition, changing "·absent·" to "the keyword absent" would make it clearer that said keyword is intended as a candidate member of the set, rather than a possible value of the property (which of course it cannot be, since the property value is required.
About the first problem. There is an error in the configuration file that generates the spec. I've fixed it and the first {disallowed names} will (hopefully) go away in the next working draft.
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'.
A wording proposal intended to resolve this issue was sent to the XML Schema WG on 7 March 2008. http://www.w3.org/XML/Group/2004/06/xmlschema-1/structures.omni-200803b.html (member-only link). Those interested in this issue may review the proposal and are invited to comment on it.
At its telcon on 2008-03-14, the XML Schema WG adopted the wording proposal at http://www.w3.org/XML/Group/2004/06/xmlschema-1/structures.omni-200803b.html (member-only link), and believes this issue now to be resolved. Since the originator of this issue is a WG member, he is presumed to assent to this resolution of the issue. For formal purposes, however, it would be convenient if he so indicated in the usual way.
I guess this fix resolves this particular paroblem, so I'll mark it CLOSED. Note, however, that the handling of absent is still not harmonized between Part 1 and Part 2. I hope it will be, in favor of the current just-approved Part 2 version.