As a convenience, the Ripple command-line interface assumes all
prefix/namespace definitions defined in the current environment, and allows
the programmer to use them without first explicitly defining them. So, for
instance, if the foaf: namespace is defined in the triple store to which
Ripple is connected, there is no need to redefine it before typing
"foaf:name". However, this has proven a little confusing, as well. A
SemWeb-savvy first-time user neither knows about these pre-defined
namespaces nor understands why an example with a QName like ":timbl" is
legal when the namespace in question has apparently not been defined. It
might be very helpful to print these namespaces, as well as a default @base
directive if it is defined, before the first line of input. For example,
$ ./ripple.sh linkedDataNS.properties
0) @prefix : <http://ripple.fortytwo.net/code/examples#> .
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#> .
1) :timbl >> foaf:knows >> .
Original link: http://code.google.com/p/ripple/issues/detail?id=39