This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
+++ This bug was initially created as a clone of Bug #2311, to track the problem for XSD 1.0 +++ AFAIK attribute prohibitions (use="prohibited") are only significant when restricting a type; i.e. when they appear as children of <restriction> and <complexType>. Any other occurrences of such prohibitions should be pointless, but there's no consensus between various schema processors. An explicit statement about where prohibitions are pointless could be of help here. Generating a warning when we hit such pointless prohibitions would deminish confusion on the schema authors side.