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

Re: Forcing a certain document element

From: Martin J. Duerst <duerst@w3.org>
Date: Mon, 15 Jan 2001 10:01:40 +0900
Message-Id: <4.2.0.58.J.20010115100010.04096b20@sh.w3.mag.keio.ac.jp>
To: ht@cogsci.ed.ac.uk (Henry S. Thompson), Eric van der Vlist <vdv@dyomedea.com>
Cc: Ian Stokes-Rees <ian@decisionsoft.com>, "xmlschema-dev@w3.org" <xmlschema-dev@w3.org>
At 01/01/12 18:16 +0000, Henry S. Thompson wrote:
>Eric van der Vlist <vdv@dyomedea.com> writes:
>
> > "Henry S. Thompson" wrote:
> > >
> > > You can't use the XML Schema language itself to enforce this, just as
> > > you can't say it in a DTD document.  The XML Schema WG has taken on
> > > board a request that it be a requirement on XML Schema _processors_
> > > that they can be invoked in a way which specifies the element
> > > declaration to be used to validate the document element.
> >
> > Can't you design your schema to have only one global element definition
> > ?
> >
> > I reckon that it's a severe constraint, but it could be a workaround if
> > you really wanted/needed to achieve this...
>
>In the words of Richard Nixon (allegedly :-) "You could do that, but
>it would be wrong."  By which I mean you're right, if you wrote such a
>schema, it would have the desired effect, but that's a pretty
>roundabout way to get it.

I agree with this. However, this does not mean that it is wrong to
be able to (easily, and for some cases, in the Schema itself) to
express what top level element(s) can actually be used, or does it?


Regards,   Martin.
Received on Sunday, 14 January 2001 20:22:02 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 11 January 2011 00:14:19 GMT