[XML-DEV Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message]

Re: Roots of the DTD

  • From: rbourret@d... (Ron Bourret)
  • To: xml-dev@i...
  • Date: Fri, 5 Jun 1998 11:46:59 +0200

Re: Roots of the DTD
Toby Speight wrote:

> Peter> At 17:27 04/06/98 -0400, John Cowan wrote:
> 
> >> Hmmm.  This sounds like the "root" (my syntax) or "RootElement"
> >> (Ron's syntax) attribute in XSchema is a Bad Thing.  Perhaps it
> >> should be removed?
> 
> Peter> Yup :-). I have not commented on the current proposals because
> Peter> I wanted them to anneal before public comment. *For describing
> Peter> a DTD*, here should be no requirement to define a <root> of any
> Peter> sort, only <element>, <attribute>, <contentSpec> and possibly
> Peter> <entity> and <notation> according to how people think.
> 
> I can forsee applications where one might say, "Please send me documents
> conforming to the FOO schema," in much the same way as one requests
> LaTeX or Word formats these days.  In which case, one usually needs also
> to specify the root element (this is implied in LaTeX or Word).  I don't
> see any harm in the schema having a default root (on the understanding
> that documents may, if they wish, use a different root).

A default root might fly.  Certainly a mandatory root is wrong.

In many ways, the XSchema PI is like DOCTYPE -- it points to a document 
containing the structure of your document.  As Simon suggested, it should 
therefore have a way to specify the root element, similar to the doc-type in the 
DOCTYPE declaration.

Unfortunately, these raises conflicts between DOCTYPE and the XSchema PI, since 
they are two different ways to do the same thing.  For example:

<!DOCTYPE a SYSTEM "myxschema.xsc">  // root element is a

<?XSchema myxschema.xsc a>           // root element is a

<!DOCTYPE a>
<?XSchema myxschema.xsc>             // root element is a

<!DOCTYPE a>
<?XSchema myxschema.xsc b>           // root element is ???

<!DOCTYPE a SYSTEM "myxschema.xsc">
<?XSchema yourxschema.xsc b>         // ?????

I don't like telling people they can use DOCTYPE or XSchema PIs but not both.  I 
also don't like having to write a long list of conflict resolutions -- it just 
makes XSchemas harder to use.  In both cases, it feels like we are imposing 
requirements not in the XML spec.  Ideas?

-- Ron Bourret

xml-dev: A list for W3C XML Developers. To post, mailto:xml-dev@i...
Archived as: http://www.lists.ic.ac.uk/hypermail/xml-dev/
To (un)subscribe, mailto:majordomo@i... the following message;
(un)subscribe xml-dev
To subscribe to the digests, mailto:majordomo@i... the following message;
subscribe xml-dev-digest
List coordinator, Henry Rzepa (mailto:rzepa@i...)


PURCHASE STYLUS STUDIO ONLINE TODAY!

Purchasing Stylus Studio from our online shop is Easy, Secure and Value Priced!

Buy Stylus Studio Now

Download The World's Best XML IDE!

Accelerate XML development with our award-winning XML IDE - Download a free trial today!

Don't miss another message! Subscribe to this list today.
Email
First Name
Last Name
Company
Subscribe in XML format
RSS 2.0
Atom 0.3
 

Stylus Studio has published XML-DEV in RSS and ATOM formats, enabling users to easily subcribe to the list from their preferred news reader application.


Stylus Studio Sponsored Links are added links designed to provide related and additional information to the visitors of this website. they were not included by the author in the initial post. To view the content without the Sponsor Links please click here.

Site Map | Privacy Policy | Terms of Use | Trademarks
Free Stylus Studio XML Training:
W3C Member
Stylus Studio® and DataDirect XQuery ™are products from DataDirect Technologies, is a registered trademark of Progress Software Corporation, in the U.S. and other countries. © 2004-2013 All Rights Reserved.