OK, I see.
To prevent using a "process" as a range of "occurs_in", this should
probably work, but what if somebody use "occurs_in" with some new
class, for which you do not have similar disjointness axioms?
I think a safer solution would be to check externally if, e.g., all
fillers of property restrictions with this property are indeed
sub-classes of the range.
I recall, in Galen ontology there was a similar mechanism using
"sanctions", which basically say that a property can only be used with
some particular classes as domains and ranges (e.g., "part-of" can be
either a relation between anatomical structures, or between, say
ingredients and drugs). Then a classifier was used to check if each
"part-of" was used for one of these valid situations. E.g., if there
was an axiom A part-of B then it was checked whether both A and B are
subclasses of anatomical organs, or wether A is a subclass of
ingredients and B is a subclass of drug, etc. If neither of these was
the case, the editor would return an error.
The settings can be remembered between the sessions, no problems. ELK
does that already for remembering the number of workers and
incremental reasoning option (specifically in the file
~/.Protege/org.semanticweb.elk/elk.properties). So we could, in
principle, add there an option to disable all warning messages in
Protege -- but this would solve only half of the problem, one has to
do something about non-supported OWL API methods which Protege calls
and gets runtime exceptions.
But we are also concerned that disabling warnings permanently could
cause some misunderstanding, where the users could expect some results
which are not produced by ELK (the users could easily forget that they
disabled all warnings long time ago). We could try to add this as a
"hidden" configuration option (set in the file but not in the menu),
and see if that works well for you.
>
> I suppose it wouldn't be hard for us to build a special purpose jar that
> hides these warnings, we would use this jar in our projects, knowing full
> well that answers may be incomplete.
>
> Sounds like it's not worth you worrying about though.
>
>>
>> > 3. support for reasoner.getObjectPropertyValues
>> >
>> > I'm tempted to write a reasoner that wraps elk to support these,
>> > possibly in
>> > a kludgy incomplete way. But I wouldn't bother doing this if support for
>> > this was planned in the near future.
>>
>> We did not add any property reasoning methods so far (so even
>> computing object property hierarchy and checking consistency of object
>> properties is not supported yet). Once we have a proper infrastructure
>> for this in place (classification of object properties), we can look
>> into more advanced reasoning tasks, such as computation of property
>> values and property ranges.
>
>
> OK, great
>
>>
>> Before that, please create tickets for your feature requests here:
>>
>>
https://code.google.com/p/elk-reasoner/issues/list
>>
>> This way, we can track various user requests and prioritize them
>> accordingly.
>
>
> I will do, thanks.
Thanks, we look forward for your tickets!
Yevgeny
>
>>
>> Best regards,
>>
>> Yevgeny
>
>
>
> --
> You received this message because you are subscribed to the Google Groups
> "elk-reasoner-discussion" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to
elk-reasoner-disc...@googlegroups.com.
> For more options, visit
https://groups.google.com/groups/opt_out.