[Pellet-users] cardonality restrictions produce erroneous taxonomy

[Christina Tziviskou]

hi,

I'm using Pellet API for reasoning upon a Knowledge Base.

I want to include cardinality properties restriction,
so I'm using *all* the following for a property:

kb.addEquivalentClass(domainClass,
ATermUtils.makeSomeValues(newProperty, rangeClass));
kb.addEquivalentClass(domainClass, ATermUtils.makeMin(newProperty,
(ATermInt) ATermUtils.term(minCardinality), rangeClass));
kb.addEquivalentClass(domainClass, ATermUtils.makeMax(newProperty,
(ATermInt) ATermUtils.term(maxCardinality), rangeClass));

The results is that Pellet does not produce the right taxonomy for the
classes in the KB.
Instead, If I use only one of the above (it does not matter which one),
the taxonomy is correct.
Even If I use only the second and third invocations without the first
one, I keep taking a wrong taxonomy.

I would appreciate any help.
Thank you,
christina