Closed martinnec closed 4 years ago
This issue is related to #86, so I will proceed the same way (ask about Termit behaviour, then report back).
This is because ufo/object-type is not loaded in ontoGrapher's default configuration, and therefore it is not recognized (the object-type used is from Z-SGoV, I believe). As for the subclassing issue, the relation that Termit uses is skos:broader, whereas the relation that ontoGrapher uses is rdfs:subClassOf as per #54.
We have had discussions previously on the proper behaviour in a situation where an unrecognized term is referenced (mainly whether to ignore it or show it in a read-only state, for example), so this is something we are definitely thinking of, but haven't yet decided. I'll discuss with others whether inclusion of skos:broader relationships makes sense (In my opinion, it does) and if so, how should it be done. If we decide on anything concrete, I will make sure to issue relevant enhancement tickets.
TermIt is updated to contain correct prototypes, so this is fixed.
As for the subclassing issue: I don't think we should support skos:broader as a rdfs:subClassOf in ontographer:
I checked the behaviour and its seems fixed.
Closing, fixed.
I created a new term in Termit:
I openned the workspace in Ontographer and I cannot see its prototype (shall be object type) and its connection to its broader type (člověk)
On this screenshot, you can see the emty list of stereotypes (I expected the object type here)
And here the empty list of connections (I would expect specialization of člověk here)