Hello everyone,
I would like to use KIM to semantically annotate content of a course with the topics of the domain ontology for that course (as you might have guessed, I'm doing my research in the learning domain). I read the instructions for extending the KIM platform and it seams clear to me what is to be done:-), however I am not sure how to extend the PROTON ontology.
I thought of defining classes of my domain ontology as subclasses of the protont:Topic class. However, I have doubts here. Should I model all my classes as direct subclasses of the Topic class and relate them in a hierarchy using protont:subTopicOf property, or should I model them in the hierarchy in the typical manner it is done in ontologies ( i.e. using rdfs:subClassOf). According to the PROTON documentation the first option seams to be preferable, but I'm concerned that this design decision might not be in accordance with KIM extraction modules, and that I might later have problems when using KIM IE functionality to extract entities from text.
In order to clarify my question i will give you an example for the above mentioned options:
1) Defining domain classes as direct subclasses of the Topic class and relating them in a hierarchy using protont:subTopicOf property
<owl:Class rdf:ID="eCommerce">
<rdfs:subClassOf rdf:resource=" http://proton.semanticweb.org/2005/04/protont#Topic"/>
</owl:Class>
<owl:Class rdf:ID="b2bActivities">
<rdfs:subClassOf>
<owl:Restriction>
<owl:onProperty rdf:resource="http://proton.semanticweb.org/2005/04/protont#subTopicOf"/>
<owl:allValuesFrom rdf:resource="#eCommerce"/>
</owl:Restriction>
</rdfs:subClassOf>
<rdfs:subClassOf rdf:resource=" http://proton.semanticweb.org/2005/04/protont#Topic"/>
</owl:Class>
2) Using rdfs:subClassOf property to create hierarchy of domain classes and just make a reference to protont:Topic via the top level domain class
<owl:Class rdf:ID="eCommerce">
<rdfs:subClassOf rdf:resource="http://proton.semanticweb.org/2005/04/protont#Topic "/>
</owl:Class>
<owl:Class rdf:ID="b2bActivities">
<rdfs:subClassOf rdf:resource="#eCommerce"/>
</owl:Class>
Initially my idea was to represent domain concepts as instances of the protont:Topic class. However, I realized that in that case KIM would not be able to recognize those concepts in the content of the course - KIM would recognize each of them as Topic not as something more specific. I'm I right, or I misinterpreted that part of KIM documentation?
Thanks in advance! And sorry for the confusion with my previous email:-)
Cheers,
I would like to use KIM to semantically annotate content of a course with the topics of the domain ontology for that course (as you might have guessed, I'm doing my research in the learning domain). I read the instructions for extending the KIM platform and it seams clear to me what is to be done:-), however I am not sure how to extend the PROTON ontology.
I thought of defining classes of my domain ontology as subclasses of the protont:Topic class. However, I have doubts here. Should I model all my classes as direct subclasses of the Topic class and relate them in a hierarchy using protont:subTopicOf property, or should I model them in the hierarchy in the typical manner it is done in ontologies ( i.e. using rdfs:subClassOf). According to the PROTON documentation the first option seams to be preferable, but I'm concerned that this design decision might not be in accordance with KIM extraction modules, and that I might later have problems when using KIM IE functionality to extract entities from text.
In order to clarify my question i will give you an example for the above mentioned options:
1) Defining domain classes as direct subclasses of the Topic class and relating them in a hierarchy using protont:subTopicOf property
<owl:Class rdf:ID="eCommerce">
<rdfs:subClassOf rdf:resource=" http://proton.semanticweb.org/2005/04/protont#Topic"/>
</owl:Class>
<owl:Class rdf:ID="b2bActivities">
<rdfs:subClassOf>
<owl:Restriction>
<owl:onProperty rdf:resource="http://proton.semanticweb.org/2005/04/protont#subTopicOf"/>
<owl:allValuesFrom rdf:resource="#eCommerce"/>
</owl:Restriction>
</rdfs:subClassOf>
<rdfs:subClassOf rdf:resource=" http://proton.semanticweb.org/2005/04/protont#Topic"/>
</owl:Class>
2) Using rdfs:subClassOf property to create hierarchy of domain classes and just make a reference to protont:Topic via the top level domain class
<owl:Class rdf:ID="eCommerce">
<rdfs:subClassOf rdf:resource="http://proton.semanticweb.org/2005/04/protont#Topic "/>
</owl:Class>
<owl:Class rdf:ID="b2bActivities">
<rdfs:subClassOf rdf:resource="#eCommerce"/>
</owl:Class>
Initially my idea was to represent domain concepts as instances of the protont:Topic class. However, I realized that in that case KIM would not be able to recognize those concepts in the content of the course - KIM would recognize each of them as Topic not as something more specific. I'm I right, or I misinterpreted that part of KIM documentation?
Thanks in advance! And sorry for the confusion with my previous email:-)
Cheers,
Jelena
_______________________________________________ NOTE: Please REPLY TO ALL to ensure that your reply reaches all members of this mailing list.
KIM-discussion mailing list [email protected] http://ontotext.com/mailman/listinfo/kim-discussion_ontotext.com
