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

Derived DTD - overriding attributes

• To: xml-dev <xml-dev@l...>
• Subject: Derived DTD - overriding attributes
• From: Kevin Burges <xmldude@b...>
• Date: Wed, 14 Nov 2001 11:50:38 +0000
• Organization: Formedix Ltd.
• Reply-to: Kevin Burges <xmldude@b...>

I need to create one DTD derived from another. The docs for the base
DTD say that I should use this structure:

    -----------------
    <!-- Put here to override existing attribute declarations -->

    <!-- Put here to override existing entities from the base DTD -->

    <!-- Define and use an entity reference to the base DTD -->
    <!ENTITY % baseDTD SYSTEM "http://127.0.0.1/dtd/base.dtd">
    %baseDTD;

    <!-- Put new element declarations here -->

    <!-- Put new attribute declarations here -->
    
    -----------------

I want to override an ATTLIST to add an extra choice to one of the
attributes. I tried putting the new ATTLIST declaration above the
inclusion of the base DTD, as suggested.

I am using XMLSpy (4.1) as my editor, and it did not pick up the new
attribute value.

I tried moving the ATTLIST to beneath the inclusion of the base DTD
and it then worked.

When duplicate ATTLISTs are found, is it not supposed to be the first
one that is used? This is certainly not the behaviour XMLSpy seems to
be giving me. Or am I doing something wrong?


-- 
May the flares be with you,
 Kevin                     kevin@b...

+++++++++++++ Cool music - http://mp3.com/marshan
++ Attitude Rock Webzine - http://burieddreams.com/attitude

• Prev by Date: Re: W3C XML Schema is more than "close by default) (Re: annotations outside validation)
• Next by Date: Re: Caught napping!
• Previous by thread: RE: Updating XML
• Next by thread: How to avoid the sequens of child elements in DTD, yet keep the cardinality?
• Index(es):
  • Date
  • Thread