Hi,
The question is not stupid at all. The javadoc for
SemanticRepositoryAPI. isSubClassOf(..) is neither clear nor informative.
SemanticRepositoryAPI. isSubClassOf(..) accepts String parameters,
unlike TaxonomyAPI.isSubClass(..) which requires the more type-safe
Sesame Resource interface. Using isSubClassOf(..) with string is
particularly useful in the Java right-hand side of JAPE rules.
There the lack of import statements makes creating URIImpl instances
from string annotation features very cumbersome and thus using
TaxonomyAPI.isSubClass(..) gets very prone to technical errors.
Use SemanticRepositoryAPI. isSubClassOf(..) in JAPEs . Use
TaxonomyAPI.isSubClass(..) in regular Java code.
Hope this help,
Marin Nozhchev
(surname required for name disambiguation :)
On 06.10.2009 ?. 14:17, Milena Yankova-Doseva wrote:
Hi,
My question may be stupid but what's the difference between
- SemanticRepositoryAPI
<http://nmwiki.semanticannotation.com/kim-javadoc/com/ontotext/kim/client/semanticrepository/SemanticRepositoryAPI.html>.
isSubClassOf(..) and
- TaxonomyAPI
<http://nmwiki.semanticannotation.com/kim-javadoc/com/ontotext/kim/client/semanticrepository/TaxonomyAPI.html>.isSubClass(..)
And which one should I use?
Thanks
Milena
_______________________________________________
Kim-discussion mailing list
Kim-discussion@ontotext.com
http://ontotext.com/mailman/listinfo/kim-discussion
_______________________________________________
Kim-discussion mailing list
Kim-discussion@ontotext.com
http://ontotext.com/mailman/listinfo/kim-discussion
