[Gzz-commits] manuscripts/storm article.rst

[Toni Alatalo]

CVSROOT:        /cvsroot/gzz
Module name:    manuscripts
Changes by:     Toni Alatalo <address@hidden>   03/02/03 10:25:01

Modified files:
        storm          : article.rst 

Log message:
        little work on intro: how to deal with interoperability and OTOH use 
cases?

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

Patches:
Index: manuscripts/storm/article.rst
diff -u manuscripts/storm/article.rst:1.77 manuscripts/storm/article.rst:1.78
--- manuscripts/storm/article.rst:1.77  Mon Feb  3 08:40:20 2003
+++ manuscripts/storm/article.rst       Mon Feb  3 10:25:01 2003
@@ -9,7 +9,8 @@
 either have to include location information (as in URLs, which break 
 when documents are moved), or can only be resolved locally (as in
 link services that can only find links stored on a select set
-of link servers [ref Microcosm, DLS, ...]). Berners-Lee [ref NameMyth] argues 
that 
+of link servers [ref Microcosm, DLS, ...]). Berners-Lee [ref NameMyth - that
+was '96, what does he say now?] argues that 
 unique random identifiers are not globally feasible for this reason.
 
 However, recent developments in peer-to-peer systems have
@@ -62,6 +63,9 @@
 of our implementation of Xanalogical storage is to be taken.
 (Vitali [ref] notes that Xanalogical storage necessiates
 strong discipline in version tracking, which current systems lack.)
+Investigating the degrees of interoperability with (other) Open Hypermedia
+(/Structural Computing?) and (more primitive?) other (Web) XXX is a possible
+direction for future work, and will be preliminarly discussed here too.
 
 This paper is structured as follows. In next section, we describe 
 related work. In section 3, we introduce the basic storage unit of our 
@@ -85,6 +89,10 @@
 In section 8, we report on implementation experience and future 
 directions. Section 9 concludes the paper. -Hermanni]
 
+(where and how use cases? are not mentioned in either of the above, but are
+currently split in two - hinting somewhere in the beginning and reviewing at
+the and).
+
 
 2. Related Work
 ===============
@@ -600,7 +608,9 @@
 the computer pops up a little window saying, "There are currently
 three different versions of this resource. Which one would you like
 to open?" Overcoming this problem will be an important issue
-as the system matures.
+as the system matures. Possible situation-specific solutions include one
+where there may be (simple) rules to prioritize them based on metadata, e.g.
+if some sort of an official or original version is preferred.
 
 While we see the pointer system as useful for 
 asynchronous collaboration, it is not well suited to Web-like publishing.