gzz-commits
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Gzz-commits] fenfire docs/pegboard/swamp_rdf_api--tjl/peg.rs...


From: Tuomas J. Lukka
Subject: [Gzz-commits] fenfire docs/pegboard/swamp_rdf_api--tjl/peg.rs...
Date: Tue, 15 Apr 2003 05:03:50 -0400

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

Modified files:
        docs/pegboard/swamp_rdf_api--tjl: peg.rst 
        org/fenfire/util: pagespanpaper.test 

Log message:
        Benja's comments

CVSWeb URLs:
http://savannah.gnu.org/cgi-bin/viewcvs/fenfire/fenfire/docs/pegboard/swamp_rdf_api--tjl/peg.rst.diff?tr1=1.11&tr2=1.12&r1=text&r2=text
http://savannah.gnu.org/cgi-bin/viewcvs/fenfire/fenfire/org/fenfire/util/pagespanpaper.test.diff?tr1=1.8&tr2=1.9&r1=text&r2=text

Patches:
Index: fenfire/docs/pegboard/swamp_rdf_api--tjl/peg.rst
diff -u fenfire/docs/pegboard/swamp_rdf_api--tjl/peg.rst:1.11 
fenfire/docs/pegboard/swamp_rdf_api--tjl/peg.rst:1.12
--- fenfire/docs/pegboard/swamp_rdf_api--tjl/peg.rst:1.11       Sun Apr 13 
03:49:05 2003
+++ fenfire/docs/pegboard/swamp_rdf_api--tjl/peg.rst    Tue Apr 15 05:03:50 2003
@@ -3,8 +3,8 @@
 =============================================================
 
 :Author:   Tuomas J. Lukka
-:Last-Modified: $Date: 2003/04/13 07:49:05 $
-:Revision: $Revision: 1.11 $
+:Last-Modified: $Date: 2003/04/15 09:03:50 $
+:Revision: $Revision: 1.12 $
 :Status:   Current, Partially preliminarily implemented (since in its own 
package)
 
 This document outlines the main issues in the Jena api
@@ -29,9 +29,10 @@
     RESOLVED: Implicit observing, since we *can* wrap all parts
     of the API without too much cost. If the API is non-object-oriented,
     in the sense that the individual nodes and statements are not tied 
-    to any model/space, we only need to wrap O(1) objects.
+    to any graph, we only need to wrap O(1) objects.
 
-    Additionally, we can cheaply make "derived" models, 
+    Additionally, we can cheaply make "derived" graphs (i.e.
+    graph H(G) which is a function of the other graph G), 
     e.g. when implementing the model_versions--tjl stuff.
 
 - How should resources and properties be represented?
@@ -48,6 +49,9 @@
 
     For properties and other such resources, interned strings should be 
sufficient.
 
+    Of course, the Nodes class will decide at get() time what representation
+    to use and that representation will be valid everywhere.
+
 - How should literals be represented?
 
     RESOLVED: As immutable Literal objects, with several types of accessors.
@@ -135,7 +139,10 @@
       <benja> so that graphs would cache a few, and only create new ones if 
too many in 
       use simultaneously
 
-    Thinking.
+  Lots of possibilities.
+
+    RESOLVED: At first, Iterators.
+    Suffixing the return type name will help add / change this later.
 
 - What about queries with more than one component? Say, "give me all triples",
   or "give me all property-value pairs for the given subject node"
@@ -151,6 +158,9 @@
     RESOLVED: Not yet. We may, at some point, want to put in the functional
     part right into swamp itself...
 
+- How are anonymous nodes represented?
+
+- Literals: searching for, languages, uniqueness?
 
 Problems with jena
 ==================
@@ -211,6 +221,9 @@
         * when serializing a space.
         */
        public static void appendToString(Object res, StringBuffer buf);
+
+       public static void write(Object res, OutputStream stream) throws 
IOException;
+       public static void write(Object res, Writer stream) throws IOException;
     }
 
 The appendToString method solves one problem we had in Gzz: when saving,
@@ -289,7 +302,7 @@
        Only 1 and X may be used.
 
     rm
-       Remove the matching triples from the model. Any amount of Xs
+       Remove the matching triples from the model. Any amount of As
        may be used.
 
 and, after an underscore, the parameter scheme:
@@ -315,6 +328,17 @@
     }
 
 The wildcards are set to null.
+
+For example, if the user calls ::
+
+    graph.find1_11X(foo, bar);
+
+and there are the triples (foo, bar, baz) and (foo, bar, zip) in the model,
+then ::
+
+    NotUniqueError(foo, bar, null)
+
+is generated.
 
 Observing
 ---------
Index: fenfire/org/fenfire/util/pagespanpaper.test
diff -u fenfire/org/fenfire/util/pagespanpaper.test:1.8 
fenfire/org/fenfire/util/pagespanpaper.test:1.9
--- fenfire/org/fenfire/util/pagespanpaper.test:1.8     Thu Apr 10 14:01:50 2003
+++ fenfire/org/fenfire/util/pagespanpaper.test Tue Apr 15 05:03:50 2003
@@ -62,7 +62,7 @@
     global sc
 
     id = "01ACE8A2E202A26072012715A94A270CD012F9B0F2"
-    sc = alph.impl.PageImageScroll(None, storm.Mediaserver.Id(id))
+    sc = alph.impl.PageImageScroll(None, storm.BlockId(id))
 
 def testTestSpan():
     """Test that we really have the pagespan images.




reply via email to

[Prev in Thread] Current Thread [Next in Thread]