Re: Cougar DTD: Do not use CDATA declared content for SCRIPT (fwd)

MegaZone (
Mon, 29 Jul 1996 20:52:33 -0700 (PDT)

Message-Id: <>
Subject: Re: Cougar DTD: Do not use CDATA declared content for SCRIPT (fwd)
Date: Mon, 29 Jul 1996 20:52:33 -0700 (PDT)
From: MegaZone <>

Once upon a time Paul Prescod shaped the electrons to say...
>Most likely they would all use the same "end of data string" (<\SCRIPT>)
>that they see on Netscape's site, even when their script contains the string

So what?  today you can't put </SCRIPT> in a SCRIPT container, it is 
considered invalid.  Coders live with that today, so it isn't a step back at

>Since there is no way to standardize inline scripts that will result in
>reliable interoperability, they should be disallowed.

Whoa!  Says who?  Any reasonable coder knows there are always limits to what
they can do.  I'd love to see multiple ways to do it - SRC to call an
external file (I'd love to be able to put multiple scripts in a file and
call them out by name or something, but yeah, right...), SRC="data:..." for
inlining (still want to read more on that myself), and <SCRIPT>script</SCRIPT>
inlining as it is done today - which is the technique most understood by
the majority of web authors.

Most people on the web today don't care a whit about SGML compliance, they
just want it to work anyway it can.  I believe folks like us who have a bit
more knowledge should look for ways to provide good tools and we need to be
flexible in addressing existing usage.  Coming out with an edict because we
don't like the way it works doesn't seem right to me, a few people have made
proposals to address this and I'd like to see them hashed out before giving
up on it.

Livingston Enterprises - Chair, Department of Interstitial Affairs
Phone: 800-458-9966 510-426-0770 FAX: 510-426-8951
For support requests:  <> 
Snail mail: 6920 Koll Center Parkway  #220, Pleasanton, CA 94566