2835 2006-02-11 01:42:05 +0000 RQ-121 Clarify behavior for attributes that are both fixed and prohibited (prohibited-and-fixed) 2007-04-16 16:17:42 +0000 1 1 1 Unclassified XML Schema Structures: XSD Part 1 1.1 only Other All RESOLVED FIXED medium, work needsDrafting P3 normal --- 2176 1 cmsmcq cmsmcq www-xml-schema-comments oldest_to_newest 8200 0 cmsmcq 2006-02-11 01:42:06 +0000 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. 12997 1 sandygao 2006-11-22 05:24:09 +0000 Proposal: to add a new clause to "Attribute Declaration Representation OK" "If fixed and use are both present, use must not have the ·actual value· prohibited." Resolution: adopted at 2006-10-17 telecon.