Re: Links, Types and Documents

davis@willow.tc.cornell.edu (Jim Davis)
Date: Wed, 24 Jun 92 11:55:33 EDT
From: davis@willow.tc.cornell.edu (Jim Davis)
Message-id: <9206241555.AA13109@willow.tc.cornell.edu>
To: www-talk@nxoc01.cern.ch
Subject: Re:  Links, Types and Documents
In considering R. Raisch's link types, it seems to me that the
expansion and replacement can be combined and generalized.  In both
cases portion of the document is replaced.  In expansion case, the
condensed text is replaced (perhaps temporarily) with the enlarged
text, in replacement the entire document is replaced with some other.
So the more general case is a link which labels a range in both the
source and target document.  The replacement link labels the entire
document, the expansion labels only a portion.

As for execution links in general, I see Dan's point that adding
procedures to documents makes them difficult to manipulate.  And N
Borenstein has pointed out (in Mime) the dangers of executing
arbitrary code.  But I still see that there are functions which only
code can provide, and so we just face the challenge of designing a
language that is both powerful and safe, perhaps sacrificing Turing
completeness.  Is Atomicmail [tm?] such a language?