new issue for latest SKOS

[Jean-Marc Vanel]

Hi

Apparently this was unnoticed :
http://code.google.com/p/skoseditor/issues/detail?id=11&thanks=11&ts=1321088843

Same problem with Protégé 4.1, but works with Protégé 4.0.2 .

[Simon Jupp]

It seems the underlying OWL API is interpreting the object property
assertions in your file as annotation property assertions.
I'm waiting to hear back from the API developers to try and understand
what changed in the RDF parser.

Aside from this issue, the SKOS editor view shouldn't cark it like it
does when loading your file. I will investigate further...

Cheers
Simon

On Nov 16, 11:23 am, Jean-Marc Vanel <jeanmarc.va...@gmail.com> wrote:
> Hi
>

> Apparently this was unnoticed :http://code.google.com/p/skoseditor/issues/detail?id=11&thanks=11&ts=...

[Simon Jupp]

Hi,

It seems the OWL API used to recognise SKOS properties and handle them
properly, but this feature has now gone. I will fight to get it put
back in.

In the meantime if you want to view/edit your Matiere vocabulary in
SKOSEd 2.0 / Protege 4.1 you need to explicitly declare your
properties. Or, alternatively import the SKOS core ontology from
http://www.w3.org/2004/02/skos/core.

In your RDF/XML, just replace the header of your file with this:

<rdf:RDF xmlns:owl="http://www.w3.org/2002/07/owl#"
xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
xmlns:dc="http://purl.org/dc/elements/1.1/"
xmlns:foaf="http://xmlns.com/foaf/0.1/" xml\
ns:dct="http://purl.org/dc/terms/"
xmlns:skos="http://www.w3.org/2004/02/skos/core#"
xmlns:rdfs="http://www.w3.org/2000/01/rdf-schema#">
<owl:Ontology rdf:about="http://www.archivesdefrance.culture.gouv.fr/thesaurus/resource/Matiere.owl">
<owl:imports rdf:resource="http://www.w3.org/2004/02/skos/core"/>
</owl:Ontology>

I tested it and it now loads and displays correctly in SKOSEd 2.0/Protege 4.1

Hope that helps.
Simon

> --
> You received this message because you are subscribed to the Google Groups "skos-dev" group.
> To post to this group, send email to skos...@googlegroups.com.
> To unsubscribe from this group, send email to skos-dev+u...@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/skos-dev?hl=en.
>
>

[Jean-Marc Vanel]

Indeed , it helps !

After clicking on the pull down menu SKOSED / import SKOS-DL ontology it works in Protégé 4.2.0 build 249 ( and probably 4.1 ) .

But shouldn't the plugin do automatically this import anyway ?

The individuals in SKOS document , are they really valid from an OWL point of view without the ontology being defined ?

2011/11/16 Simon Jupp <simon...@gmail.com>

--
Jean-Marc Vanel
Déductions SARL - Consulting, services, training,
Rule-based programming, Semantic Web
http://jmvanel.free.fr/ - EulerGUI, a turntable GUI for Semantic Web + rules, XML, UML, eCore, Java bytecode
+33 (0)6 89 16 29 52
chat :  irc://irc.freenode.net#eulergui

[Simon Jupp]

> But shouldn't the plugin do automatically this import anyway ?

I think it should be optional if you want to import the full SKOS
ontology, hence the menu item.

> The individuals in SKOS document , are they really valid from an OWL point
> of view without the ontology being defined ?

There is nothing in your document that states the resource types, so
from an OWL point of view, you don't really know what the OWL types
are. When the OWL API parses the RDF it looks at how the resources are
being used, and then interprets the OWL types from that.

By importing the SKOS ontology, where the type definitions are
explicit, your SKOS file gets interpreted correctly. This avoids
having some code in the OWL API to treat SKOS as some special case
(which is what I think the developers were trying to avoid). I think
it's good practice to either import the core SKOS ontology or define
your resources explicitly in your file. Especially if you want OWL
based applications to play nicely with your SKOS. Of course, if you
don't care about the OWL nature of SKOS, you can ignore all of this,
but you do so at a cost.

Cheers
Simon

On Wed, Nov 16, 2011 at 6:30 PM, Jean-Marc Vanel
<jeanmar...@gmail.com> wrote:
> Indeed , it helps !
> After clicking on the pull down menu SKOSED / import SKOS-DL ontology it
> works in Protégé 4.2.0 build 249 ( and probably 4.1 ) .
>

> The individuals in SKOS document , are they really valid from an OWL point

[Jean-Marc Vanel]

Thanks Simon , it's clear and I agree; note that it's not *my* document at all, it's just a representative example, and I don't even intend to use it in a real project .

2011/11/16 Simon Jupp <simon...@gmail.com>

> But shouldn't the plugin do automatically this import anyway ?

I think it should be optional if you want to import the full SKOS
ontology, hence the menu item.

OK. But the  menu item maybe should be  "import SKOS full" , and if not checked by user, automatically apply this default : import SKOS - DL ?