properties and classes as owl:namedIndividual

[pennyl67]

All classes and properties appear at the LexMeta documentation as named individuals (metashare.ilsp.gr/ontologies/lex-meta/lex-meta.v1.0.0.prelease/documentation/index-en.html#namedindividuals). This is not explicitly asserted in the ontology (at least I can't find it). Trying to figure out why this happens. One idea might be that this is due to the relation lexmeta:wikibaseEntity, which has no domain or range; could it be that wikibase entities are defined as named individuals, and this causes the same for the equivalent item in LexMeta? Any other ideas?

[gkirtzou]

Maybe it is inferred due to the way owl:ObjectProperty is declared in owl. I found this "OWL distinguishes between two main categories of properties that an ontology builder may want to define:

• Object properties link individuals to individuals.
• Datatype properties link individuals to data values " extract from here -> https://www.w3.org/TR/owl-ref/#Property

Maybe if we define domain and range in lexmeta:wikibaseEntity as owl:class and wiki entity (I am not sure how it is declared official), respectively, the problem might solve?

[dlindem]

In the TTL downloadable from the link in the documentation header, terms appear as named individuals, e.g. http://w3id.org/meta-share/lexmeta/idiom rdf:type owl:NamedIndividual .

In the TTL I produce, these rdf:type assertions are not present. I understand that entities are automatically provided with this rdf:type. The same happens, afaik, if one uploads an ontology to protégé; at least, I have seen appearing the same when doing that. It would be good to be able to set ontoology for not adding these, and list skos:Concept instances instead of owl:NamedIndividual instances in the documentation.

[gkirtzou]

It would be good to be able to set ontoology for not adding these,

The generated files (ttl, owl, html, etc) are generated from Widoco which runs as part of the Ontoology service. Unfortunately, the configuration of widoco is very limited, and I am sure that basic rdfs/owl inference is a default behavior in many tools. That's why also in protege considers all resources with the property lexmeta:wikibaseEntity as owl:namedIndividual.

and list skos:Concept instances instead of owl:NamedIndividual instances in the documentation.

each instance of a skos:Concept and in general each instance of a owl:Class is an owl:NamedIndividual. The documentation generated by widoco is a generic one, thus groups all instance of a class under owl:NamedIndividual. It cannot be configured to set the grouping under each class, since in the general case an instance could belong into multiple classes. If you notice it does mentions under which class in belongs to. So all the required information is provided