SHARE Client as Service

[Nicholas Del Rio]

Hello SADI team,

Is there any other interface to the SHARE client other than the HTML query page?  Perhaps some kind of RESTFull service capability?

Thanks,

Nick

[Mark Wilkinson]

Hi Nick,

I'm fairly sure it is possible to do what you want (Luke can confirm) -
there is a command-line SHARE client
(http://code.google.com/p/sadi/wiki/SHAREClient) that you could wrap to be
"RESTful". I doubt that we have a RESTful interface to our instance of
SHARE, but I request that you don't use our instance to do what you want
to do anyway :-)

It's fairly easy to set-up an instance of SHARE, and I think Luke is close
to getting an image that can be deployed on one of the public clouds too.

I'll wait for his reply before I say any more, since I'm not sure of the
current status of that project.

Cheers!

M

[Nicholas Del Rio]

Thanks for your reply!

We have our own SHARE deployment that coordinates the execution of some biodiversity modeling services.  We also have a GUI that lets users specify the biodiversity modeling constraints, specified in OWL, and I need to hook this GUI up to the SHARE client to let it do its magic. I was thinking of wrapping our SHARE deployment as a W3C sparql endpoint and let the GUI pose the modeling queries.

Thanks for pointing me to the command line tool :-) I would be very happy to wrap the command-line client or interface with the Java code behind the command line client directly if possible.

Thanks,

Nick

[Alexandre Riazanov]

Hi Nicholas,

If you have interesting Life Science-related use cases for SADI querying, I suggest you to also consider subscribing for closed beta testing of our commercial query engine HYDRA: http://ipsnp.wikidot.com/call-for-beta-testers

Best regards,

--
You received this message because you are subscribed to the Google Groups "sadi-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to sadi-dev+u...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

--
======================================
Alexandre Riazanov (Alexander Ryazanov), PhD
Saint John, New Brunswick, Canada
Skype: alexandre.riazanov
http://www.freewebs.com/riazanov/
http://www.linkedin.com/in/riazanov
http://www.unbsj.ca/sase/csas/faculty.php
======================================

[Luke McCarthy]

The CardioSHARE web app exposes a JSON interface that is used by the HTML query page, so you could co-opt that. It is nothing like RESTful, but it is there.

Briefly, the protocol goes like this:

request: http://server/path/to/cardioSHARE/query?query=… (either GET or POST)

response: {success: true, taskId: $TASK_ID}

request: http://server/path/to/cardioSHARE/query?poll=$TASK_ID

response: one of 

a simple JSON string with a status message (if the query is still being processed) OR

{fields: [list, of, variable, names], rows: [list, of, bindings], error: [list, of, error, messages], warnings: [list, of, warning, messages]}

Cheers,

Luke

[Nicholas Del Rio]

Much appreciated Luke.  This will suit our needs perfectly for now :)