gzz-commits
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Gzz-commits] manuscripts/storm article.rst


From: Benja Fallenstein
Subject: [Gzz-commits] manuscripts/storm article.rst
Date: Sat, 08 Feb 2003 17:08:02 -0500

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

Modified files:
        storm          : article.rst 

Log message:
        Some actual UML

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

Patches:
Index: manuscripts/storm/article.rst
diff -u manuscripts/storm/article.rst:1.116 manuscripts/storm/article.rst:1.117
--- manuscripts/storm/article.rst:1.116 Sat Feb  8 15:21:55 2003
+++ manuscripts/storm/article.rst       Sat Feb  8 17:08:01 2003
@@ -178,7 +178,8 @@
 
 The dangling link problem has received a lot of attention
 in hypermedia research [refs]. As examples, we examine the ways
-in which HTTP, Microcosm [ref] and Hyper-G [ref] deal with the problem.
+in which HTTP, Microcosm [ref], Hyper-G [ref] and URNs [ref]
+deal with the problem.
 
 In HTTP, servers are able to notify a client that a document
 has been moved, and redirect it accordingly [ref spec?]. However,
@@ -745,21 +746,25 @@
 indexing (Section 5): Keeping an index of all pointer blocks
 about pointer ``P``, we can quickly find out the current one.
 
-UML to be drawn::
+.. uml:: storm_pointers
 
-                                   obsoleted block
-                                     * -----\ 
-                                       /      \
-    +---------+ 1      * +---------------+    |
-    | Pointer |----------| Pointer block |----/
-    +---------+          +---------------+ 1
-                               * |
-                                 | 
-                                 |
-                               1 | target
-                            +---------+
-                            | Target  |
-                            +---------+
+    class Pointer
+
+    class PointerBlock
+        assoc multi(*) - multi(1) Pointer
+        assoc multi(*) - multi(1) role(target) Target
+        
+    ring = assoc PointerBlock multi(1) - multi(*) role(obsoleted) PointerBlock
+
+    class Target
+
+    ---
+
+    Pointer.c = (0, 0);
+    horizontally(100, foo, Pointer, PointerBlock);
+    vertically(50, bar, foo, Target);
+    ring.p = PointerBlock.e{right} .. PointerBlock.n{down};
+    
 
 In addition to the pointer and the target, pointer blocks contain
 a list of zero or more *obsoleted* pointer blocks. When a new version




reply via email to

[Prev in Thread] Current Thread [Next in Thread]