On 11.09.12 12:00, Andrea Giovanni Nuzzolese wrote:
Hi Andrea,
> you are right, the documentation is not exhaustive and not helpful at all.
> I am going to add more details.
Now I'm on the latest SVN version where the doc is better, unfortunately
I can't get a lot to work from the REST examples and I have some general
questions as well:
- /recipe does not work, there seems to be no handler for that (in terms
of I get a "not found"). Is this really supposed to be there?
- What exactly is the difference between recipes and rules? Is a recipe
a collection of rules?
- Am I right that a rule has to belong to a recipe and I have to post a
recipe before I can post a rule?
- From what I can read I always apply a refactor on a recipe and not on
a rule. But in the end of the documentation I find:
--
Request example which shows how to perform a refactoring applying an
existing recipe in the rule store:
$ curl -X POST -H "Content-Type: multipart/form-data" \
-H "Accept: application/turtle" \
-F recipe="
has(, ?x, ?z) . \
has(, ?z, ?y) \
-> \
has(, ?x, ?y)" \
-F input=@graph.rdf
http://localhost:8080/refactor/apply
--
and you write:
--
Parameters:
recipe (Mandatory). The recipe's identifier that is basically an URI
input-graph (Mandatory). The ID of the graph to transform
output-graph (Mandatory). The ID that the transformed graph has to have
in the IKS triple store
--
This does not fit at all IMHO. Either the variable is an ID or it is
data, in your example 'recipe' becomes data as well as 'input', which
you call 'input-graph' above and the "mandatory" field output-graph is
missing, which gives me all together total confusion.
Would be nice if you could explain that a bit more, I *really* want to
get it to work :)
cu
Adrian
