[Gzz-commits] manuscripts/storm article.rst

[Benja Fallenstein]

CVSROOT:        /cvsroot/gzz
Module name:    manuscripts
Changes by:     Benja Fallenstein <address@hidden>      03/01/25 08:11:48

Modified files:
        storm          : article.rst 

Log message:
        bit

CVSWeb URLs:
http://savannah.gnu.org/cgi-bin/viewcvs/gzz/manuscripts/storm/article.rst.diff?tr1=1.34&tr2=1.35&r1=text&r2=text

Patches:
Index: manuscripts/storm/article.rst
diff -u manuscripts/storm/article.rst:1.34 manuscripts/storm/article.rst:1.35
--- manuscripts/storm/article.rst:1.34  Fri Jan 24 09:57:16 2003
+++ manuscripts/storm/article.rst       Sat Jan 25 08:11:48 2003
@@ -16,10 +16,37 @@
 Real-live data mobility. Server centricity not suited to this.
 It's well recognized that references should not be by location [ref URN].
 
+->
+On the Web, documents are tightly bound to one location: they 
+cannot be moved to a different server without breaking links to them. 
+This paradigm may be tolerable for published data, but it mixes
+badly with data on desktop computers, since users expect to
+move data quite freely, copying it through the network,
+taking it home on diskettes, sending it in e-mail attachments,
+or moving it between their desktop and laptop computers.
+Documents are copied from the Web to local storage for off-line reading.
+We examine two issues this *data mobility* raises for hypermedia:
+keeping track of links, and keeping track of alternative versions
+as documents move between computers.
+
+->
+It is the norm for hypermedia systems to assume a centralized infrastructure,
+much like the Web. [Discuss Microcosm, Chimera and other OHS here.]
+Even Xanadu [ref], which went a long way to ensure that links do not break
+when their targets are copied from one document to another,
+required permanent connection to a network of servers to function,
+and, at least in its 1988 incarnation [ref Green] addressed data 
+based on the address of a server holding a 'master copy.'
+
+->
+
+
 (To explain data mobility:
 Data moves like this and that. The server/location paradigm
 is not suited to this: To support hypermedia functionality correctly,
-we need to recognize two copies of the *same* document.)
+we need to recognize two copies of the *same* document.
+Only then can we merge the fragmented worlds of desktop computing
+and online publishing into one.)
 
 Server centricity is what made the web scalable. Backlinks rejected
 for this reason [ref TBL]. However, recent innovations in P2P have made