-
Notifications
You must be signed in to change notification settings - Fork 11
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Declare disjointedness #2
Comments
A problem with providing disjointness axioms is that many of the DBpedia classes are in unusual places in the taxonomy or are not very well defined. For example, one might expect that Canal and Stream should be disjoint but Canal is a subclass of Stream. Classes like Swarm have no effective definition making it very difficult to determine what they should be disjoint from. |
You are right, I agree. I'll make a separate issue for improving the class/properties documentation but there is not time to tackle this for the next release. |
-----BEGIN PGP SIGNED MESSAGE----- Disjointness between the top-level concepts is also tricky as there are peter On 03/05/2015 06:29 AM, Dimitris Kontokostas wrote:
iQEcBAEBAgAGBQJU+IIVAAoJECjN6+QThfjzTFsIANMEUf/4y4g6e8aCcfo2bI1G |
The idea here is to define all the disjoint classes the DBpedia ontology. This will information be used for better validation.
Disjoint properties can be defined as well but the wiki does not support that yet, maybe when we move to WebProtege
The text was updated successfully, but these errors were encountered: