Direct registration of ontology

[mmisw]

From caru...@gmail.com on November 09, 2009 10:22:53

What capability do you want added or improved? Direct mechanism (as opposed to the portal interface) to register an ontology so a client can simply specify the desired ontology (ideally containing the recommended metadata--see below) and a few required fields including username and password. Where do you want this capability to be accessible? In the main ORR service. What sort of input/command mechanism do you want? A simple HTTP POST call where I specify the ontology file, username/password and other relevant information (to be determined). What is the desired output (content, format, location)? A textual response (perhaps in XML) indicating the result of the operation: i) success, confirming the registered ontology URI; ii) error, including the reason of the error. Other details of your desired capability? 0) The ontology is to registered in "re-hosted" mode. (We can later add the ability to register in "fully hosted" mode.)

1) An HTML form should be included to illustrate the required information (and demonstrate the functionality).

2) A programmatic example (in java) showing how to use the service.

3) The submitted ontology should include metadata as recommended by MMI. Initially, this can be relaxed while testing is performed. For now, the submitted ontology can include the following prefixes:

xmlns:omvmmi=" http://mmisw.org/ont/mmi/20081020/ontologyMetadata/ "
xmlns:omv=" http://omv.ontoware.org/2005/05/ontology# "

and define the following properties associated with the ontology resource:

    \<omv:name> THE TITLE OF THE ONTOLOGY \</omv:name>

    \<omv:acronym> A SHORT NAME BY WHICH THE ONTOLOGY IS KNOWN

</omv:acronym>

    \<omv:hasCreator> AUTHOR/CREATOR OF THE ONTOLOGY CONTENTS

</omv:hasCreator>

    \<omv:description> DESCRIPTION OF THE ONTOLOGY \</omv:description>

Original issue: http://code.google.com/p/mmisw/issues/detail?id=214

[mmisw]

From caru...@gmail.com on November 09, 2009 17:54:48

Basic mechanism implemented. MMI Portal 1.6.2.alpha (20091109174222)

The HTML form in the MMI ORR deployment is located at: http://mmisw.org/orr/direg.html The fields in the POST request must indicate:

• username/password: MMI ORR user submitting the ontology
• ontologyUri: URI associated with the submitted ontology
• file: the selected file in the local system

Note: 1) the client should indicate the ontology URI (ie., this is not obtained automatically from the contents of the ontology) 2) if the ontology URI is already registered, then the submitting user must be the same.

Tested with the attached file. The response from the 'direg' servlet is:

http://example.com/direg_test New ontology registered

Then, submitted again to test registration of new version. The response is:

http://example.com/direg_test New version of ontology registered

See: http://mmisw.org/orr/#http://example.com/direg_test and click the "versions" button.

NEXT: 1- more testing 2- the programmatic example code in java.

Attachment: test1.owl

[mmisw]

From ber...@gmail.com on November 10, 2009 03:22:39

I'm trying to register an inference graph - which can contain several ontologies, so there is no real base URI. I created a namespace ""= http://mmisw.org/ont/ooi-ci/all# with a distinct identifier.

So I am getting the error:

Error creating ontology for registration: The new base URI ( http://mmisw.org/ont/ooi-ci/cdm-instance-ml ) is not equal to the registered base URI ( http://mmisw.org/ont/ooi-ci/all )

Attachment: inf-all-ooi.rdf

[mmisw]

From caru...@gmail.com on November 10, 2009 15:59:20

I did changes to accept any (valid) RDF file and prepare to indicate desired model graph in the back-end.

Please note:

1) the Ontology URI field is required as the identification of the registered entry. No information (base URI or any other) is extracted from the contents of the file. The URI given in the form is what will be used as ID.

2) The form now includes a graphId parameter. This is intended to identify a particular model graph in the MMI repository. It has two options: "ooici" and "main". At time of writing, this is NOT yet fully implemented in the back-end (that is, the RDF contents always go to the main ORR graph) but I will work on that later.

I tested these changes with the inf-all-ooi.rdf file and the following parameters in the form:

Ontology URI: http://mmisw.org/ont/ooi-ci/all-TEST graphId: ooici

Note, I added -TEST for the URI in this test because I will be removing that entry shortly. Please do your test with the desired URI ( http://mmisw.org/ont/ooi-ci/all ).

The response to the test was:

http://mmisw.org/ont/ooi-ci/all-TEST ooici New ontology registered

[mmisw]

From caru...@gmail.com on November 10, 2009 16:25:20

Just some test queries below.

(Note: I'm noting an issue with the update of the graph upon registration. After re-loading the graph the following queries were processed OK.)

SELECT ?p ?o WHERE { < http://motherlode.ucar.edu:8080/thredds/fileServer/station/metar/Surface_METAR_20091106_0000.nc > ?p ?o }

PREFIX rdfs: < http://www.w3.org/2000/01/rdf-schema# > SELECT ?s
WHERE {?s rdfs:isDefinedBy < http://xmlns.com/foaf/0.1/ >. }

PREFIX rdf: < http://www.w3.org/1999/02/22-rdf-syntax-ns# > PREFIX rdfs: < http://www.w3.org/2000/01/rdf-schema# > SELECT ?comment WHERE { http://www.w3.org/2003/01/geo/wgs84_pos# "> rdfs:comment ?comment }

[mmisw]

From caru...@gmail.com on November 10, 2009 22:04:42

I created issue #218 for the problem of not proper update of the graph upon registration, indicated in my previous comment.

[mmisw]

From caru...@gmail.com on November 24, 2009 22:54:40

Except for the actual processing of the graphId parameter (see new issue #225 ), this is implemented now. The demo program is available at: https://code.google.com/p/mmisw/source/browse/#svn/trunk/mmiorr-client-demo

Status: Fixed