On 25.09.12 18:04, Alessandro Adamou wrote: Hi Alessandro,
> You could do that earlier? Hmmmmm, that's odd, it should have never > been that way - not very RESTful. 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? > To be named, an ontology needs to have a single named resource typed > with owl:Ontology . DC elements is in RDFS and has no OWL > statements. Resource "http://purl.org/dc/elements/1.1/"; is not even > typed in the schema. ok as mentioned in the proposal I'm using Stanbol as a cache for ontologies as well. Our framework now first checks if it finds the ontology in Stanbol, if not it fetches it and posts it there as well. So I do need the URI of the prefix as an identifier, otherwise I cannot look it up properly. > You see all those annotation properties because there is no statement > in the ontology that claims them to be something more powerful, such > as object properties. That's normal for OWL axiom interpretation > praxis (and a known cause of problems e.g. for OWL reasoners - but > we're working on that). ok tnx for the clarification! Was confused because I remembered the turtle I posted. > 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 > Some ways to do so could be: You propose that or they should work? I think PUT/POST is more correct then if it's about choosing the right way. > What you saw was not for deleting ontologies, yet. An HTTP DELETE on > an ontology within a scope or session will simply release the handle > from that scope/session on the ontology - hopefully making it > deletable if there are no other handles. ah ok > The actual deletion of ontologies was implemented in the commit I did > a few minutes ago. You may want to update and rebuild the > ontologymanager and try it out. ok cool tnx cu Adrian
