W3C home > Mailing lists > Public > xmlschema-dev@w3.org > January 2001

Possible XSV bug - failure to report namespace errors with import

From: <MarkH@i2.co.uk>
Date: Fri, 5 Jan 2001 17:01:09 -0000
Message-ID: <1E73B637CFC3D411A12F00B0D0795DDD09147A@uknts40exh01.i2.co.uk>
To: xmlschema-dev@w3.org
XML Spy 3.5 beta 3 complains, but XSV does not - see bug report to XML Spy
and reply below. I think he's right. Changing my namespace refs to be
consistent fixes the XML Spy validation errors.

Thanks

Mark
--
Mark Hughes
  Agile HTML Editor
    http://www.agilic.com

-----Original Message-----
From: Gavrielov, Vladislav [mailto:va@altova.com]
Sent: 05 January 2001 15:35
To: 'MarkH@i2.co.uk'
Subject: RE: XML Spy v3.5 beta 3 bug: undefined types when using import

Your schema has two bugs: 
1. You are using in imported schema namespace 
<http://www.i2group.com/Schemas/2001-01-01/VLVXSchema> 
but trying to address it with a prefix "vlvx" with 
<http://www.i2group.com/Schemas/2001-01-01/VLVXSchemaTypes> 
2. import statement has to use a namespace name and not prefix "vlvx" 
Best regards, 
Vladislav Gavrielov 
... Altova GmbH - The XML Spy Company 
... Vladislav Gavrielov 
... President, CTO 
========================================================================= 
XML Spy 3.0 - the first true Integrated Development Environment for XML 
Visit <http://www.xmlspy.com/> to download a free 30-day evaluation version 
========================================================================= 
-----Original Message----- 
From: MarkH@i2.co.uk [<mailto:MarkH@i2.co.uk>] 
Sent: Freitag, 05. Jšnner 2001 16:20 
To: support@xmlspy.com 
Cc: markh@i2.co.uk 
Subject: XML Spy v3.5 beta 3 bug: undefined types when using import 
XSV 1.173/1.80 of 2000/10/18 15:54:58 reports NO ERRORS validating the 
following schema. 
XML Spy v3.5 beta 3 reports errors relating to undefined types vlvx:topType 
and vlvx:derivedFromTopType. 
Is this a bug? 
Thanks 
Mark 
-- 
Mark Hughes 
Agile HTML Editor 
<http://www.agilic.com> 
================ FILE: types-test.xsd ================== 
<?xml version="1.0"?> 
<schema 
targetNamespace="<http://www.i2group.com/Schemas/2001-01-01/VLVXSchemaTypes>
" 
xmlns:vlvx="<http://www.i2group.com/Schemas/2001-01-01/VLVXSchemaTypes>" 
xmlns="<http://www.w3.org/2000/10/XMLSchema>"> 
<import namespace="vlvx" schemaLocation="imported-schema.xsd"> 
<annotation> 
<documentation> 
imported-schema.xsd defines a top level complexType 'topType' 
</documentation> 
</annotation> 
</import> 
<element name="newdoc"> 
<complexType> 
<sequence> 
<element name="thing1" 
type="vlvx:derivedFromTopType"> 
<annotation> 
<documentation> 
No errors here, cos derivedFromTopType is resolved. 
</documentation> 
</annotation> 
</element> 
<element name="thing2" 
type="vlvx:derivedFromTopType"> 
<annotation> 
<documentation> 
XML Spy 3.5 beta 3 complains that vlvx:topType is undefined. (Same 
happens if I use type='topType'). 
</documentation> 
</annotation> 
</element> 
</sequence> 
</complexType> 
</element> 
<complexType name="derivedFromTopType"> 
<annotation> 
<documentation>No errors here, so we are seeing 
topType</documentation> 
</annotation> 
<complexContent> 
<extension base="vlvx:topType"> 
<sequence/> 
</extension> 
</complexContent> 
</complexType> 
</schema> 
================ FILE: imported-schema.xsd ================== 
<?xml version="1.0"?> 
<schema 
targetNamespace="<http://www.i2group.com/Schemas/2001-01-01/VLVXSchema>" 
xmlns:vlvx="<http://www.i2group.com/Schemas/2001-01-01/VLVXSchema>" 
xmlns="<http://www.w3.org/2000/10/XMLSchema>"> 
<complexType name="topType"> 
<attribute name="format" type="CDATA" use="required"/> 
</complexType> 
</schema> 
=== END === 
Received on Friday, 5 January 2001 12:08:11 GMT

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