[Gzz-commits] manuscripts/UMLLink SCRATCH umllink.rst

[Tuomas J. Lukka]

CVSROOT:        /cvsroot/gzz
Module name:    manuscripts
Changes by:     Tuomas J. Lukka <address@hidden>        03/01/21 04:14:51

Modified files:
        UMLLink        : SCRATCH umllink.rst 

Log message:
        Reorg

CVSWeb URLs:
http://savannah.gnu.org/cgi-bin/viewcvs/gzz/manuscripts/UMLLink/SCRATCH.diff?tr1=1.1&tr2=1.2&r1=text&r2=text
http://savannah.gnu.org/cgi-bin/viewcvs/gzz/manuscripts/UMLLink/umllink.rst.diff?tr1=1.15&tr2=1.16&r1=text&r2=text

Patches:
Index: manuscripts/UMLLink/SCRATCH
diff -u manuscripts/UMLLink/SCRATCH:1.1 manuscripts/UMLLink/SCRATCH:1.2
--- manuscripts/UMLLink/SCRATCH:1.1     Tue Jan 21 04:11:56 2003
+++ manuscripts/UMLLink/SCRATCH Tue Jan 21 04:14:51 2003
@@ -1,39 +1,5 @@
 
 Recommended sources for references: IEEE, ACM
-
-- Borges's "taxonomy" for animals;
-  http://www.multicians.org/thvv/borges-animals.html
-- !! A Taxonomy of Link Types;
-  http://www.workpractice.com/trigg/thesis-chap4.html
-  
-  Thinking about linking... at first we do have UML->reST and 
-  UML->javadoc links. Because of embedding diagrams implicitly
-  into target documents we can see linking also as 
-  bi-directional reST<->javadoc, reST<->reST, and javadoc<->javadoc.
-
-  Mapping our links to types defined by Trigg:
-
-    reST<->reST  Alternate View (this occurs, when the same diagram is 
-                 explicitly referred in two or more architectural documents)
-
-    javadoc -> javadoc AlternativeView? (We can browse through all classes, 
which
-                     are part of the diagram.)
-
-    UML in javadoc -> reST    Detail->Summary
-
-    UML in reST -> Javadoc General->Spesific or Summary->Detail
-
-  Trigg classifies the following type-pairs for bi-directional links, which 
can are
-  interpreted oppositionally depending on the direction
-
-  Generalization/Specification
-  Abstraction/Example 
-  Formalization/Application
-  Summarization/Detail
-  Simplification/Complication
-
-  Could Generalization/Specification be best for reST<->Javadoc.  
-
 - Labeled, typed links as cues when reading hypertext documents; 
http://search.epnet.com/direct.asp?an=9702214682&db=afh
 
 - Automatically connecting documentation to code with rose; 
http://doi.acm.org/10.1145/584955.584979
Index: manuscripts/UMLLink/umllink.rst
diff -u manuscripts/UMLLink/umllink.rst:1.15 
manuscripts/UMLLink/umllink.rst:1.16
--- manuscripts/UMLLink/umllink.rst:1.15        Tue Jan 21 04:12:31 2003
+++ manuscripts/UMLLink/umllink.rst     Tue Jan 21 04:14:51 2003
@@ -2,7 +2,7 @@
 A free software toolchain for bidirectional linking between UML diagrams and 
Javadoc
 
====================================================================================
 
-:Last-Modified: $Date: 2003/01/21 09:12:31 $
+:Last-Modified: $Date: 2003/01/21 09:14:51 $
 
 Introduction
 ============
@@ -178,6 +178,43 @@
 UML diagrams act as multi-ended nexus links, bringing together all documents
 they relate to. They function like navigation bars on the WWW, except that
 the same page may have several of them.
+
+Analysis from a hypertext theory point of view
+==============================================
+
+- Borges's "taxonomy" for animals;
+  http://www.multicians.org/thvv/borges-animals.html
+- !! A Taxonomy of Link Types;
+  http://www.workpractice.com/trigg/thesis-chap4.html
+  
+  Thinking about linking... at first we do have UML->reST and 
+  UML->javadoc links. Because of embedding diagrams implicitly
+  into target documents we can see linking also as 
+  bi-directional reST<->javadoc, reST<->reST, and javadoc<->javadoc.
+
+  Mapping our links to types defined by Trigg:
+
+    reST<->reST  Alternate View (this occurs, when the same diagram is 
+                 explicitly referred in two or more architectural documents)
+
+    javadoc -> javadoc AlternativeView? (We can browse through all classes, 
which
+                     are part of the diagram.)
+
+    UML in javadoc -> reST    Detail->Summary
+
+    UML in reST -> Javadoc General->Spesific or Summary->Detail
+
+  Trigg classifies the following type-pairs for bi-directional links, which 
can are
+  interpreted oppositionally depending on the direction
+
+  Generalization/Specification
+  Abstraction/Example 
+  Formalization/Application
+  Summarization/Detail
+  Simplification/Complication
+
+  Could Generalization/Specification be best for reST<->Javadoc.  
+
 
 Implementation
 ==============