OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

 


 

   Requirement for attributes with schema scope

[ Lists Home | Date Index | Thread Index ]
  • From: "Arnold, Curt" <Curt.Arnold@hyprotech.com>
  • To: "'xml-dev@ic.ac.uk'" <xml-dev@ic.ac.uk>, "'www-xml-schema-comments@w3.org'" <www-xml-schema-comments@w3.org>
  • Date: Thu, 6 Jan 2000 14:59:20 -0700

Section 2.5 of Structures says:

Attributes and local element declarations are special, in that every type defines its own attribute symbol space and local element symbol space, which are distinct from each other. In addition,
top-level elements (whose declarations are not contained within a type definition) reside in their own symbol space.  And the Schema for Schema only allows attribute declarations to appear within the
scope of a type or attributeGroup.

However, you can use the <anyAttribute> element to say that an element in this namespace can have any attribute from an alien namespace.  However, without being able to have an attribute with schema
scope, how do you know which declaration of a given attribute should be used for validation.  For example,

Schema for ThisNamespace:

<schema xmlns="http://www.w3.org/1999/XMLSchema"
 	  targetNamespace="http://www.software.aeat.com/ThisNamespace">

	<element name="someElement">
		<anyAttribute>http://www.software.aeat.com/ThatNamespace</anyAttribute>
	</element>
</schema>

Schema for ThatNamespace:

<schema xmlns="http://www.w3.org/1999/XMLSchema"
 	  targetNamespace="http://www.software.aeat.com/ThatNamespace">

	<element name="coffee">
		<attribute name="temp">
			<datatype>
				<enumeration value="Hot"/>
				<enumeration value="Tepid"/>
			</datatype>
		</attribute>			
	</element>

	<element name="employee">
		<!--  is this employee a temporary  -->
		<attribute name="temp" type="boolean"/>
	</element>
</schema>

Sample Document:

<!--  that:temp is ambiguous, 
	should it be the employee status or the coffee temperature -->
<someElement xmlns="http://www.software.aeat.com/ThisNamespace"
		 xmlns:that=http://www.software.aeat.com/ThatNamespace"
		 that:temp="false"
</someElement>

Resolution:

Attribute declarations need to be able to appear in the scope of a <schema> element.  To allow reuse, <attribute> should also have a ref attribute so that global scoped attributes can appear in a
element without a duplicate definition.  Only attributes with a schema scope should be used to resolve namespace qualified attributes.

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






 

News | XML in Industry | Calendar | XML Registry
Marketplace | Resources | MyXML.org | Sponsors | Privacy Statement

Copyright 2001 XML.org. This site is hosted by OASIS