[Gzz-commits] fenfire/docs/pegboard markup_xhtmlmodules--tjl/...

[Tuomas J. Lukka]

CVSROOT:        /cvsroot/fenfire
Module name:    fenfire
Changes by:     Tuomas J. Lukka <address@hidden>        03/04/09 15:24:47

Modified files:
        docs/pegboard/markup_xhtmlmodules--tjl: peg.rst 
        docs/pegboard/swamp_rdf_api--tjl: peg.rst 

Log message:
        Adjustments from discussion with benja. Peer review RULEZ

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

Patches:
Index: fenfire/docs/pegboard/markup_xhtmlmodules--tjl/peg.rst
diff -u fenfire/docs/pegboard/markup_xhtmlmodules--tjl/peg.rst:1.2 
fenfire/docs/pegboard/markup_xhtmlmodules--tjl/peg.rst:1.3
--- fenfire/docs/pegboard/markup_xhtmlmodules--tjl/peg.rst:1.2  Tue Apr  8 
16:31:05 2003
+++ fenfire/docs/pegboard/markup_xhtmlmodules--tjl/peg.rst      Wed Apr  9 
15:24:47 2003
@@ -3,12 +3,13 @@
 =============================================================
 
 :Author:   Tuomas J. Lukka
-:Last-Modified: $Date: 2003/04/08 20:31:05 $
-:Revision: $Revision: 1.2 $
+:Last-Modified: $Date: 2003/04/09 19:24:47 $
+:Revision: $Revision: 1.3 $
 :Status:   Current
 
 Marked-up text has always been a difficult but focal point for us.  
 This PEG proposes using some modules from modularized XHTML
+(http://www.w3.org/TR/xhtml-modularization/, http://www.w3.org/TR/xhtml11/)
 to accomplish it.
 
 This PEG extends the Alph PEG ``styled_text--benja`` by providing
Index: fenfire/docs/pegboard/swamp_rdf_api--tjl/peg.rst
diff -u fenfire/docs/pegboard/swamp_rdf_api--tjl/peg.rst:1.5 
fenfire/docs/pegboard/swamp_rdf_api--tjl/peg.rst:1.6
--- fenfire/docs/pegboard/swamp_rdf_api--tjl/peg.rst:1.5        Tue Apr  8 
08:03:02 2003
+++ fenfire/docs/pegboard/swamp_rdf_api--tjl/peg.rst    Wed Apr  9 15:24:47 2003
@@ -3,8 +3,8 @@
 =============================================================
 
 :Author:   Tuomas J. Lukka
-:Last-Modified: $Date: 2003/04/08 12:03:02 $
-:Revision: $Revision: 1.5 $
+:Last-Modified: $Date: 2003/04/09 19:24:47 $
+:Revision: $Revision: 1.6 $
 :Status:   Current
 
 This document outlines the main issues in the Jena api
@@ -80,6 +80,41 @@
 
     Quite likely code generation will be used.
 
+    However, we shall also provide less efficient but more comfortable
+    versions which take null as the wildcard.
+
+- The non-OO approach is not nice for some code. Could we use OO instead?
+
+    RESOLVED: No. Need for speed.
+
+    HOWEVER, it's pretty simple to build an OO API on top for the less 
+    speed-sensitive locations ::
+
+       class OONode {
+           Graph g;
+           Object node;
+           ...
+       }
+
+    and use it as ::
+
+       person = OONode(thePersonNode);
+       name = person.getProperty(nameProperty);
+
+- What should the RDF model/graph/thing be called? You know, the 
+  set of triples?
+
+    RESOLVED: Graph. A nice word, and has images with it that may
+    help us leave the word "space" behind.
+
+- how should the methods in Graph be named?
+
+    Open. I'm still flexible about this.
+
+- What should the resource mapper and its methods be called? RMap? 
+  Nodes?
+
+    Still open, under consideration.
 
 Problems with jena
 ==================
@@ -102,7 +137,7 @@
 
 Efficiency is also important: in order for Fenfire to work properly,
 *ALL* searches within memory must be O(1). Jena makes no guarantees,
-since its goal is to support different implementations of Model.
+since its goal is to support different implementations of Graph.
 For us, the different implementations do not matter so much as raw
 efficiency of the memory-based implementation. This is quite different
 from most RDF uses, since the usual scenario is that there is not too much
@@ -156,7 +191,7 @@
 To avoid this, we'll drop the semantics (subject,predicate,object) for now
 and name all methods according to a general scheme. ::
 
-    public interface ConstFirstOrderModel {
+    public interface ConstFirstOrderGraph {
        public Object find1_11X(Object subject, Object predicate);
        public Object find1_X11(Object predicate, Object subject);
        ...
@@ -164,7 +199,7 @@
        ...
     }
 
-    public interface FirstOrderModel extends ConstFirstOrderModel {
+    public interface FirstOrderGraph extends ConstFirstOrderGraph {
        public void set1_11X(Object subject, Object predicate, Object object);
        public void set1_X11(Object subject, Object predicate, Object object);
        ...