XSV - possible bug with XSV type checking

Not sure if this is a bug with XSV or a misapprehension on my part, but if I validate a schema with lines like:
   <xsd:attribute name="id"                  type="xsd:ForceBreak"  use="required" />
   <xsd:attribute name="year"           type="xsd:integer"  use="required" />

I would expect a failure because I wouldn't expect [type="xsd:ForceBreak"] to be acceptable because it is not an xsd: type.
This came to light when I had a schema that contained  type="xsd:real", which another tool (Xerces?) did not like (quite rightly by my interpretation of XML Schema spec).

So I would be interested in knowing whether this is a bug or a known behaviour that has a sensible reason behind it. If the latter, it might be worth posting something with the XSV to explain it.

thanks

Ian Mockford




*******************************************************************************
This email and any files transmitted with it are intended solely for the use of
the individual or entity to whom they are addressed and may not be divulged to
any third party without the express permission of the originator.  Any views
expressed in this message are those of the individual sender, except where the
sender specifically states them to be the views of Thales Research Ltd.

Following the acquisition of Racal Electronics plc by Thomson-CSF, please note
that our new name is Thales Research Ltd.  For more information regarding the
Thales Group (formerly Thomson-CSF) please see our website www.Thalesgroup.com
*******************************************************************************