- From: Daniel W. Connolly <connolly@hal.com>
- Date: Thu, 09 Jun 1994 12:58:13 -0500
- To: Dave Raggett -- HTML+ Spec Editor <dsr@hplb.hpl.hp.com>, Marc Andreessen -- Mosaic Communications <marca@netcom13.netcom.com>, Peter Flynn -- HTML educator <pflynn@curia.ucc.ie>, Stu Weibel -- OCLC <weibel@oclc.org>, Terry Allen -- O'Reilly & Assoc <terry@ora.com>, Christopher McRae -- ORA <mcrae@ora.com>, Tim Berners-Lee -- WWW Project Lead <timbl@www0.cern.ch>, Eric Sink -- Spyglass <esink@spyglass.com>, Jay Glicksman -- EIT Project Leader <jay@eit.com>, Larry Jackson -- NCSA SDG <jackson@ncsa.uiuc.edu>, Yuri Rubinsky -- SoftQuad <yuri@sq.com>, Murray Maloney -- SCO <murray@sco.com>, "William Perry -- U. Indiana" <wmperry@indiana.edu>, "Gary R. Adams -- Sun Labs" <gary.adams@east.sun.com>, "Ronald E. Daniel -- Los Alamos National Labs" <rdaniel@acl.lanl.gov>, Eduardo Gutentag -- Sun <Eduardo.Gutentag@eng.sun.com>, Corp Reed -- Cold Spring Harbor Lab <reed@hades.cshl.org>, www-talk@www0.cern.ch, www-html@www0.cern.ch
I have an urgent need for the kind of services provided by the WIT system (see http://info.cern.ch/hypertext/WWW/WIT/User/Overview.html), but I believe that we should deploy this application on top of existing collaborative applications: USENET news and Internet Mail. For the purpose of the HTML 2.0 review, I suggest we use the www-html list and a hypermail archive (I got wind that one is in the works). *** To the www-html maintainers: can the list processor be changed to stop repeating headers? Especially MIME related headers. In the future, I'd like to be able to process an archive of html documents sent to www-html, but witht the current list set-up, they get munged. This is better than when they got deleted, but... *** Alternatively, if somebody wants to set up a special list just for the HTML 2.0 discussion (with a hypermail archive, of course) I'd be happy to use that in stead. I would like to be able to create WIT-style views of the archive of this discussion, so we should adopt some convention for expressing the topic/proposal/argument structure in RFC822 headers. See below for details... Why not just use WIT over HTTP? WIT over HTTP has no privisions for scalability. Even under the current load, it is unresponsive and faulty. Here are the features I think we need, and how they map to the HTTP, internet-mail, and USENET mechanisms: Feature HTTP Mail News Subscribe POST (authenticated subscription edit .newsrc transaction with request the server) message Add a topic POST start a mailing create a newsgroup list Add a proposal POST send a message post an article to the list with a novel with a novel Subject: Subject: Change a ??? use Supercedes: header document Add an argument POST use In-Reply-To: and References: !need "link type" info! [I propose In-Support-Of:, In-Opposition-To: headers, or perhaps Reply-Disposition: ...] Include a link HTML anchors HTML anchors (use MIME to tag in the body of the body as HTML) a document Include an Copy and paste, traditional USENET excerpt markup excerpt in the perhaps with a link for plain text. body... to the original Sign a message Secure HTTP PEM techniques PEM techniques (not widely deployed) Browse all GET topics list !need archive! !need archive! topics Browse all follow link from !need archive! !need archive! proposals topics list on a topic Browse recent ??? read new mail NEWNEWS topics Browse recent ??? read new mail NEWNEWS proposals Browse argument GET propsal doc scan headers of scan headers of summary relavent* relevant articles, messages as in threaded news readders Comments? Dan
Received on Thursday, 9 June 1994 19:58:24 UTC