[Bug 2835] RQ-121 Clarify behavior for attributes that are both fixed and prohibited (prohibited-and-fixed)

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

           Summary: RQ-121 Clarify behavior for attributes that are both
                    fixed and prohibited (prohibited-and-fixed)
           Product: XML Schema
           Version: 1.1 only
          Platform: Other
        OS/Version: All
            Status: NEW
          Keywords: needsDrafting
          Severity: normal
          Priority: P2
         Component: Structures: XSD Part 1
        AssignedTo: ht@w3.org
        ReportedBy: cmsmcq@w3.org
         QAContact: www-xml-schema-comments@w3.org


This issue was originally reported by Stanley Guan, Ashok Malhotra.

Clarify the expected processor behavior if an attribute has both
use="prohibited", and a fixed value specified.

Should a schema validator:

* silently ignore fixed, or
* flag "attribute fixed and prohibited" as an error

See (member-only link)
http://lists.w3.org/Archives/Member/w3c-xml-schema-ig/2002Sep/0122.html
(http://lists.w3.org/Archives/Member/w3c-xml-schema-ig/2002Sep/0122.html).

This item was discussed in the meeting of 2003-10-24
(http://lists.w3.org/Archives/Member/w3c-xml-schema-ig/2003Oct/0085.html)

This item was discussed in the meeting of 2003-11-21
(http://lists.w3.org/Archives/Member/w3c-xml-schema-ig/2003Nov/0050.html).
Let "prohibited" win? Treat as error on component?  Handle
symmetrically with type?  Need to make sure we handle possible
re-introduction of attributes prohibited in the base.  Need a phase-1
proposal.

This item was discussed, and phase-1 agreement was reached, in the
meeting of 2004-03-25
(http://lists.w3.org/Archives/Member/w3c-xml-schema-ig/2004Mar/0133.html).

According to the requirements document, phase-1 agreement has been reached.

Received on Saturday, 11 February 2006 01:42:12 UTC