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

Possible bug in XSV/XML Spy 3.5 beta 3... missed validation error

From: <MarkH@i2.co.uk>
Date: Thu, 4 Jan 2001 17:53:36 -0000
Message-ID: <1E73B637CFC3D411A12F00B0D0795DDD09146D@uknts40exh01.i2.co.uk>
To: xmlschema-dev@w3.org, support@xmlspy.com
<?xml version='1.0'?>
<schema  xmlns='http://www.w3.org/2000/10/XMLSchema'
xmlns:vlvx='http://www.i2group.com/2001-01-01/VLVXSchema'
targetNamespace='http://www.i2group.com/2001-01-01/VLVXSchema'>

<complexType name='elementPropertyType'>
 <annotation>
  <documentation>Generic string property (name/value) on
element</documentation>
 </annotation>
      <attribute name='name' type='string' use='required'/>
      <attribute name='value' type='string' use='required'/>
</complexType>

<complexType name='displayNamePropertyType'>
 <annotation>
  <documentation>Generic string property (name/value) on
element</documentation>
 </annotation>
 <simpleContent>
  <restriction base='vlvx:elementPropertyType'>
      <attribute name='name' type='string' use='required'
value='displayName'/>
  </restriction>
 </simpleContent>
</complexType>

Validating with XSV 1.173/1.80 of 2000/10/18 15:54:58 says everything is
fine. 

Validation with XML Spy v3.5 beta 3 normally says its ok too - unless you
modify the document externally and cause XML Spy to revalidate when it
regains application focus. It then complains that simpleContent cannot have
a base (vlvx:elementPropertyType) that is a complexType with complexContent.

Who's right here? XML Spy is showing at least one bug here (reporting a
validation error intermittently). But is XSV right to allow the above?

Mark
--
Mark Hughes
  Agile HTML Editor
    http://www.agilic.com
Received on Thursday, 4 January 2001 13:00:29 GMT

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