Skip to content
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

Open
jimkont opened this issue Feb 16, 2015 · 3 comments
Open

Declare disjointedness #2

jimkont opened this issue Feb 16, 2015 · 3 comments

Comments

@jimkont
Copy link
Member

jimkont commented Feb 16, 2015

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

@pfps
Copy link

pfps commented Mar 3, 2015

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.

@jimkont
Copy link
Member Author

jimkont commented Mar 5, 2015

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.
For now we could limit this to top-level classes where the class definitions are usually more obvious

@pfps
Copy link

pfps commented Mar 5, 2015

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Disjointness between the top-level concepts is also tricky as there are
several whose definition is rather inscrutable.

peter

On 03/05/2015 06:29 AM, Dimitris Kontokostas wrote:

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. For now we could limit this to top-level classes where
the class definitions are usually more obvious

— Reply to this email directly or view it on GitHub
#2 (comment).

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQEcBAEBAgAGBQJU+IIVAAoJECjN6+QThfjzTFsIANMEUf/4y4g6e8aCcfo2bI1G
8ZKpgdC+4b1FSi1KWifJz18ZENUJ8EIEQzVQNYBPijGjyJIRgYsum63eHl271ZW1
E9/Y6Skf2OzwbQcEeEwEL4EyxmmZEZZH8qxWQWW62C+arb05Mh0+HjKJp06yh637
f4uQR6F4rR37YcQ0jU7rn8ohbWPGwSNu3NZ/SOmy++WXQoo/YGm1Qh0LTygzKPmH
WaQmo7615Era0M4UrP9EohycNJxDy5zI8qMJ2K9jtTOyqUQTE4DbSeb1c4+YHNSx
dOATY7yzM+cTxUINHGFzmxLJuJIiizL6Csa2UpXKvmqBAQCylRJuL9id+h6qHwI=
=hd8q
-----END PGP SIGNATURE-----

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants