** That Strict DTD is the only DTD that does not allow deprecated tags.
** Strict DTD does not allow frames.
therefore : yes, lets hear it - frames will be going away as the industry
moves to strict DTD.
The transitional DTD and the frameset DTD allow deprecated tags, but the
strict DTD does not, right?
The Strict DTD does not allow framesets, right?
Deprecated tags should not be used because the support for those tags will
eventually go away, right?
Shouldn't one expect that when the deprecated tags go away, so will the DTDs
that allow them?
Since the frameset DTD is one of those DTDs that allow deprecated tags, then
it will probably go away.
The end
> The transitional DTD and the frameset DTD allow deprecated tags, but the
> strict DTD does not, right?
The frameset DTD is an extension of the transitional DTD which includes
frames.
> The Strict DTD does not allow framesets, right?
Right - that's what the frameset DTD is for...
> Deprecated tags should not be used because the support for those tags will
> eventually go away, right?
There are eleven tags which are deprecated in the strict DTD: APPLET,
BASEFONT, CENTER, DIR, FONT, IFRAME, ISINDEX, MENU, S, STRIKE, and U. They
will eventually be removed from the frameset DTD too. However, the frameset
DTD itself will remain for the forseeable future, specifically to support
frames - that's what it's for...
> Shouldn't one expect that when the deprecated tags go away, so will the
> DTDs that allow them?
The transitional DTD will eventually disappear leaving only strict DTD and
frameset DTD.
> Since the frameset DTD is one of those DTDs that allow deprecated tags,
> then it will probably go away.
It will remain as long as the strict DTD - both will eventually be replaced
by newer standards...

Signature
Mark Rae
ASP.NET MVP
http://www.markrae.net