[GitHub] incubator-rya issue #180: RYA-293 Added owl:unionOf inference
Github user jessehatfield commented on the issue: https://github.com/apache/incubator-rya/pull/180 So this is a case where a few different schema terms (rdfs:subClassOf, owl:unionOf, and eventually owl:equivalentClass) end up being represented by just one term internally (subclass/superclass relationships). We could plausibly organize by either; my intuition is to use the internal representation, since the internal graph being complete and accurate can matter to the other rules. That would mean pulling the logic introduced here, plus the logic introduced in [https://github.com/apache/incubator-rya/pull/184](PR 184) , plus the logic for rdfs:subClassOf (which 184 incidentally simplifies to a method call anyway) into some "refreshSubClassGraph" method. Thoughts on that approach? Would probably do the same with subPropertyOfGraph for consistency (though it's simpler because there's no equivalent to union). --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] incubator-rya issue #180: RYA-293 Added owl:unionOf inference
Github user asfgit commented on the issue: https://github.com/apache/incubator-rya/pull/180 Refer to this link for build results (access rights to CI server needed): https://builds.apache.org/job/incubator-rya-master-with-optionals-pull-requests/367/ --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] incubator-rya issue #180: RYA-293 Added owl:unionOf inference
Github user ejwhite922 commented on the issue: https://github.com/apache/incubator-rya/pull/180 Looks good. Rebasing with master and pushing should fix the build issue. --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] incubator-rya issue #180: RYA-293 Added owl:unionOf inference
Github user pujav65 commented on the issue: https://github.com/apache/incubator-rya/pull/180 hey @jessehatfield , it looks like there are test failures: https://builds.apache.org/job/incubator-rya-fork/24/ Can you verify that these are false failures? They do not look like they are related to your pull request. --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] incubator-rya issue #180: RYA-293 Added owl:unionOf inference
Github user pujav65 commented on the issue: https://github.com/apache/incubator-rya/pull/180 looks good -- kicking of a build to merge --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
