W3C home > Mailing lists > Public > www-xml-schema-comments@w3.org > January to March 2008

[Bug 5466] Point out the cases where attribute prohibitions are pointless

From: <bugzilla@wiggum.w3.org>
Date: Fri, 08 Feb 2008 20:08:00 +0000
CC:
To: www-xml-schema-comments@w3.org
Message-Id: <E1JNZVw-0000oD-Gc@wiggum.w3.org>

http://www.w3.org/Bugs/Public/show_bug.cgi?id=5466

           Summary: Point out the cases where attribute prohibitions are
                    pointless
           Product: XML Schema
           Version: 1.0 only
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: minor
          Priority: P2
         Component: Structures: XSD Part 1
        AssignedTo: cmsmcq@w3.org
        ReportedBy: cmsmcq@w3.org
         QAContact: www-xml-schema-comments@w3.org
 BugsThisDependsOn: 2311


+++ 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.
Received on Friday, 8 February 2008 20:08:09 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Sunday, 6 December 2009 18:13:13 GMT