On 18/02/11 09:33, Rob Vesse wrote:


Hi Andy et al

As previously discussed I have been working on a command
line for SPARQL over HTTP that runs on Windows and as far as possible I am
trying to make the command line syntax and behaviours identical to your soh
scripts. This should hopefully be finished and released within a fortnight.


Since I don't have regular access to a Linux system to test the scripts
behaviours myself can you clarify the following for me.

Install (j)ruby on windows for testing?


Regarding the
optional file argument for protocol scripts (s-get, s-put, s-head,
s-delete):

        * When used with s-get should that direct output to that
file instead of the Console

No - s-get does not take a file argument. There is an error if you give it one (not a helpful error yet ... fixing ... !)

It writes to stdout always.

        * Assume is required for s-put

Yes

        * Assume it
has no meaning for s-head and s-delete

As s-get - no file argument allowed.


With s-put is there any way for the
user to access the special case of the POST operation whereby a Graph is
not specified and the server creates a new Graph with their POSTed triples
and returns them the new Graph URI. Or is this feature not supported by soh
and/or Fuseki yet?

Graphs are created if needed.

fuseki-server --mem --update /ds &
s-post http://localhost:3030/ds http://example/ D.nt
s-get http://localhost:3030/ds http://example/

works for me.


Regarding the usage syntax the scripts produce,
s-query and s-update show | @file at the end of their usage. I assume this
is just to suggest that the user should pipe the output to the given
file/utility instead of it going to the Console by default?

Mistake - will fix.


Some of the
arguments listed are of the form --ARG=value and some are --ARG value - is
there actually intended to be any difference in the two syntaxes. For ease
of use and implementation I have assumed that any argument can be used
either way for my implementation.

No difference. It's Ruby's command line parser although it's like ARQ's java one.


Thanks,

Rob Vesse

        Andy

Reply via email to