Altova Mailing List Archives

Re: Requirement for attributes with schema scope

From: ht@------.--.--.-- (----- -. --------)
To: "Arnold, Curt" <Curt.Arnold@---------.--->
Date: 1/7/2000 10:47:00 AM
"Arnold, Curt" <Curt.Arnold@h...> writes:

> [Comments on qualified attributes in instances, and a proposal for
>  top-level attribute declarations which can be 'ref'ed]

Something along these lines has been considered, and it's not out of
the question that it may happen.

For the time being, the only schema-valid way to introduce an
attribute from other than the namespace partition scoped to the
containing element is by way of an attribute GROUP from another
namespace, e.g.

   . . .
   <attributeGroup ref='foo:baz'/>

See the schema for schemas [1] for an example of how this is done, wrt


  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@c...

xml-dev: A list for W3C XML Developers. To post, mailto:xml-dev@i...
Archived as: and on CD-ROM/ISBN 981-02-3594-1
To unsubscribe, mailto:majordomo@i... the following message;
unsubscribe xml-dev
To subscribe to the digests, mailto:majordomo@i... the following message;
subscribe xml-dev-digest
List coordinator, Henry Rzepa (mailto:rzepa@i...)


These Archives are provided for informational purposes only and have been generated directly from the Altova mailing list archive system and are comprised of the lists set forth on Therefore, Altova does not warrant or guarantee the accuracy, reliability, completeness, usefulness, non-infringement of intellectual property rights, or quality of any content on the Altova Mailing List Archive(s), regardless of who originates that content. You expressly understand and agree that you bear all risks associated with using or relying on that content. Altova will not be liable or responsible in any way for any content posted including, but not limited to, any errors or omissions in content, or for any losses or damage of any kind incurred as a result of the use of or reliance on any content. This disclaimer and limitation on liability is in addition to the disclaimers and limitations contained in the Website Terms of Use and elsewhere on the site.