[Gzz-commits] fenfire/docs/pegboard/vocabprocess--tjl peg.rst

[Tuomas J. Lukka]

CVSROOT:        /cvsroot/fenfire
Module name:    fenfire
Changes by:     Tuomas J. Lukka <address@hidden>        03/05/12 11:25:28

Modified files:
        docs/pegboard/vocabprocess--tjl: peg.rst 

Log message:
        PEG names

CVSWeb URLs:
http://savannah.gnu.org/cgi-bin/viewcvs/fenfire/fenfire/docs/pegboard/vocabprocess--tjl/peg.rst.diff?tr1=1.9&tr2=1.10&r1=text&r2=text

Patches:
Index: fenfire/docs/pegboard/vocabprocess--tjl/peg.rst
diff -u fenfire/docs/pegboard/vocabprocess--tjl/peg.rst:1.9 
fenfire/docs/pegboard/vocabprocess--tjl/peg.rst:1.10
--- fenfire/docs/pegboard/vocabprocess--tjl/peg.rst:1.9 Mon May 12 11:15:05 2003
+++ fenfire/docs/pegboard/vocabprocess--tjl/peg.rst     Mon May 12 11:25:28 2003
@@ -3,8 +3,8 @@
 =============================================================
 
 :Author:   Tuomas J. Lukka
-:Last-Modified: $Date: 2003/05/12 15:15:05 $
-:Revision: $Revision: 1.9 $
+:Last-Modified: $Date: 2003/05/12 15:25:28 $
+:Revision: $Revision: 1.10 $
 :Status:   Current
 
 It seems that vocabularies are easy to create but difficult
@@ -138,13 +138,14 @@
 class should be relatively independent of the other vocabularies.
 
 For instance, a spatial canvas is a reasonable unit: there is a canvas,
-it contains certain nodes at certain locations. However, the PP links
-(now dLinks) or xu links (now CLinks) between different canvases do not
+it contains certain nodes at certain locations. However, structlinks
+or content links between different canvases do not
 actually belong in the same place; they are orthogonal to the spatial
 structure.
 
-Currently, our code is pretty well along this structure: CanvasView2D takes
-care of the spatial canvas, and PPConnector (name needs to change) of the 
dLinks.
+Currently, our code is pretty well along this structure: CanvasView2D
+takes care of the spatial canvas, and PPConnector (name needs to change)
+of the structlinks.
 
 The more independent we can make the codes using the different
 orthogonal structural pieces, the easier it will be to
@@ -221,28 +222,28 @@
        static public final Object content;
     }
 
-CLINK
-"""""
+CONTENTLINK
+"""""""""""
 
 A new namespace for Xanalogical content links.
 Javadoc::
 
     /** RDF Vocabulary of content links.
      */
-    public class FF {
+    public class CONTENTLINK {
        static public final String _nsId = 
            "http://fenfire.org/rdf-v/2003/05/clink";;
 
        /** The RDF class for content links. An node which is a content link
         * must have both the cLinkFrom and cLinkTo properties.
         */
-       static public final Object CLink;
+       static public final Object Link;
        /** The Alph-parseable enfilade XML literal of a content link from-end.
         */
-       static public final Object cLinkFrom;
+       static public final Object from;
        /** The Alph-parseable enfilade XML literal of a content link to-end.
         */
-       static public final Object cLinkTo;
+       static public final Object to;
     }
 
 
@@ -290,24 +291,23 @@
 PP is really a special-case user interface for a subset of the full
 fenfire structure, so it's quite reasonable not to include a special 
vocabulary for it.
 
-DLINK
+STRUCTLINK
 """""
 
 New class for what used to be called PP connections (directed, typeless 
connections). 
-Name comes from "Directed LINK".
 Javadoc::
 
     /** RDF vocabulary for directed (so far typeless)
      * one-to-one links.
      */
-    public class DLINK {
+    public class STRUCTLINK {
        static public final String _nsId = 
            "http://fenfire.org/rdf-v/2003/05/dlink";;
 
        /** The directed link association.
         * A and B are linked by the tuple (A, DLINK.dLink, B)
         */
-       static public final Object dLink;
+       static public final Object linkedTo;
     }