[Date Prev][Date Next][Thread Prev][Thread Next][Author Index][Date Index][Thread Index]
Why have a multipart document address?
- To: xanadu@xxxxxxxxxx
- Subject: Why have a multipart document address?
- From: Jack Seay <jackseay@xxxxxxxxxxxxx>
- Date: Tue, 8 Feb 2005 23:03:24 -0600
Is it necessary to have the server number as part of a document
address? What if the server is shut down or the document needs to be
moved? Maybe the author just wants to use a different server.
If a language that implements the Linda functions designed by David
Gelernter was used, it wouldn’t matter where the document was stored.
Just make sure it is located in more than one place for safety. There
wouldn’t be a server address at all. A query about a document would
just request a document number and distributed agents would retrieve it
from wherever it is located on the network of servers and return it to
Also, why have a version number as part of the address? Why not just
give each new added document a new document number. If it is a new
version of another document, it will transclude much of the previous
document. The revisor could be the original author, a group of writers,
or a different writer. There could be major changes, or just a few. How
do you decide if it’s a new version or just transcludes a lot from
another document. If the version number is eliminated from the address,
it doesn’t have to become a hardcoded item. A separate document could
tie the various versions together with links. And by looking at all the
documents that transclude the current one, newer versions will be
Also, why have the author part of the document address? What if there
are several authors? What if the author uses several names? What if it
is published by a group of people working for a business? What if that
Could a series of relational tables (or xanalogical documents or zigzag
dimensions) store the information on authors, publishers, buyers,
links, formats, etc. and combine the data in whatever way is needed to
create the composited document?