/[gzz]/manuscripts/storm/article.rst
ViewVC logotype

Diff of /manuscripts/storm/article.rst

Parent Directory Parent Directory | Revision Log Revision Log | View Patch Patch

revision 1.77 by hemppah, Mon Feb 3 13:40:20 2003 UTC revision 1.78 by antont, Mon Feb 3 15:25:01 2003 UTC
# Line 9  The Web and many other hypermedia system Line 9  The Web and many other hypermedia system
9  either have to include location information (as in URLs, which break  either have to include location information (as in URLs, which break
10  when documents are moved), or can only be resolved locally (as in  when documents are moved), or can only be resolved locally (as in
11  link services that can only find links stored on a select set  link services that can only find links stored on a select set
12  of link servers [ref Microcosm, DLS, ...]). Berners-Lee [ref NameMyth] argues that  of link servers [ref Microcosm, DLS, ...]). Berners-Lee [ref NameMyth - that
13    was '96, what does he say now?] argues that
14  unique random identifiers are not globally feasible for this reason.  unique random identifiers are not globally feasible for this reason.
15    
16  However, recent developments in peer-to-peer systems have  However, recent developments in peer-to-peer systems have
# Line 62  without changing applications substantia Line 63  without changing applications substantia
63  of our implementation of Xanalogical storage is to be taken.  of our implementation of Xanalogical storage is to be taken.
64  (Vitali [ref] notes that Xanalogical storage necessiates  (Vitali [ref] notes that Xanalogical storage necessiates
65  strong discipline in version tracking, which current systems lack.)  strong discipline in version tracking, which current systems lack.)
66    Investigating the degrees of interoperability with (other) Open Hypermedia
67    (/Structural Computing?) and (more primitive?) other (Web) XXX is a possible
68    direction for future work, and will be preliminarly discussed here too.
69    
70  This paper is structured as follows. In next section, we describe  This paper is structured as follows. In next section, we describe
71  related work. In section 3, we introduce the basic storage unit of our  related work. In section 3, we introduce the basic storage unit of our
# Line 85  section 7, we discuss potential peer-to- Line 89  section 7, we discuss potential peer-to-
89  In section 8, we report on implementation experience and future  In section 8, we report on implementation experience and future
90  directions. Section 9 concludes the paper. -Hermanni]  directions. Section 9 concludes the paper. -Hermanni]
91    
92    (where and how use cases? are not mentioned in either of the above, but are
93    currently split in two - hinting somewhere in the beginning and reviewing at
94    the and).
95    
96    
97  2. Related Work  2. Related Work
98  ===============  ===============
# Line 600  Yet, it is decidedly inconvenient when e Line 608  Yet, it is decidedly inconvenient when e
608  the computer pops up a little window saying, "There are currently  the computer pops up a little window saying, "There are currently
609  three different versions of this resource. Which one would you like  three different versions of this resource. Which one would you like
610  to open?" Overcoming this problem will be an important issue  to open?" Overcoming this problem will be an important issue
611  as the system matures.  as the system matures. Possible situation-specific solutions include one
612    where there may be (simple) rules to prioritize them based on metadata, e.g.
613    if some sort of an official or original version is preferred.
614    
615  While we see the pointer system as useful for  While we see the pointer system as useful for
616  asynchronous collaboration, it is not well suited to Web-like publishing.  asynchronous collaboration, it is not well suited to Web-like publishing.

Legend:
Removed from v.1.77  
changed lines
  Added in v.1.78

savannah-hackers-public@gnu.org
ViewVC Help
Powered by ViewVC 1.1.26