- From: Henry S. Thompson <ht@cogsci.ed.ac.uk>
- Date: 28 Mar 2001 11:08:55 +0100
- To: "Jeff Rafter" <jeffrafter@definedweb.com>
- Cc: "Eddie Robertsson" <eddie@allette.com.au>, <xmlschema-dev@w3.org>
Well, there's one xsv bug here, but also some misunderstandings.
"Jeff Rafter" <jeffrafter@definedweb.com> writes:
> Eddie,
>
> Wow, I am so glad to hear I am not the only one-- I was getting worried <g>.
> Well I did some more digging (and a couple more samples) and seem to have
> found some success.
>
> The first set does not work (as described earlier), uses xs: as the schema
> prefix (which is the default) and has no DOCTYPE:
>
> http://xml.definedsys.com/schema/instance.xml
> http://xml.definedsys.com/schema/element.xml
> http://xml.definedsys.com/schema/children.xml
That's an XSV bug, I'll fix ASAP. It was the cause of Eddie's problem
as well.
> The second set does not work, uses "" as the schema prefix and has no
> DOCTYPE
>
> http://xml.definedsys.com/schema/instance2.xml
> http://xml.definedsys.com/schema/element2.xml
> http://xml.definedsys.com/schema/children2.xml
That's your bug -- children2.xml is not a valid schema, it's got a
bogus element in it.
> The third set *does* work, uses "" as the schema prefix and has a DOCTYPE.
> (By working I mean children3.xml correctly raises an error when validating)
>
> http://xml.definedsys.com/schema/instance3.xml
> http://xml.definedsys.com/schema/element3.xml
> http://xml.definedsys.com/schema/children3.xml
<snip/>
Sorry for the inconvenience. It should _not_ be the case that XSV
requires a DOCTYPE.
ht
--
Henry S. Thompson, HCRC Language Technology Group, University of Edinburgh
W3C Fellow 1999--2001, part-time member of W3C Team
2 Buccleuch Place, Edinburgh EH8 9LW, SCOTLAND -- (44) 131 650-4440
Fax: (44) 131 650-4587, e-mail: ht@cogsci.ed.ac.uk
URL: http://www.ltg.ed.ac.uk/~ht/
Received on Wednesday, 28 March 2001 05:09:03 UTC