Re: %flow and headers and address

Foteos Macrides (MACRIDES@SCI.WFBR.EDU)
Mon, 30 Sep 1996 10:06:21 -0500 (EST)


Date: Mon, 30 Sep 1996 10:06:21 -0500 (EST)
From: Foteos Macrides <MACRIDES@SCI.WFBR.EDU>
Subject: Re: %flow and headers and address
To: pflynn@curia.ucc.ie
Cc: www-html@w3.org
Message-id: <01IA33A6ZMNS0090D7@SCI.WFBR.EDU>

Peter Flynn <pflynn@curia.ucc.ie> wrote:
>   [...]how far have you gotten on your DTD[...]
>
>This week some time. It's gotten as far as Near&Far, so it parses OK,
>but I'm checking their (copious) reports to make sure all the bits
>that ought to be in there really are. I was tempted to keep the switch
>for Deprecated/Recommended but decided not to: there is no attempt at
>backward compatibility with stuff that is broken (ie there's no XMP or
>LISTING) but there is DIR and MENU. FRAME, STYLE, SCRIPT etc are all
>there, but MATH is untouched from HTML3 so far: I'm no mathematician
>so I'm really not qualified to change it. The only working changes are
>to add HR to the content model for lists, because it seems reasonable
>to allow rules between long items (sugar, but harmless). I made ALT
>#REQUIRED in IMG, but an interesting problem comes up when you try to
>use a graphical editor: how do you tell it to insert ALT="" when you
>want an explicit null string :-)

	Have you included stuff from the MicroSoft DTD?  What I'm
envisioning is an EVERYTHING.DTD with anything any client has
implemented *and*(/or) has been documented (/proposed) formally
(via a public DTD), fitted together so that it all fits together
if it can, such that any other client could implement any or all
of it rationally, and any provider could include any combination
in a document instance and pass that to a validator.

				Fote

=========================================================================
 Foteos Macrides            Worcester Foundation for Biomedical Research
 MACRIDES@SCI.WFBR.EDU         222 Maple Avenue, Shrewsbury, MA 01545
=========================================================================