Lists Home |
Date Index |
Ray Tayek <firstname.lastname@example.org> writes:
> At 02:34 PM 4/22/03 +0100, Henry S. Thompson wrote:
> >Ray Tayek <email@example.com> writes:
> > > At 11:41 PM 4/7/03 -0700, you wrote:
> > > >At 02:48 PM 4/7/03 -0700, Jeff Lowery wrote:
> > > >>The schema you have looks sufficient. Unless you have content="mixed" in
> > > >>the complexType definitions, it won't allow text nodes in the element.
> > > >
> > > >oh, great! looks like i did the right thing by accident :)
> > >
> > > or almost. using the .xsd and .xml files below (the same as before i
> > > think) which has no content="mixed" in it, with a hacked up version
> > > of the traverse program from harold's book, i get stuff like: "
> > > \n\t\t\t" i.e. space, line-feed, and some tabs ...
> > > ...
> > > looks like the pretty printing is getting me. but the xml file
> > > validates against the schema (using xmlspy).
> >Not sure what your question is, but XMLSpy is correct here -- W3C XML
> >Schema, as XML 1.0 DTDs, allows whitespace between the elements
> >governed by an element-only content model.
> ok, so it is valid legal as it stands.
> my question is: is there a way to write the schema or use a later
> verson of xml or xmlschema in such a way as to ignore this white space
> or consider it not to be an element. i can probably hack it with code
> by seeing if it contains no non-space characters, but it would be nice
> if jdom would not consider this to be a text element.
That's a JDOM issue, not a schema issue, as far as I can see.
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: firstname.lastname@example.org
[mail really from me _always_ has this .sig -- mail without it is forged spam]