Obsolete elements -- trying again

"Leo _ _ _ _ _ _ _ _ _ _ _ _ _ _ Peace is not something you win. Peace is"

Mail folder: html-archive
Next message: Peter Flynn: "Re: Obsolete elements -- trying again"
Previous message: Eric W. Sink: "Re: erics, mike - OOPS!"
Reply: Peter Flynn: "Re: Obsolete elements -- trying again"

Date: Fri, 26 Aug 94 10:28:25 EDT
Message-id: <01HGCIMCRSTUT7I5A1@avion.stsci.edu>
Reply-To: "Leo"
Originator: html-wg@oclc.org
Sender: html-wg@oclc.org
Precedence: bulk
From: "Leo _ _ _ _ _ _ _ _ _ _ _ _ _ _ Peace is not something you win. Peace is"
To: Multiple recipients of list <html-wg@oclc.org>
Subject: Obsolete elements -- trying again
X-Listprocessor-Version: 6.0c -- ListProcessor by Anastasios Kotsikonas
X-Comment: HTML Working Group (Private)

> OBSOLETE ELEMENTS [WAS: HTML 2.0 CALL FOR REVIEW ]
> "Daniel W. Connolly" <connolly@hal.com>
> * Reply: Peter Flynn: "Re: Obsolete Elements [Was: HTML 2.0 Call for Review ]"
> Message-id: <9406102008.AA08103@ulua.hal.com>
> To: html-ig@oclc.org
> Subject: Obsolete Elements [Was: HTML 2.0 Call for Review ]
> In-Reply-To: Your message of "Mon, 06 Jun 1994 13:25:11 -0000."
>              <9406061225.AA11520@dragget.hpl.hp.com>
> Date: Fri, 10 Jun 1994 15:08:28 -0500
> From: "Daniel W. Connolly" <connolly@hal.com>
> 
> In message <9406061225.AA11520@dragget.hpl.hp.com>, Dave Raggett writes:
> >
> >    o   <!ENTITY % pre "PRE | XMP | LISTING">
> >
> >Doesn't this make it hard to test for obsolete elements with SGMLS?
> >I would prefer to see them defined in a marked section so that
> >its easy to switch obsolete elements in/out of the DTD for testing.
> 
> Good idea.
> 
> What's the general consensus out there about obsolete elements?
> 
> The only ones I know of are XMP and LISTING.
> 
> Should we even mess with putting them in the DTD? Or should we just
> stick a note in the spec about how implementations are encouraged
> to include this hack?
> 
> Dan

Dan,

I was wondering why XMP and LISTING are being made obsolete.  They are
very useful when you want to return system error messages to the user
during the execution of a script.  I can't use PRE because Lynx will get
confused when there is an unadorned "<".

Is there any chance that the obsolete status of XMP and/or LISTING can
be changed?

Leo