Sorry for the delay, I'm not feeling very well.
On 9/25/12 7:33 PM, Adrian Gschwend wrote:
Either that or I was lucky with the resources I tried :-D Are you sure
that REST doesn't allow you to set the ID on your own
I have the code before me right now, and can't see any PUT or POST
methods for *subresources* of /ontonet, /ontonet/session or
/ontonet/ontology. But given your valuable input, I guess it's time to
add some.
It seems however that you would like to specify a public key
manually. To my knowledge this wasn't possible earlier, but since I
have now implemented aliasing, I guess it is not a problem to have
the client specify new aliases. We can figure out together the best
way to do so, though.
That would be great, otherwise the caching stuff I do won't really work
Ok I'll look into it shortly and open a ticket for it. Shouldn't be very
hard since aliasing was implemented recently.
You propose that or they should work? I think PUT/POST is more correct
then if it's about choosing the right way.
They need to be implemented, but come to think of it, perhaps it could
be useful to implement both services together.
Best,
Alessandro
--
M.Sc. Alessandro Adamou
Alma Mater Studiorum - Università di Bologna
Department of Computer Science
Mura Anteo Zamboni 7, 40127 Bologna - Italy
Semantic Technology Laboratory (STLab)
Institute for Cognitive Science and Technology (ISTC)
National Research Council (CNR)
Via Nomentana 56, 00161 Rome - Italy
"I will give you everything, just don't demand anything."
(Ettore Petrolini, 1917)
Not sent from my iSnobTechDevice
