[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 06:40:54

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

Log message:
        Resolve

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

Patches:
Index: fenfire/docs/pegboard/vocabprocess--tjl/peg.rst
diff -u fenfire/docs/pegboard/vocabprocess--tjl/peg.rst:1.4 
fenfire/docs/pegboard/vocabprocess--tjl/peg.rst:1.5
--- fenfire/docs/pegboard/vocabprocess--tjl/peg.rst:1.4 Mon May 12 06:31:47 2003
+++ fenfire/docs/pegboard/vocabprocess--tjl/peg.rst     Mon May 12 06:40:54 2003
@@ -3,8 +3,8 @@
 =============================================================
 
 :Author:   Tuomas J. Lukka
-:Last-Modified: $Date: 2003/05/12 10:31:47 $
-:Revision: $Revision: 1.4 $
+:Last-Modified: $Date: 2003/05/12 10:40:54 $
+:Revision: $Revision: 1.5 $
 :Status:   Current
 
 It seems that vocabularies are easy to create but difficult
@@ -47,7 +47,7 @@
 
 - Should we merge spatial into canvas2d?
 
-    SUGGESTED RESOLUTION Can you give me an example where spatial would
+    RESOLVED: Yes. Can you give me an example where spatial would
     be used without canvas2d?  The point is, the x and y coordinates
     are pretty specific to canvases, and while I see containment + x +
     y as a reasonable structure orthogonal to everything else, separating
@@ -55,31 +55,36 @@
 
     Also, if it's spatial, it should also have z ;)
 
+    It would be acceptable to have Spatial be a *superclass* of Canvas2D, 
+    but this might not be worth the trouble.
+
 - What should be the namespace prefix? ``vocabulary``,
   ``rdf`` or ``terms`` or ``rdfv``?
 
+    RESOLVED: ``rdf-v``. For "RDF Vocabulary", which mentions
+    the term RDF as well as that this is not just RDF, it's something else.
+
 - Should URIs contain timestamps?
 
-    RESOLVED: YES. XXX PEG not changed yet.
+    RESOLVED: [benja:] ::
 
-    [benja:]
-    > - NEVER use URIs you want to be permanent without a timestamp.
-    >
-    > Actually the above could be used with a timestamp, but you don't
-    > explicitly say so. Please define a full template for namespaces. I
-    > suggest::
-    >
-    >     http://fenfire.org/terms/YYYY/MM/[DD/]namespacename
-    >
-    > where ``YYYY``, ``MM``, ``DD`` are the date (or month) when the
-    > namespace was created, and ``namespacename`` is chosen by the person
-    > creating the namespace. (DD is optional.)
-    >
-    > Items in the namespace would have the form::
-    >
-    >     http://fenfire.org/terms/YYYY/MM/[DD/]namespacename#id
-    >
-    > where ``id`` is chosen by the person creating the namespace.
+       > - NEVER use URIs you want to be permanent without a timestamp.
+       >
+       > Actually the above could be used with a timestamp, but you don't
+       > explicitly say so. Please define a full template for namespaces. I
+       > suggest::
+       >
+       >     http://fenfire.org/terms/YYYY/MM/[DD/]namespacename
+       >
+       > where ``YYYY``, ``MM``, ``DD`` are the date (or month) when the
+       > namespace was created, and ``namespacename`` is chosen by the person
+       > creating the namespace. (DD is optional.)
+       >
+       > Items in the namespace would have the form::
+       >
+       >     http://fenfire.org/terms/YYYY/MM/[DD/]namespacename#id
+       >
+       > where ``id`` is chosen by the person creating the namespace.
 
 - Should we separate cLink from FF? A separate CLink namespace?
 
@@ -87,18 +92,23 @@
 
 - Should we merge PP (directed links) into FF, or something else? 
 
-    RESOLUTION: Move to DLINK, Analogous to CLink and Canvas2D, 
+    RESOLVED: Move to DLINK, Analogous to CLink and Canvas2D, 
     this property creates its own orthogonal substructure. 
 
 - What should the types of coordx, coordy be? Float? Int? Numeric?
 
+    RESOLVED: Floats. We use them with all coordinate systems anyway.
+    If you want gridding, it's something for the UI to provide.
+
 - Should each vocabulary also define its "identity", a RDF node that 
   is used to talk about that vocabulary. This could be useful for describing
   the schema of some data, e.g. "This is spatial canvas data with dLinks".
 
+    RESOLVED: Not yet. While this might be nice, it needs further thinking.
+
 - Where should the RDF schemas the objects be defined?
 
-XXX Change changes to retained, + javadoc
+    RESOLVED: Not yet. A further PEG will address this issue.
 
 Changes
 =======
@@ -131,11 +141,18 @@
 
 Freeze ``org.fenfire.vocab``. Changes only through PEG process.
 
-Change the prefix ``http://fenfire.org/vocabulary``
-to ``http://fenfire.org/rdf``.
+Change the prefix ``http://fenfire.org/vocabulary/``
+to ``http://fenfire.org/rdf-v/``.
+After the prefix, each namespace shall contain the year and month it was 
originally
+defined in, in the form
+``2003/05/``. After that, the name of the namespace, lowercase, with .html 
-suffix.
+So, for instance, FF.content would be
+``http://fenfire.org/rdf-v/2003/05/fenfire.html#content``.
+
 
 All new words define without PEG go into org.fenfire.vocab.lava
-and use the prefix ``http://fenfire.org/EXPERIMENTAL/rdf``.
+and use the prefix ``http://fenfire.org/EXPERIMENTAL/rdf-v``, after 
+which the URI continues as above.
 
 All entries in vocabulary classes shall have their **official**
 definitions there, in their javadocs. There shall be no members
@@ -222,7 +239,7 @@
        static public Object contains;
        /** The x and y coordinates of a node on a canvas.
         * (node, x, literal), where the literal is parseable
-        * as an integer (XXX).
+        * as a float. 
         * Note that these are the <em>default</em> coordinate
         * properties: later on, we might make it possible for a Canvas2D
         * to define its own coordinate attributes, which would take