X-VM-v5-Data: ([nil nil nil nil nil nil nil nil nil] ["739" "Wed" "10" "September" "1997" "12:12:06" "+0100" "Sebastian Rahtz" "s.rahtz@ELSEVIER.CO.UK" nil "19" "Re: HyperLaTeX" "^Date:" nil nil "9" nil "HyperLaTeX" nil nil nil] nil) Received: from listserv.gmd.de (listserv.gmd.de [192.88.97.1]) by mail.Uni-Mainz.DE (8.8.5/8.8.5) with ESMTP id NAA10849; Wed, 10 Sep 1997 13:18:10 +0200 (MET DST) Received: from lsv1.listserv.gmd.de by listserv.gmd.de (LSMTP for OpenVMS v1.1a) with SMTP id <0.3BE95BFA@listserv.gmd.de>; Wed, 10 Sep 1997 13:16:38 +0200 Received: from RELAY.URZ.UNI-HEIDELBERG.DE by RELAY.URZ.UNI-HEIDELBERG.DE (LISTSERV-TCP/IP release 1.8b) with spool id 196613 for LATEX-L@RELAY.URZ.UNI-HEIDELBERG.DE; Wed, 10 Sep 1997 13:17:28 +0200 Received: from pillar.elsevier.co.uk (root@pillar.elsevier.co.uk [193.131.222.35]) by relay.urz.uni-heidelberg.de (8.7.6/8.7.4) with ESMTP id NAA01727 for ; Wed, 10 Sep 1997 13:17:25 +0200 (MET DST) Received: from snowdon.elsevier.co.uk (snowdon.elsevier.co.uk [193.131.197.164]) by pillar.elsevier.co.uk (8.8.5/8.8.5) with ESMTP id MAA03513 for ; Wed, 10 Sep 1997 12:17:35 +0100 (BST) Received: from SRAHTZ (actually host srahtz.elsevier.co.uk) by snowdon.elsevier.co.uk with SMTP (PP); Wed, 10 Sep 1997 12:17:37 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit References: X-Mailer: VM 6.33 under Emacs 19.34.4 Message-ID: <7118-Wed10Sep1997121206+0100-s.rahtz@elsevier.co.uk> Reply-To: Mailing list for the LaTeX3 project In-Reply-To: Date: Wed, 10 Sep 1997 12:12:06 +0100 From: Sebastian Rahtz Sender: Mailing list for the LaTeX3 project To: Multiple recipients of list LATEX-L Subject: Re: HyperLaTeX Status: R X-Status: X-Keywords: X-UID: 2301 > So how does the hypertex protocol work together with other protocols, > like embedded PS or non-GIF pictures? Does every protocol invent its own > syntax to identify itself? there *is* no protocol for embedded PS or non-GIF, so what are you getting at > Well, the HTML standard is evolving, and one would then want to have oh you think its a `standard'.... sensible people like TeXxies [1] should be plugging XML > access to the new hyperlink features, but not the markup features. So one > would really want to work with a hyperlink protocol, and not HTML. which is exactly what we have. the fact that the tags start `html' does not imply that random HTML after them is acceptable. sebastian [1] i am famous for my irony