Re: Issues of DTD unification and revision

>We didn't come to a definitive decision a couple of months ago about
>"unifying" all the needs of the various DTD users.  However, I become
>convinced that for now, it's fine to have a single DTD that incorporates
>the structures needed for XML-related W3C specs.  Thus, Gavin, if you want
>to send me your DOM markup declarations, I will incorporate them (as a
>module, if you wish, though it would be easier to incorporate it "in the
>flesh").

I will send the module presently, along with the (very slightly
modified) version of the spec.dtd we use for the DOM. I've been
careful to to alter much...

>Is it a problem that the most recent DTD doesn't work with the XML spec?
>Personally, I don't think so -- that's why I put the date in the FPI and
>the filename.  We just need to make sure that the old version continues to
>be available.  However, I don't intend to make backwards-incompatible
>changes every week, or even every month.

Yes. DTD's evolve over time, like everything else. I see no problem with
an older document being incompatible with a newer DTD.

Received on Thursday, 4 June 1998 15:13:15 UTC