[Gzz-commits] manuscripts/storm article.rst

[Hermanni Hyytiälä]

CVSROOT:        /cvsroot/gzz
Module name:    manuscripts
Changes by:     Hermanni Hyytiälä <address@hidden>      03/01/21 06:16:41

Modified files:
        storm          : article.rst 

Log message:
        More on Notes <-> Gzz

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

Patches:
Index: manuscripts/storm/article.rst
diff -u manuscripts/storm/article.rst:1.23 manuscripts/storm/article.rst:1.24
--- manuscripts/storm/article.rst:1.23  Tue Jan 21 03:47:18 2003
+++ manuscripts/storm/article.rst       Tue Jan 21 06:16:41 2003
@@ -34,7 +34,7 @@
 
 Research has been done in a number of areas to alleviate this problem.
 There are a number of proposals for sharing a web browser's cache
-between users [search for refs!].
+between users [squirrel].
 ... 
 Thompton and De Roure [ref ht'01] propose a peer-to-peer system
 for discovering cached web resources in a mobile, disconnected setting,
@@ -137,12 +137,55 @@
 I'd prefer term 'replication' instead of term syncing, when
 updating data to 'the most recent state'. E.g. Lotus Notes uses
 term replication, when one performs locally made updates into
-a centralized server --> 'used within same system'. Syncing term, however, is 
used when importing/exporting
-e.g. Nokia Communicator calendar data into/from Lotus Notes calendar --> 'used 
between different systems'.
+a centralized server --> 'used within same system'. Syncing term, however, 
+is used when importing/exporting e.g. Nokia Communicator calendar data 
into/from 
+Lotus Notes calendar --> 'used between different systems'.
 
 
-hemppah: worth to mention is that Ray Ozzie is a man behind Lotus Notes and 
Groove; Lotus Notes
-is based on client-server model and, Groove is based on p2p model --> possible 
direction etc. ? 
+hemppah: worth to mention is that Ray Ozzie is a man behind Lotus Notes and 
Groove; 
+Lotus Notes is based on client-server model and, Groove is based on p2p model 
--> 
+possible direction etc. ?
+
+hemppah: I think we should mention that in Gzz one refer to data in 
non-hierarchial 
+way, where as in Notes (and other systems also, references!!), we must use 
+hierarchial way. In Notes
+1) every document has a unique identifier, which is unique among all replicas 
+of database
+2) every document/design element has a identifier, named as noteID, which is 
unique 
+in database, but not among all replicas of database 
+3) every view has a unique identifier,  which is unique among all replicas of 
+database
+4) every database has a ID, named as replicaID, which identifies database's 
replicas 
+among all databases
+
+So, if we want to refer to a document, we use format:
+
+replicaID/viewID/documentID
+
+Also, we can refer to same document, through *many different* views:
+replicaID/viewID1/documentID
+replicaID/viewID2/documentID
+
+Notes://server/D235632D00313587/38D22BF5E8F088348525JK7500129B2C/REWB3FDE0D53807B67C2256CB50026FCVV
+
+Where in Gzz, we don't know the location, we know only the *identify*, like 
this
+
+urn-5:FAB3FDE0hgfD5kkjj3807B67C2256CfsdB50026FC51 
+
+Above is not a *correct* urn-5, but very similar to last part of notes' syntax.
+
+(Of course, this is very similar to 'normal' URLs, but our purpose here is to 
give an example
+of how one refer to a particular data item in colloboration-like tool, like 
Notes)
+
+Of course, in Notes, there are servers, which maintain replication of data, 
opposite to Gzz. What is 
+interesting in Notes' replication, is the fact that the replication of 
database not only 
+replicate the *data* but also design of data, which represent the data.
+Worth to mention is also that, even if the data and the design of data (logic 
etc.) is 
+in the *same* (physical) structure, data and design of data is very loosely 
coupled with 
+each other.
+
+Additionally, worth mention is that how things are going towards 
non-hierarchical reference models, 
+for instance, Notes and Gzz, which both are based on the same Xanalogical 
model.
 
 
 "Usability in the face of intermittent connectivity" is