Hello,

I've seen several messages posted to the list stating that a newer 
version (1.6.7.18) is available for download from 
http://ontodemo.sirma.bg/KIM/download.  However, I get a 404 error 
(resource not found) when I try that URL.  Is there another location 
to download the latest version?  The URL I was given in my 
registration email still points to the 1.5.11.4 version. The new 
version might address some of the problems I've encountered.

INSTALLATION

I downloaded the Macintosh installer and tried installing KIM on a 
new Intel iMac, however I ran into problems when it came time to 
select the installation directory.  If I left the default directory 
selected (/usr/local/bin/../kim-platform) I would receive a message 
that I didn't have permission to create the selected directory, even 
though I was running the installer as root.  If I clicked the 
"Choose" button to change the installation directory the installer 
would hang.  When I checked the error log it said (something to the 
effect) that an IllegalArgumentException had been thrown because of 
an unknown file dialog type.  I apologize as I thought I had made a 
copy of the log file to include, but the error message was 
overwritten when later I successfully installed KIM.

To circumvent the problem I manually created the directory 
/usr/local/kim-platform, made myself the owner with rwx permissions, 
re-ran the installer (as root), and the installation proceeded 
without problem from then on.  Of course, part of my problem might be 
that I've been a Mac user for 3 days now and know just enough about 
UNIX to be dangerous...

MY PROGRESS SO FAR

I've been able to extend the OWL ontologies to add my own classes, 
properties etc. and I have written an N-TRIPLE file containing 
definitions for instances of the classes.  I can browse the ontology 
in the WebUI and annotate our texts with the Populate and Store 
program (more about that below).  I'm still having problems selecting 
entities, but that's likely because the ontologies and KB still need 
tweaking.  I've also been able to use the KIM GATE UI to create a 
Corpus Pipeline to annotate our documents with the KIM Client and 
also use the KIM Gazetteer to annotate files and see what Lookup 
annotations the JAPE rules will have available.  KIM is using our 
classes and instances so it looks good so far.

I did have one problem with the Populate and Store tool.  If I 
selected a Serial Datastore and tried to annotate our files I would 
get a "Check Failed" (FileNotFoundException) error because the 
directory "/local/kim-platform/index-and-store" could not be 
found.  For some reason the /usr is being stripped off the 
filename.  I tried creating a symbolic link from /local to 
/usr/local, and while the check succeeded the tool would hang when it 
tried to save a document.  Using a Lucene datastore worked fine.

EXTENDING/RESTRICTING THE WKB

Our domain is the time period leading up to, and including, World War 
II.  Therefore quite a bit of the "knowledge" in the wkb.nt file is 
incorrect.  However, I don't want to toss out the whole thing as alot 
of the information is correct and (I assume) alot of the JAPE rules 
depend on information it provides.  What is the best way to go about 
editing this file?  What tools do the folks at OntoText use?

GATE

Is it correct to assume that running the KIM Client in GATE performs 
much the same task as running the Populate and Store tool?  Since I 
am quite familiar with GATE I am thinking that it would be easiest to 
work on and test the JAPE rules using GATE.

Finally, is there any problem using the latest version of GATE (3.1) 
with KIM?  That is, can I simply replace the gate.jar file that KIM 
is using with the latest version?  And can I use the KIM plugins with GATE 3.1?

Thanks in advance
Keith


_______________________________________________
NOTE: Please REPLY TO ALL to ensure that your reply reaches all members of this 
mailing list.

KIM-discussion mailing list
[email protected]
http://ontotext.com/mailman/listinfo/kim-discussion_ontotext.com

Reply via email to