Home. 
.

transparent

transparent

transparent

Altova Mailing List Archives


RE: [xml-dev] Does DTD allow deriving all possible paths in an

From: "Michael Kay" <mike@--------.--->
To: "'Liam Quin'" <liam@--.--->, <ycao5@---.--------.-->
Date: 10/13/2009 8:56:00 AM
One other point: you need to know what the root element type is. Technically
this is not part of the document type definition (=DTD), rather it is part
of the document type declaration. The two are often (understandably)
confused.

Regards,

Michael Kay
http://www.saxonica.com/
http://twitter.com/michaelhkay 
 

> -----Original Message-----
> From: Liam Quin [mailto:liam@w...] 
> Sent: 13 October 2009 01:04
> To: ycao5@s...
> Cc: xml-dev@l...
> Subject: Re: [xml-dev] Does DTD allow deriving all possible 
> paths in an XMLdocument?
> 
> On Mon, Oct 12, 2009 at 07:10:26PM -0400, ycao5@s... wrote:
> >     I have one question about XML DTD. In a paper, the authors say 
> > that DTD allows deriving all possible paths from the root to the 
> > leaves appearing in related XML documents. Does this statement 
> > correct? Based on my knowledge, DTD may not contain all possible 
> > elements in an XML document. I would like to get your 
> opinion. Thanks.
> 
> If you say that the XML document must be dtd-valid, then all 
> elements in the document must be listed (and defined) in the DTD.
> 
> A ontent model like
> <!ELEMENT mayhem ANY>
> means that "mayhem" elements may contain any elements at all 
> as children (as well as text), but for the document to be 
> valid the elemets must still be declared.
> 
> However, it is not possible to precompute all paths to leaves, because
> (1) mayhem could have any elements as children
> (2) a recursive content content model does not generate a finite
>     grammar - there's an unbounded set of possible valid input
>     documents.
> 
> e.g. <!ELEMENT doll (doll?)>
> allows
>     <doll><doll><doll /></doll></doll>
> to any depth.
> 
> These two points, ANY and cursion, are also rtue for SGML.
> 
> Liam
> 
> 
> --
> Liam Quin, W3C XML Activity Lead, 
> http://www.w3.org/People/Quin/ http://www.holoweb.net/~liam/ 
> * http://www.fromoldbooks.org/
> 
> ______________________________________________________________
> _________
> 
> XML-DEV is a publicly archived, unmoderated list hosted by 
> OASIS to support XML implementation and development. To 
> minimize spam in the archives, you must subscribe before posting.
> 
> [Un]Subscribe/change address: http://www.oasis-open.org/mlmanage/
> Or unsubscribe: xml-dev-unsubscribe@l...
> subscribe: xml-dev-subscribe@l... List archive: 
> http://lists.xml.org/archives/xml-dev/
> List Guidelines: http://www.oasis-open.org/maillists/guidelines.php
> 


_______________________________________________________________________

XML-DEV is a publicly archived, unmoderated list hosted by OASIS
to support XML implementation and development. To minimize
spam in the archives, you must subscribe before posting.

[Un]Subscribe/change address: http://www.oasis-open.org/mlmanage/
Or unsubscribe: xml-dev-unsubscribe@l...
subscribe: xml-dev-subscribe@l...
List archive: http://lists.xml.org/archives/xml-dev/
List Guidelines: http://www.oasis-open.org/maillists/guidelines.php



transparent
Print
Mail
Digg
delicious
Disclaimer
.

These Archives are provided for informational purposes only and have been generated directly from the Altova mailing list archive system and are comprised of the lists set forth on www.altova.com/list/index.html. Therefore, Altova does not warrant or guarantee the accuracy, reliability, completeness, usefulness, non-infringement of intellectual property rights, or quality of any content on the Altova Mailing List Archive(s), regardless of who originates that content. You expressly understand and agree that you bear all risks associated with using or relying on that content. Altova will not be liable or responsible in any way for any content posted including, but not limited to, any errors or omissions in content, or for any losses or damage of any kind incurred as a result of the use of or reliance on any content. This disclaimer and limitation on liability is in addition to the disclaimers and limitations contained in the Website Terms of Use and elsewhere on the site.

.
.

transparent

transparent