MO nip and tuck

[zazi]

Hi folks,

I've experimented a little bit around with 2 ontology modelling tools
(TopBraid Composer and Protégé). To get the current N3 version of MO to
work (load) with both tools, I had to do some small changes in the
ontology. They dealt mainly about handling the imports and setting the
base uri, but also in fixing a small bug related quotation marks of the
comments. I also removed the redundant (?) owl:Ontology definitions,
because only mo: should in this a owl:Ontology. What about the other
stuff from "bio:event" until "vs:term_status" (exclude that last
definition).
Here [1][2] is the result in N3 and RDF/XML notation (the second one is
automatically generated from TopBraid and not really nice, because of
the auto-generated node ids). TopBraid can handle both files without
problems. With Protégé 4.0 I just get the RDF/XML to work and you must
have some of the imported ontologies locally available to fix missing
imports (unfortunately, the are not fully loaded every time). Of course,
Protégé is now a little bit nice ;) - especially the DL metrics view,
but in the aspect of visualisation TopBraid is my favourite. It is fast
and adaptable. Unfortunately, it cost money.
Maybe we can also commit the N3 file to the SVN.

Cheers zazi

[1] http://www1.inf.tu-dresden.de/~s9736463/mo/mo.n3
[2] http://www1.inf.tu-dresden.de/~s9736463/mo/mo.owl

[Yves Raimond]

Hello!

On Sat, Jul 18, 2009 at 11:32 PM, zazi<za...@elbklang.net> wrote:
>
> Hi folks,
>
> I've experimented a little bit around with 2 ontology modelling tools
> (TopBraid Composer and Protégé). To get the current N3 version of MO to
> work (load) with both tools, I had to do some small changes in the
> ontology. They dealt mainly about handling the imports and setting the
> base uri, but also in fixing a small bug related quotation marks of the
> comments. I also removed the redundant (?) owl:Ontology definitions,
> because only mo: should in this a owl:Ontology. What about the other
> stuff from "bio:event" until "vs:term_status" (exclude that last
> definition).

Really? I changed some things in MO last year to make it work with
Protege, but I thought it was fine now? Apart from some issues with
imported ontologies not loading into Protege for some reason, which
can be bypassed by pointing Protege to a dir where all ontologies sit,
it seems to work ok. vs:term_status is an annotation property and
should be handled fine. What is the problem with bio:event?

I never tried it with TopBraid though - thanks a lot for making it
work! Do you have an account on the motools sourceforge project? If
so, I think it would make sense to have that version committed there.
We can work on merging the changes in the main RDF file then. Do you
have a list of the changes you had to make?

Cheers,
y