• From: David Carlisle <davidc@n...>
• To: =?UTF-8?B?TWFpayBTdMO8aHJlbmJlcmc=?= <maik.stuehrenberg@u...>
• Date: Mon, 31 Jan 2011 14:32:27 +0000

On 31/01/2011 14:22, Maik Stührenberg wrote:

> But when in mixed content models duplicate types are not allowed -- why
> are they allowed in element content models? The additional #PCDATA of a
> mixed content model should have only little effect on the question of
> determinism, or do I forget anything (maybe the whitespace characters
> that are allowed...)?


If there is a #PCDATA token you can't use , or ? in dtd only 
(#PCDATA|a|b|c)* and the deterministic content model rule explictly only 
applies to element content.

http://www.w3.org/TR/xml/#sec-element-content



> But your declaration is (of course) accepted by the parser because it is
> non-ambiguous. However, the question remains: why is the original

the requirement to check that teh content model is deterministic os 
marked as "an error"
http://www.w3.org/TR/xml/#dt-compat
for compatibility (with SGML)

"an error" is not "fatal error" and so formally it means that the dtd is 
in error but a system isn't obliged to report that. It may make it an 
error, or may just give a warning, or may just work.

David

________________________________________________________________________
The Numerical Algorithms Group Ltd is a company registered in England
and Wales with company number 1249803. The registered office is:
Wilkinson House, Jordan Hill Road, Oxford OX2 8DR, United Kingdom.

This e-mail has been scanned for all viruses by Star. The service is
powered by MessageLabs. 
________________________________________________________________________

• Follow-Ups:
  • Re: DTD vs XSD: No Duplicate Types in (Mixed) Content Models
    • From: =?UTF-8?B?TWFpayBTdMO8aHJlbmJlcmc=?= <maik.stuehrenberg@u...>

• References:
  • Re: DTD vs XSD: No Duplicate Types in (Mixed) Content Models
    • From: =?UTF-8?B?TWFpayBTdMO8aHJlbmJlcmc=?= <maik.stuehrenberg@u...>