I believe that this is a spec usability issue. To understand this, users must read - Attribute Decl Schema Component (section 3.2.1) - XML Representation of Attribute Decl (section 3.2.2) - Constraints on XML Representation of Attribute Decl (section 3.2.3) ... - And, Schema for Schemas (Appendix A) before they can compose a valid schema. Many users bumped into the same issue. Asir -----Original Message----- From: www-xml-schema-comments-request@w3.org [mailto:www-xml-schema-comments-request@w3.org]On Behalf Of Henry S. Thompson Sent: Friday, June 07, 2002 4:19 AM To: asirv@webmethods.com Cc: www-xml-schema-comments@w3.org Subject: Re: topLevelAttribute and use=(optional|prohibited|required) "Asir S Vedamuthu" <asirv@webmethods.com> writes: > attribute 'use' is ruled out [in sForS] > > <xs:attribute name="use" use="prohibited"/> > > However, prose in section 3.2.3 (constraints on XML Representation) doesn't > say a word about 'use' attribute. The Constraints on XML Repr never duplicate what's in the sForS -- it's normative. ht -- Henry S. Thompson, HCRC Language Technology Group, University of Edinburgh W3C Fellow 1999--2002, part-time member of W3C Team 2 Buccleuch Place, Edinburgh EH8 9LW, SCOTLAND -- (44) 131 650-4440 Fax: (44) 131 650-4587, e-mail: ht@cogsci.ed.ac.uk URL: http://www.ltg.ed.ac.uk/~ht/ [mail really from me _always_ has this .sig -- mail without it is forged spam]Received on Friday, 14 June 2002 09:57:47 GMT
This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 23 October 2007 06:13:30 GMT