Sorry for the late response. On 11/12/12 5:32 PM, adasal wrote:
I expect so. With a means to inspect a count of aliases so that admin may override and remove the referenced ontology.
well I've also added the boolean "meta" query parameter for the ontology resource too, so you can get the aliases as owl:sameAs statements in RDF/XML, Turtle or JSON-LD.
I also think a single RESTful service for removing all the aliases altogether (effectively deleting the graph) is probably a little too much, but a sequence of DELETE calls on the above sameAs subjects/objects would work.
Does admin have the ability to version ontologies, is that a use case in Stanbol? If so there are other issues here of admin to consumer responsibility.
There is some version management in terms of OWL 2, i.e. by expressing it as owl:versionIRI statements. The general policy is that if you submit an ontology that is already versioned, then the versionIRI stays untouched, otherwise upon export it is set to be the requestURI of the ontology resource (as per the OWL 2 version specification).
How are they dealt with in other ontology versioning environments?
I honestly only dealt with the intrinsic versioning mechanism in OWL 2, and frankly I would want to see it adopted for "external" versioning (i.e. of published ontologies), see http://www.w3.org/TR/2009/REC-owl2-syntax-20091027/#Ontology_Documents
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
