also... SGML/DTD

[Hussain Chinoy]

eew, flamed!  <whoosh!>
	
	Ok, no big deal, I'd just thought that since SGML & DTD are used 
in other places than the WWW (though HTML happens to be the most widely 
used), it'd would be nice to expand OmniWeb's features in a way that I 
thought (probably naively thought) would be relatively easy compared to 
implementing Java or Webspace capabilities.  I'm assuming that making a 
superset of HTML (oh, this is getting odd, DTD->SGML->HTML, and I'm going 
the other way!) would be a bit easier and Omni would be able to say, 
"Hey, look, yes this can do HTML (2.0, 3.0), but also can do SGML and 
can read this device-independant data."
	I can see, though, why this would be an obsolete request: HTML's 
popularity and the greater flexibility of 3.0 may begin to rule the 
world.
	Maybe typesetters will begin to take manuscripts in HTML (4.0,
etc) instead/along-with TeX and other formatting langauges? 

	</whoosh!>

  ___	 __________________________________________________________
 /\__\        G. Hussain Chinoy
 \/__/                                 314/591-4955       vox
NEXTSTEP,                              314/935-5799       fax
  baby                     hussain at artsci.wustl.edu       net
              http://www.artsci.wustl.edu/~hussain/       web

On Tue, 27 Jun 1995, Eric Litman wrote:

> This fundamentally violates one of the key principals the internet was
> built upon, and that is to generate strictly, accept loosely. What
> exactly would be the benefit of restricting yourself from viewing the
> nearly countless number of pages on the web which do not conform
> precisely to the latest DTD? The "purity" of which you speak should
> not be an end in an of itself - I refer you to the OSI stack for
> historical reference.
> 
> </eal>