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

Re: DTD parameter entities

• To: richard@c... (Richard Tobin)
• Subject: Re: DTD parameter entities
• From: Toni Uusitalo <toni.uusitalo@p...>
• Date: Thu, 22 Apr 2004 21:18:24 +0200
• Cc: xml-dev@l...
• In-reply-to: <20040422124545.81DEAB2786@m...>
• References: <6.0.0.22.0.20040421212252.02130b80@p...><20040422124545.81DEAB2786@m...>

At 14:45 22.4.2004, you wrote:
>This is well-formed but not valid: the rule that a declaration must
>end in the same entity it starts in is a validity constraint.
>
>RXP will report this if you use the -V flag (at least recent versions
>will, I can't remember when I implemented that check).

True, my windows executable (v 1.2.5) catches this when I turn validation
on with -v flag:

Warning: Attlist declaration ends in different entity from that in which it 
star
ts in entity "CLOSE" defined at line 2 char 1 of file:///C:/temp/petest.dtd
in unnamed entity at line 6 char 58 of file:///C:/temp/petest.dtd

It is this "not from the same entity thing" that makes %ATTLIST; and 
%CLOSE; illegal (and
making any DTD declaration start like <!ELEMENT or <[IGNORE[ to be written 
as PE reference illegal).
Same thing that makes splitting general entity references like <!ENTITY e1 
"<!--"> and <!ENTITY e2 "-->">
illegal, is this true?
but shouldn't this be a well-formedness error?


with respect,
Toni Uusitalo

• References:
  • DTD parameter entities
    • From: Toni Uusitalo <toni.uusitalo@p...>
  • Re: DTD parameter entities
    • From: richard@c... (Richard Tobin)

• Prev by Date: Re: DTD parameter entities
• Next by Date: Re: DTD parameter entities
• Previous by thread: Re: DTD parameter entities
• Next by thread: RE: When to design an attribute in a namespace?
• Index(es):
  • Date
  • Thread