nimble-platform / common

Common modules that can be accessed by the other NIMBLE services.
Apache License 2.0
2 stars 4 forks source link

Common label for concepts of the ontology (domain specific and eclass) #10

Open marcofranke opened 6 years ago

marcofranke commented 6 years ago

Currently, we have domain specific concepts and eclass based concepts. Both kinds of concepts use different labeling mechanism in Marmotta to describe the label of the concept. The index/core concepts have to be a harmonized at least in the index/core Concepts. Otherwise, the user cannot find any concept.

marcofranke commented 6 years ago

Dear all, I discussed with Felix today that an ontology concept and an eclass have a translation label. In both cases, it should be named the same within the index. That means, in both scenarios the translation is located below the same translation labels (same index/core fields).

If a concept has no translation for a specific chosen language, we will use the translation label for English. That means, for each concept in NIMBLE at least a label for the English language have to be available.

iot365 commented 6 years ago

Here are two examples concepts from from the Furniture Ontology and from eClass to show the differences:

<rdf:Description rdf:about="http://www.aidimme.es/FurnitureSectorOntology.owl#Leather">
    <rdf:type rdf:resource="http://www.w3.org/2002/07/owl#Class"/>
    <rdfs:subClassOf rdf:resource="http://www.aidimme.es/FurnitureSectorOntology.owl#Upholstery"/>
    <FurnitureSectorOntology1:translation xml:lang="es">Cuero</FurnitureSectorOntology1:translation>
    <owl:disjointWith rdf:resource="http://www.aidimme.es/FurnitureSectorOntology.owl#Polyskin"/>
</rdf:Description>

Harmonisation can be done by keyword search. To my understanding, a "true" mapping between the related conecpts cannot automatically be derived.