[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 00:54:27

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

Log message:
        Benja's commetns - some not yet finished

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

Patches:
Index: fenfire/docs/pegboard/vocabprocess--tjl/peg.rst
diff -u fenfire/docs/pegboard/vocabprocess--tjl/peg.rst:1.2 
fenfire/docs/pegboard/vocabprocess--tjl/peg.rst:1.3
--- fenfire/docs/pegboard/vocabprocess--tjl/peg.rst:1.2 Mon May 12 00:45:54 2003
+++ fenfire/docs/pegboard/vocabprocess--tjl/peg.rst     Mon May 12 00:54:27 2003
@@ -3,8 +3,8 @@
 =============================================================
 
 :Author:   Tuomas J. Lukka
-:Last-Modified: $Date: 2003/05/12 04:45:54 $
-:Revision: $Revision: 1.2 $
+:Last-Modified: $Date: 2003/05/12 04:54:27 $
+:Revision: $Revision: 1.3 $
 :Status:   Current
 
 It seems that vocabularies are easy to create but difficult
@@ -25,6 +25,17 @@
     Any URI in the experimental space should not be widely used
     before being properly defined and accepted.
 
+    It is desirable to be able to *see* from the URI which data is
+    stable, which is not, without having to look at the definitions.
+
+    For example, grepping for the experimental ns from a file would
+    give you a good idea whether your data is based on stable code.
+
+    The idea is also that conversion wouldn't be too often necessary:
+    the move from lava to real wouldn't require too much work, just a PEG
+    round.
+
+
 - What about ALPH? How much should we be defining ALPH things
   here, outside Alph proper?
 
@@ -45,6 +56,35 @@
     Also, if it's spatial, it should also have z ;)
 
 - Should we merge PP (directed links) into FF? 
+
+- What should be the namespace prefix? ``vocabulary``,
+  ``rdf`` or ``terms`` or ``rdfv``?
+
+- Should URIs contain timestamps?
+
+    RESOLVED: YES. XXX PEG not changed yet.
+
+    [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.
+
+
+XXX Change changes to retained, + javadoc
 
 Changes
 =======