[Date Prev][Date Next][Thread Prev][Thread Next][Author Index][Date Index][Thread Index]
:zz: virtual cells (was Re: [zzdev] "Virtual" (was: Re: [zzdev] Some thoughts on virtual structures)
- To: zzdev@xxxxxxxxxx
- Subject: :zz: virtual cells (was Re: [zzdev] "Virtual" (was: Re: [zzdev] Some thoughts on virtual structures)
- From: Ted Nelson <ted@xxxxxxxxxx>
- Date: Thu, 08 Nov 2001 23:58:02 +0000
- Cc: ted@xxxxxxxxxx
- In-reply-to: <3BCFF4A4.E3AD09A0@xxxxxx>
- References: <18.104.22.168.20011018185138.45bff88a@xxxxxxxxxxxxx>
I intended the term "virtual cells" to mean non-persistent
but well-defined cells that were there whenever you need them,
for example calendar cells five years from now. These would
be automatically generated when you wanted to look at them,
but would only become persistent if you linked to them,
gave them contents etc.
At 11:38 AM 10/19/01 +0200, you wrote:
>Brent Turcotte wrote:
>> "Virtual structures, which enable any data, such as Web pages
>> and conventional databases, to be seen through the ZigZag structure"
>> -- from the "GZigZag in a Nutshell" article at
>> A virtual structure is a mapping of data onto a hypergrid
>> implementation, as I understand it.
>I do not think the term is particularly suited to this meaning. I don't
>understand the nutshell article the same way you do, either, but that's
>less important IMHO; I think what's important is to agree on a useful term.
>The adjective "virtual" invokes the question: "So what's the real
>counterpart?" What's a real structure, as opposed to a mapping of data
>onto a hypergrid implementation? Makes no sense to me. For me, there are
>two associations here: Ted's notion of a "virtuality" as opposed to
>"reality:" a designed environment that is enacted e.g. on a computer
>screen and that only exists in our heads; and the notion of "virtual
>cells" as opposed to "real cells," where the real cells are those in a
>hypergrid structure that are saved on the harddisk, whereas the virtual
>ones are those that the computer constructs on-the-fly, for example the
>numbers in a representation of the natural number system. There can only
>be a finite number of real cells, as storage is limited, but, as the
>example shows, a theoretically infinite number of virtual cells.
>To get back to the article, it is my understanding that it uses the term
>in this latter sense: the computer shows "virtual" cells that represent
>*external* data: a web page as retrieved through HTML; the contents of a
>database as queried through SQL. So when you used "virtual structures"
>in conjunction with file formats, I thought you might be talking about,
>similarly, representing the contents of a file as seen through the file
>system, not stored in the hypergrid.
>I cannot see a good reason to use the term "*virtual* structures" for
>"mapping of data onto a hypergrid implementation," and I would propose
>to simply use "hypergrid structure" instead; does this capture your
>meaning? Or am I missing some good reason to use "virtual structure" instead?
>Hope that we can agree on something,
Theodor Holm Nelson
Project Professor, Keio University SFC Campus, Fujisawa, Japan
? e-mail: ted@xxxxxxxxxx ? world-wide fax 1/415/332-0136
? http://www.sfc.keio.ac.jp/~ted/ ? http://www.xanadu.net
? Coordinates in USA Tel. 415/ 331-4422
Project Xanadu, 3020 Bridgeway #295, Sausalito CA 94965