In-response-to-base:
In-response-to:
Date: Tue, 04 Mar 1997 12:19:52 GMT
From: Christophe Vermeulen (cver@rc.bel.alcatel.be)

The

HTTP/1.1 200 OK Date: Tue, 24 Nov 2009 18:28:03 GMT Server: Apache/2.2.6 (Fedora) Last-Modified: Thu, 30 Oct 1997 19:45:01 GMT ETag: "284135-368-5902a940" Accept-Ranges: bytes Content-Length: 872 Connection: close Content-Type: text/html; charset=UTF-8

In a sense, Java and SGML _are_ orthogonal.

But when you look at what happens on the net, they aren't
orthogonal anymore, they are complementary, and building
on each other's strength :

- Yes, there are (several) SGML parser in Java
- W3C is considering a SGML subset (called XML) for the Web,
  so that Browsers can (as suggested by  Charlie Stross )
  accept other DTDs
- SGML brings structure in Web documents, what HTML 
  failed at (and it's needed, as search engines now 
  fail to "understand" what's in a page).

On the "One Web for programers and one for Librarians",
it's simply untrue : there is one web, and it's for 
users (not "programmers", living on a Unix network, nor
librarians, living in keywords and references). Both
categories, though, have the mission of "building a 
better Web" (for users). Java _AND_ SGML will be tools
for that.