W3C home > Mailing lists > Public > xmlschema-dev@w3.org > September 2001

Re: Allowing empty element content

From: Henry S. Thompson <ht@cogsci.ed.ac.uk>
Date: 14 Sep 2001 12:47:05 +0100
To: Henna Ilvonen <hilvonen@lut.fi>
Cc: <xmlschema-dev@w3.org>
Message-ID: <f5bwv32m1ty.fsf@cogsci.ed.ac.uk>
Henna Ilvonen <hilvonen@lut.fi> writes:

>   I'm trying to find  a way to allow elements, which are defined to have
> content, to be empty. These elements should be also allowed to have value
> as well, because values are set after structure has been validated, so
> xsi:nil can't be used.

I'm not sure I understand what you mean by "values are set after
structure has been validated".

If you mean actually using e.g. a DOM interface to change the tree --
well, if you change the [children] property, why not change the
[attributes] property as well and set the [schema normalized value] of 
the 'xsi:nil' attribute to 'false'?

On the other hand, why isn't making the content optional sufficient
for your needs?

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 Friday, 14 September 2001 07:46:33 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 14:55:52 UTC