- From: Jeff Rafter <jeffrafter@definedweb.com>
- Date: Wed, 28 Mar 2001 08:08:04 -0800
- To: "Henry S. Thompson" <ht@cogsci.ed.ac.uk>
- Cc: <xmlschema-dev@w3.org>
Henry, thanks for the clarifications... [snip] > > 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. Are you referring to the "error" element? If so, that was intentional-- I was trying to get XSV to tell me it was bogus. It unfortunately did not give me that error-- in fact, from what I saw it never got to children2.xml at all. I rewrote the second example with a (hopefully) error-less children.xml http://xml.definedsys.com/schema/instance4.xml http://xml.definedsys.com/schema/element4.xml http://xml.definedsys.com/schema/children4.xml And it still gives the same warning: Warning: The attribute xmlns of element schema does not match the declared #FIXED value in unnamed entity at line 3 char 43 of http://xml.definedsys.com/schema/element4.xml Error: can't retrieve "http://xml.definedsys.com/samples": 302 Object Moved I have tried to decipher what is going on here but haven't quite figured out what is going on in the background... I suppose I need to take some lessons in Python. > Sorry for the inconvenience. It should _not_ be the case that XSV > requires a DOCTYPE. Inconvenience? Ha! These are small, small problems in moving to the latest version of an invaluable *free* tool-- no apology necessary-- whatsoever. Regards, Jeff Rafter
Received on Wednesday, 28 March 2001 11:07:52 UTC