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's not currently defined that unknown attributes in the vc: namespace are erronous, so misspelling an attribute name such as vc:typesUnavailable is likely to be troublesome to diagnose, because the attribute will simply be ignored. I propose adding to Schema Representation Constraint: Conditional Inclusion Constraints the rule: Any attribute that appears on an element information item in a ·schema document·, and whose name is in the schema versioning namespace, MUST have the local name minVersion, maxVersion, typeAvailable, typeUnavailable, facetAvailable, or facetUnavailable.
<MSM> proposed amendment: for MUST read SHOULD, <MSM> and add a Note saying (roughly) "This is a SHOULD in order to preserve the ability of future versions of this spec to add new attributes to the namespace. <MSM> Processors are encouraged to issue warnings about attributes other than those named, but it is not, strictly speaking, an error."
A change proposal intended to resolve this issue (and others) was adopted by the XML Schema WG on 5 September 2008. http://www.w3.org/XML/Group/2004/06/xmlschema-1/structures.b5904etc.html Accordingly, I am marking the issue RESOLVED. Michael, as the originator of the issue, you can indicate your assent to the disposition of the issue by closing it, or your opposition to the disposition by reopening the issue. If we don't hear from other in two weeks, we'll assume you are content. Thank you.