 |
 |
 |
Mathieu Lemoine <Swoog@l...> writes:
> Hussien Shafie, XMLmind _<hussein@p...>_
>
> Why doesn't __xsdvalid__ complain about base="xs:anyType" in:
> ---
> <xs:complexType base="xs:anyType" name="empty" />
> ---
> ?
>
> __xsdvalid__ works in 2 passes:
> [1] The XML Schema For Schemas *which is normative* is used to
> validate your schema.
> [2] __xsdvalid__ translates the XML to validation objects,
> without checking what should have been checked during first
> pass. (Yes, there is a form of bootstrapping here.)
This is a sensible architecture, but I don't understand the reply from
XML Mind -- the sForS does in fact rule out a base attribute on
xs:complexType elements, so their tool should throw it out at [1].
I've moved this discussion to xmlschema-dev, since it's not an issue
about the REC as such.
ht
--
Henry S. Thompson, HCRC Language Technology Group, University of Edinburgh
Half-time member of W3C Team
2 Buccleuch Place, Edinburgh EH8 9LW, SCOTLAND -- (44) 131 650-4440
Fax: (44) 131 650-4587, e-mail: ht@i...
URL: http://www.ltg.ed.ac.uk/~ht/
[mail really from me _always_ has this .sig -- mail without it is forged spam]
From jeffs@i... Thu Jan 27 21:31:13 2005
Received: from bart.w3
|
 | 

|  |
These Archives are provided for informational purposes only and have been generated directly from the Altova mailing list archive system and are comprised of the lists set forth on www.altova.com/list/index.html. Therefore, Altova does not warrant or guarantee the accuracy, reliability, completeness, usefulness, non-infringement of intellectual property rights, or quality of any content on the Altova Mailing List Archive(s), regardless of who originates that content. You expressly understand and agree that you bear all risks associated with using or relying on that content. Altova will not be liable or responsible in any way for any content posted including, but not limited to, any errors or omissions in content, or for any losses or damage of any kind incurred as a result of the use of or reliance on any content. This disclaimer and limitation on liability is in addition to the disclaimers and limitations contained in the Website Terms of Use and elsewhere on the site.
|  |
| |
 |
 |
 |