ripple - Project Hosting on Google Code

Older Nov 21, 2009 issue 44 (Lisp-style list primitives) Labels changed by parcour - Labels: Libraries Labels: Libraries Nov 21, 2009 issue 44 (Lisp-style list primitives) reported by parcour - Ripple includes the 'first' and 'rest' primitives, among others, for accessing list members. Lisp also includes 'second', 'last', 'nth', and possibly others which may be handy. Implement some of these. Ripple includes the 'first' and 'rest' primitives, among others, for accessing list members. Lisp also includes 'second', 'last', 'nth', and possibly others which may be handy. Implement some of these. Nov 03, 2009 KeywordsAndSpecialURIs Wiki page commented on by turnguard - thanks for and congrats to this great work! wkr www.turnguard.com thanks for and congrats to this great work! wkr www.turnguard.com Sep 08, 2009 r119 ([No log message]) committed by parcour - [No log message] [No log message] Aug 29, 2009 r118 ([No log message]) committed by parcour - [No log message] [No log message] Aug 14, 2009 r117 (Odds and ends.) committed by parcour - Odds and ends. Odds and ends. Aug 14, 2009 r116 (Renamed Maven package for LinkedDataSail, further decoupling...) committed by parcour - Renamed Maven package for LinkedDataSail, further decoupling it from Ripple. Note: there are still code dependencies. Renamed Maven package for LinkedDataSail, further decoupling it from Ripple. Note: there are still code dependencies. Aug 13, 2009 issue 43 (handle SecurityExceptions gracefully) reported by parcour - Currently, Ripple would not. Currently, Ripple would not. Aug 08, 2009 issue 42 (Ripple ScriptEngine implementation) reported by parcour - Implement javax.script.ScriptEngine (present in Java 1.6). Implement javax.script.ScriptEngine (present in Java 1.6). Aug 08, 2009 ripple-0.5.0.zip (Ripple 0.5 -- August 2009) file uploaded by parcour Aug 08, 2009 ripple-0.4.2.zip (Ripple 0.4) file uploaded by parcour Aug 08, 2009 ripple-0.3.0.zip (Ripple 0.3 (SFSW version) -- June 2007) file uploaded by parcour Aug 08, 2009 ripple-0.2.1.tar.gz (Ripple 0.2 -- May 2007) file uploaded by parcour Aug 08, 2009 ripple-0.1.2.tar.gz (Ripple 0.1.2 -- April 2007) file uploaded by parcour Aug 08, 2009 demo-cache.rdf (Ripple 0.1.1 demo cache -- April 2007) file uploaded by parcour Aug 08, 2009 ripple-0.1.1.tar.gz (Ripple 0.1.1 -- April 2007) file uploaded by parcour Aug 08, 2009 ripple-0.1.tar.gz (Ripple SFSW2007 release) file uploaded by parcour Aug 08, 2009 ripple-0.4.2.zip (Ripple 0.4) file uploaded by parcour Aug 08, 2009 r115 (Set MIME types for screencast files so that they can (hopefu...) committed by parcour - Set MIME types for screencast files so that they can (hopefully) be served directly out of the repository. Set MIME types for screencast files so that they can (hopefully) be served directly out of the repository. Aug 08, 2009 r114 (Added SFSW screencast to docs.) committed by parcour - Added SFSW screencast to docs. Added SFSW screencast to docs. Aug 06, 2009 r113 (Misc. recent changes.) committed by parcour - Misc. recent changes. Misc. recent changes. Jun 01, 2009 issue 41 (connection error when using AllegroSail) reported by parcour - This error frequently appears in ripple.log while using Ripple on AllegroSail, although it doesn't cause any other obvious problems: 2009-06-01 11:34:40,678 [main] ERROR SesameModelConnection - tried to close an already-closed connection It's unknown whether this is a Ripple issue or an AllegroSail issue. This error frequently appears in ripple.log while using Ripple on AllegroSail, although it doesn't cause any other obvious problems: 2009-06-01 11:34:40,678 [main] ERROR SesameModelConnection - tried to close an already-closed connection It's unknown whether this is a Ripple issue or an AllegroSail issue. May 29, 2009 issue 33 (Missing maven artifacts) Status changed by parcour - Fixed -- the server is back up... and down... and up again. I need to find a more stable home for fortytwo.net. However, the Maven repository at http://fortytwo.net/maven2 is now browseable. Thanks for reporting the issue. Status: Fixed Fixed -- the server is back up... and down... and up again. I need to find a more stable home for fortytwo.net. However, the Maven repository at http://fortytwo.net/maven2 is now browseable. Thanks for reporting the issue. Status: Fixed May 29, 2009 issue 37 (non-terminating decimals) Labels changed by parcour - Labels: Model Labels: Model May 29, 2009 issue 18 (program/list ambiguity with stream:each (0.5-dev)) Labels changed by parcour - Labels: Model Labels: Model May 29, 2009 issue 4 (RDF lists and native lists serialize differently) Labels changed by parcour - Labels: Model Labels: Model May 29, 2009 issue 27 (allow empty stacks) Labels changed by parcour - Labels: Model Labels: Model May 29, 2009 issue 8 (dereferencer fails due to trailing slash) Labels changed by parcour - Labels: LinkedDataSail Labels: LinkedDataSail May 29, 2009 issue 14 (strange "unknown host" error) Labels changed by parcour - Labels: LinkedDataSail Labels: LinkedDataSail May 29, 2009 issue 21 (implement recursion primitives) Labels changed by parcour - Labels: Libraries Labels: Libraries May 29, 2009 issue 16 (stack:ifte is not the same as Joy's ifte) Labels changed by parcour - Labels: Libraries Labels: Libraries May 29, 2009 issue 15 (clean up or automate library API descriptions) Labels changed by parcour - Labels: Libraries Labels: Libraries May 29, 2009 issue 5 (services:uriqr primitive is outdated) Labels changed by parcour - Labels: Libraries Labels: Libraries May 29, 2009 issue 35 (make application operators tolerant of white space) Labels changed by parcour - Labels: Syntax Labels: Syntax May 29, 2009 issue 34 (command-line hangs on bad @prefix URI) Labels changed by parcour - Labels: Syntax Labels: Syntax May 29, 2009 issue 24 (white space within long URIs) Labels changed by parcour - Labels: Syntax Labels: Syntax May 29, 2009 issue 3 (empty URI literal causes parse error) Labels changed by parcour - Labels: Syntax Labels: Syntax May 29, 2009 issue 10 (tab completion doesn't work on Windows) Labels changed by parcour - Labels: Lexicon Labels: Lexicon May 29, 2009 issue 2 (tab completion fails between prefix and local name) Labels changed by parcour - Labels: Lexicon Labels: Lexicon May 29, 2009 issue 12 (query engine should not redefine the default namespace) Labels changed by parcour - Labels: Lexicon Labels: Lexicon May 29, 2009 issue 25 (@base directive) Labels changed by parcour - Labels: Lexicon Labels: Lexicon May 29, 2009 issue 38 (lexicon should be session-specific) changed by parcour - Summary: lexicon should be session-specific Labels: Lexicon Summary: lexicon should be session-specific Labels: Lexicon May 29, 2009 issue 40 (@keyword directive) Labels changed by parcour - Labels: Lexicon Labels: Lexicon May 29, 2009 issue 36 (exclude deprecated keywords from tab completion results) Labels changed by parcour - Labels: Lexicon Labels: Lexicon May 29, 2009 issue 39 (display lexicon state before the command prompt) Labels changed by parcour - Labels: Lexicon Labels: Lexicon May 29, 2009 issue 1 (Turtle view shouldn't use reverse keyword map) Labels changed by parcour - Labels: Lexicon Labels: Lexicon May 29, 2009 issue 24 (white space within long URIs) commented on by parcour - Does Turtle support them? Does Turtle support them? May 29, 2009 issue 40 (@keyword directive) reported by parcour - One outstanding problem in interpreting Ripple programs independently of a query engine (among other things, preventing Ripple from being a proper RDF format) is that keyword bindings are not explicitly given. Thus, the meaning of any source code which uses keywords depends on the configuration of libraries and primitives in the Ripple environment, which is by no means constant. Providing a way to explicitly define keywords would: 1) make "complete", self-contained Ripple source files possible, and as an added benefit, 2) allow users to create keywords for resources which are important to their applications This syntax would be handy: @keyword foo: <http://example.org/ns#foo> . This clashes a bit with N3's @keywords directive. However, @keywords apparently makes reference to the default namespace, so you'd have to use it in conjunction with @prefix, in a rather awkward way, in order to achieve the desired effect. One outstanding problem in interpreting Ripple programs independently of a query engine (among other things, preventing Ripple from being a proper RDF format) is that keyword bindings are not explicitly given. Thus, the meaning of any source code which uses keywords depends on the configuration of libraries and primitives in the Ripple environment, which is by no means constant. Providing a way to explicitly define keywords would: 1) make "complete", self-contained Ripple source files possible, and as an added benefit, 2) allow users to create keywords for resources which are important to their applications This syntax would be handy: @keyword foo: <http://example.org/ns#foo> . This clashes a bit with N3's @keywords directive. However, @keywords apparently makes reference to the default namespace, so you'd have to use it in conjunction with @prefix, in a rather awkward way, in order to achieve the desired effect. May 29, 2009 issue 39 (display lexicon state before the command prompt) commented on by parcour - On a related note: when namespace definitions are automatically added in the course of importing data, the user should be notified, e.g. 0) @prefix : <http://ripple.fortytwo.net/code/examples#> . 1) :timbl >> . [1] ... ... 0) @prefix foaf: <http://xmlns.com/foaf/0.1/> . 0) @prefix rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> . 0) @prefix rdfs: <http://www.w3.org/2000/01/rdf-schema#> . 2) If there is ever such a thing as an input log, these implicit directives should be made explicit by adding them to the log. On a related note: when namespace definitions are automatically added in the course of importing data, the user should be notified, e.g. 0) @prefix : <http://ripple.fortytwo.net/code/examples#> . 1) :timbl >> . [1] ... ... 0) @prefix foaf: <http://xmlns.com/foaf/0.1/> . 0) @prefix rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> . 0) @prefix rdfs: <http://www.w3.org/2000/01/rdf-schema#> . 2) If there is ever such a thing as an input log, these implicit directives should be made explicit by adding them to the log. May 29, 2009 issue 39 (display lexicon state before the command prompt) Summary changed by parcour - Summary: display lexicon state before the command prompt Summary: display lexicon state before the command prompt

issue 40 (@keyword directive) reported by parcour - One outstanding problem in interpreting Ripple programs independently of a query engine (among other things, preventing Ripple from being a proper RDF format) is that keyword bindings are not explicitly given. Thus, the meaning of any source code which uses keywords depends on the configuration of libraries and primitives in the Ripple environment, which is by no means constant. Providing a way to explicitly define keywords would: 1) make "complete", self-contained Ripple source files possible, and as an added benefit, 2) allow users to create keywords for resources which are important to their applications This syntax would be handy: @keyword foo: <http://example.org/ns#foo> . This clashes a bit with N3's @keywords directive. However, @keywords apparently makes reference to the default namespace, so you'd have to use it in conjunction with @prefix, in a rather awkward way, in order to achieve the desired effect.

One outstanding problem in interpreting Ripple programs independently of a query engine (among other things, preventing Ripple from being a proper RDF format) is that keyword bindings are not explicitly given. Thus, the meaning of any source code which uses keywords depends on the configuration of libraries and primitives in the Ripple environment, which is by no means constant. Providing a way to explicitly define keywords would: 1) make "complete", self-contained Ripple source files possible, and as an added benefit, 2) allow users to create keywords for resources which are important to their applications This syntax would be handy: @keyword foo: <http://example.org/ns#foo> . This clashes a bit with N3's @keywords directive. However, @keywords apparently makes reference to the default namespace, so you'd have to use it in conjunction with @prefix, in a rather awkward way, in order to achieve the desired effect.

Older