W3C home > Mailing lists > Public > xmlschema-dev@w3.org > December 2000

[XSV bug] Namespaces ignored in <appinfo>

From: Ed Staub <estaub@kana.com>
Date: Wed, 20 Dec 2000 13:44:56 -0500
Message-ID: <B7EE31F81D42D41197D200D0B74D4AE101A21F01@mht-ex1.silknet.com>
To: "'xmlschema-dev@w3.org'" <xmlschema-dev@w3.org>
I believe I've run into a small bug in
XSV 1.173/1.80 of 2000/10/18 15:54:58.

Here's a sample piece of schema:


<xsd:schema xmlns:xsd="http://www.w3.org/2000/10/XMLSchema"
xmlns:kdo="http://www.kana.com/ns/KDOSchema" elementFormDefault="qualified">

...
			<xsd:all>
				<xsd:element name="jobTitle" minOccurs="0">
					<xsd:annotation>
						<xsd:appinfo>

							<kdo:element>
								<kdo:label
locale="ENUS">job Title</kdo:label>
							</kdo:element>

						</xsd:appinfo>
						<xsd:documentation>job
Title</xsd:documentation>
					</xsd:annotation>
					<xsd:simpleType>
						<xsd:restriction
base="xsd:string">
							<xsd:maxLength
value="50"/>
						</xsd:restriction>
					</xsd:simpleType>
				</xsd:element>
				...


When I use a schema which includes the <kdo:element> elements within appinfo
to validate another document, I receive complaints from the validator:

	file:///c:\DlgStudio\Schema\StaffSchema.xsd:25:8: Invalid: element
with no name or ref

My guess is that the namespace is not being observed, and hence XSV thinks
this is a <xsd:element>.


Henry and Richard:  Thanks for the nice validator!


-Ed Staub
Kana Communications, Inc.
Received on Wednesday, 20 December 2000 13:45:33 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 11 January 2011 00:14:19 GMT