Error_when_loading_MO_in_OSF

32 views
Skip to first unread message

Manfred

unread,
Nov 17, 2014, 3:46:27 PM11/17/14
to music-ontology-sp...@googlegroups.com

Hi,

there was an issue in loading the MO in OSF:
https://groups.google.com/forum/#!topic/open-semantic-framework/10-a7Jw2Ols

I worked with the files from these resources:
https://github.com/motools/musicontology/blob/master/rdf/musicontology.rdfs
https://github.com/motools/musicontology/blob/master/rdf/musicontology.n3

The reason is that some imported ontologies were not accessible.

After removing the concerned ontologies - MO was able to be imported in OSF.
The removed ontologies were imported separately in OSF.

Attached: the adjusted file

Thanks,

Manfred
musicontology.rdfs

Bo Ferri

unread,
Nov 19, 2014, 8:45:39 AM11/19/14
to music-ontology-sp...@googlegroups.com
Hi Manfred,

I'm not really sure, whether this is an issue of MO or of one of its
importing ontologies (especially AO and from AO the Similarity
Ontology), or whether this is an issue of the OSF importing mechanism.
I could successfully resolve both ontologies with curl:

1. Association Ontology

curl -H "Accept: text/turtle" http://purl.org/ontology/ao/core
=> delivers a 302 with http://smiy.sourceforge.net/ao/associationontology

curl -H "Accept: text/turtle"
http://smiy.sourceforge.net/ao/associationontology
=> delivers a 303 with
http://smiy.sourceforge.net/ao/rdf/associationontology.n3

curl -H "Accept: text/turtle"
http://smiy.sourceforge.net/ao/rdf/associationontology.n3
=> delivers a 200 with the ontology as text/turtle

2. Similarity Ontology

curl -H "Accept: application/rdf+xml" http://purl.org/ontology/similarity/
=> delivers a 303* with http://kakapo.dcs.qmul.ac.uk/ontology/musim/latest/

curl -H "Accept: application/rdf+xml"
http://kakapo.dcs.qmul.ac.uk/ontology/musim/latest/
=> delivers a 303 with
http://kakapo.dcs.qmul.ac.uk/ontology/musim/0.2/musim.owl

curl -H "Accept: application/rdf+xml"
http://kakapo.dcs.qmul.ac.uk/ontology/musim/0.2/musim.owl
=> delivers a 200 with the ontology as application/rdf+xml


So my result so far is that both ontologies are available as necessary.
Maybe Frederick can investigate this issue a bit more in detail on OSF side.

Cheers,


Bo/T


*) which should probably a 302 to be more precise, or?


On 11/17/2014 9:46 PM, Manfred wrote:
>
> Hi,
>
> there was an issue in loading the MO in OSF:
> https://groups.google.com/forum/#!topic/open-semantic-framework/10-a7Jw2Ols
>
> I worked with the files from these resources:
> https://github.com/motools/musicontology/blob/master/rdf/musicontology.rdfs
> <https://www.google.com/url?q=https%3A%2F%2Fgithub.com%2Fmotools%2Fmusicontology%2Fblob%2Fmaster%2Frdf%2Fmusicontology.rdfs&sa=D&sntz=1&usg=AFQjCNGvY-QBpuUEdjcAIiYg5NUoPKs_9Q>
> https://github.com/motools/musicontology/blob/master/rdf/musicontology.n3 <https://github.com/motools/musicontology/blob/master/rdf/musicontology.n3>
>
>
> The reason is that some imported ontologies were not accessible.
>
> After removing the concerned ontologies - MO was able to be imported in OSF.
> The removed ontologies were imported separately in OSF.
>
> Attached: the adjusted file
>
> Thanks,
>
> Manfred
>
> --
> You received this message because you are subscribed to the Google
> Groups "Music Ontology Specification Group" group.
> To unsubscribe from this group and stop receiving emails from it, send
> an email to
> music-ontology-specific...@googlegroups.com
> <mailto:music-ontology-specific...@googlegroups.com>.
> To post to this group, send email to
> music-ontology-sp...@googlegroups.com
> <mailto:music-ontology-sp...@googlegroups.com>.
> Visit this group at
> http://groups.google.com/group/music-ontology-specification-group.
> For more options, visit https://groups.google.com/d/optout.

Frederick Giasson

unread,
Nov 19, 2014, 8:52:46 AM11/19/14
to music-ontology-sp...@googlegroups.com
Hi Bo,

The problem appears to be with http://purl.org/ontology/similarity/

OSF is using the OWLAPI to load the ontologies, so these errors are
coming from the library. You can try using Protégé to have the OWLAPI
stacktrace. My guess is that the Accept header sent by the OWLAPI may
not be properly interpreted by the similarity's conneg system which
appears to lead to the HTML page of the ontology.

Thanks,

Fred

Bo Ferri

unread,
Nov 19, 2014, 9:35:20 AM11/19/14
to music-ontology-sp...@googlegroups.com
Hi Frederick,

thanks a lot for your fast reply. I tried to load the Similarity
Ontology with Protégé and got the bespoken error stacktrace. I think
that probably only Kurt can help here, since he administrated(/s (?))
the Similarity Ontology.
On the other side, I was able to successfully load the Similarity
Ontology into TopBraid Composer (which makes use of Jena (afaik)).
Furthermore, I could also successfully load the complete Music Ontology
into TopBraid Composer. Anyway, this doesn't solve Manfred issue at all ;)

Cheers,


Bo/T

Frederick Giasson

unread,
Nov 19, 2014, 1:08:39 PM11/19/14
to music-ontology-sp...@googlegroups.com
Hi Bo,


> thanks a lot for your fast reply. I tried to load the Similarity
> Ontology with Protégé and got the bespoken error stacktrace. I think
> that probably only Kurt can help here, since he administrated(/s (?))
> the Similarity Ontology.
> On the other side, I was able to successfully load the Similarity
> Ontology into TopBraid Composer (which makes use of Jena (afaik)).
> Furthermore, I could also successfully load the complete Music
> Ontology into TopBraid Composer. Anyway, this doesn't solve Manfred
> issue at all ;)

Yeah exact, in that case I would suspect that the Accept header of
TopBraid is different than Protégé's which would explain why it works on
one but not on the other one. In any case, the issue appears to be on
the conneg side of the ontology's server. So yes Kurt would have to look
into this :)

Thanks,

Fred
Reply all
Reply to author
Forward
0 new messages