• From: Murali Mani <mani@C...>
• To: Peter Flynn <peter@s...>
• Date: Tue, 26 Jun 2001 10:10:17 -0700 (PDT)

Hi Peter,

I think you should not genalize it so.. This generalization might be true
often, but need not always be. It is neither a "necessary" condition nor a
"sufficient" condition for the root element to follow.

> You don't need to. The root element is always the one that
> does not appear in the content model of any other element
> type. All other elements must get mentioned somewhere else,
> but the root element never does. eg
>
> <!ELEMENT name (#PCDATA)>
> <!ELEMENT phone (#PCDATA)>
> <!ELEMENT email (#PCDATA)>
> <!ELEMENT person (name,phone,email)>
> <!ELEMENT directory (person+)>
>
> "directory" will be deduced as the root element because it
> does not appear in the content model of any other element
> type.

regards - murali.

• Follow-Ups:
  • Re: Define a root in a DTD
    • From: Peter Flynn <peter@s...>

• References:
  • Re: Define a root in a DTD
    • From: Peter Flynn <peter@s...>

• Prev by Date: Re: Define a root in a DTD
• Next by Date: 3 new XML programs (2 audio, 1 video) now playing on Technetcast
• Previous by thread: Re: Define a root in a DTD
• Next by thread: Re: Define a root in a DTD
• Index(es):
  • Date
  • Thread