This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 5466 - Point out the cases where attribute prohibitions are pointless
Summary: Point out the cases where attribute prohibitions are pointless
Status: RESOLVED FIXED
Alias: None
Product: XML Schema
Classification: Unclassified
Component: Structures: XSD Part 1 (show other bugs)
Version: 1.0 only
Hardware: All All
: P2 minor
Target Milestone: ---
Assignee: C. M. Sperberg-McQueen
QA Contact: XML Schema comments list
URL:
Whiteboard:
Keywords:
Depends on: 2311
Blocks:
  Show dependency tree / graph
 
Reported: 2008-02-08 20:08 UTC by C. M. Sperberg-McQueen
Modified: 2010-03-16 18:41 UTC (History)
1 user (show)

See Also:

Attachments

Description C. M. Sperberg-McQueen 2008-02-08 20:08:00 UTC 
+++ 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.