- From: Arnold, Curt <Curt.Arnold@hyprotech.com>
- Date: Fri, 7 Jan 2000 12:33:04 -0700
- To: "'ht@cogsci.ed.ac.uk'" <ht@cogsci.ed.ac.uk>
- Cc: "'xml-dev@ic.ac.uk'" <xml-dev@ic.ac.uk>, "'www-xml-schema-comments@w3.org'" <www-xml-schema-comments@w3.org>
And some approach that allowed us to have "schema-scoped" attributes would allow us to validate. Maybe a less disruptive approach would be to allow a scope attribute on a attribute declaration. Something like: <element name="coffee"> <attribute name="temp" scope="schema"> ... where scope would be an enumation of "schema" and "element" (with element as the default) and it would be an error to have two identically named attributes with schema scope within the same schema element. -----Original Message----- From: ht@cogsci.ed.ac.uk [mailto:ht@cogsci.ed.ac.uk] Sent: Friday, January 07, 2000 1:17 PM To: Arnold, Curt Cc: 'xml-dev@ic.ac.uk'; 'www-xml-schema-comments@w3.org' Subject: Re: Requirement for attributes with schema scope "Arnold, Curt" <Curt.Arnold@hyprotech.com> writes: > Are you saying that <anyAttribute> has been removed from subsequent WG > documents and the point is moot. Sorry, you're absolutely right, e.g. <anyAttribute namespace="##other"/> will allow, but not know how to validate, attributes with qualified names in instances. My remarks should have begun "the only schema-valid way to introduce _and validate_ an attribute from other than the namespace partition scoped to the containing element is . . . " ht -- Henry S. Thompson, HCRC Language Technology Group, University of Edinburgh 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/
Received on Friday, 7 January 2000 14:35:22 UTC