Hi Zoran, It appeared that the execution of the "createDocument" method does only a default retrieval of document features which is not very helpful.
For our demos we use an external tool which extracts additionally the other features of the document. In your case you shoud additionally open the web page and extract the title from it. Then you can put it as a feature together with the subject feature. Greetings, DanKo ----- Original Message ----- From: "Zoran Jeremic" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]>; <[email protected]> Sent: Tuesday, September 16, 2008 9:53 PM Subject: Re: [KIM-discussion] change recognized entity in content > Hi Danko, > > > >1) Create the KIM document through "CorporaAPI" method: > >KIMDocument createDocument(URL url, String encoding); > >providing the page URL. Execute: > >KIMDocument doc = > createDocument("http://my.web.pages/lecture_1.html","UTF-8"); > >2) Retrieve the text of the title of the resulting document like this: > >String doc_title = > doc.getFeatures().get(KIMDocument.DOCUMENT_FEATURE_TITLE) > > This sounds as a great idea that could be useful for my problem as well as > for some other thinks that I could use it for. However, I have the problem > on the second step. > Here is the code: > > KIMDocument kdoc = apiCorpora.createDocument(url, "UTF-8"); > String doc_title=(String) > kdoc.getFeatures().get(KIMDocument.DOCUMENT_FEATURE_TITLE); > System.out.println("doc title:"+doc_title); > > Iterator iterator=kdoc.getFeatures().keySet().iterator(); > while(iterator.hasNext()){ > Object key=iterator.next(); > System.out.println("feature:"+kdoc.getFeatures().get(key)); > } > > The result I get here for any page I try to annotate is something like > this: > doc title:null > feature:1221633671515 > feature:text/html > feature:http://en.wikipedia.org/wiki/Design_Patterns > > Did I miss something to do here? I have checked these pages they contains > <title> tag in head. > > > Zoran > > > ----- Original Message ----- > From: "DanKo" <[EMAIL PROTECTED]> > To: <[EMAIL PROTECTED]>, <[email protected]> > Date: Tue, 16 Sep 2008 13:38:49 +0300 > Subject: Re: [KIM-discussion] change recognized entity in content > >> Hi Zoran, >> >> Please send me a copy of your extention to the ontology and the >> knowledge-base with the instances you want to be recognised later >> >> Greetings, >> DanKo >> ----- Original Message ----- >> From: Zoran Jeremic >> To: [email protected] ; DanKo >> Sent: Thursday, September 11, 2008 8:24 PM >> Subject: Re: [KIM-discussion] change recognized entity in content >> >> >> Hi Danko, >> >> Thank you for your answer. >> >> > The one resource which case sensitivity could be manipulated is the >> > Gazeteer. >> > Use the parameter: >> > com.ontotext.kim.KIMConstants.ENTITY_CASE_TYPE=caseinsensitive >> > in file: >> > <KIM_HOME>\config\install.properties >> >> >> I have tried this, but in this case I don't get any annotation. Actually, >> I'm not sure what Gazeteer is. I remmember that I have read about it from >> your documents, but I can't find that document now, and I don't know if >> it concern my case. In my application I have extended proton's Topic >> class with several class from my domain ontology, and all I use to >> annotate the content are instances of these classes. >> >> Zoran >> >> --- On Wed, 9/10/08, DanKo <[EMAIL PROTECTED]> wrote: >> From: DanKo <[EMAIL PROTECTED]> >> Subject: Re: [KIM-discussion] change recognized entity in content >> To: [EMAIL PROTECTED], [email protected] >> Date: Wednesday, September 10, 2008, 4:17 AM >> >> Hi Zoran, >> >> This mail slipped my attention besides your other troubles :) >> >> Here are my comments on your questions: >> >> 1) The annotation process is multistaged and complex so the case >> sensitivity cant be manipulated as a whole. >> For example the JAPE rules largely rely on detection of Title case >> words for name recognition. >> The one resource which case sensitivity could be manipulated is the >> Gazeteer. >> Use the parameter: >> com.ontotext.kim.KIMConstants.ENTITY_CASE_TYPE=caseinsensitive >> in file: >> <KIM_HOME>\config\install.properties >> >> 2) To make your tag insertion the most easy way is to use the >> "KIMDocument" structure. >> You can put in it the text for annotation, then use the method: >> public KIMDocument execute(KIMDocument doc2) >> Then the returned document contains the plain text and the >> corresponding annotations in structured form ("KIMAnnotationSet") >> Then you will: >> - cycle through the annotations >> - pick the text offsets and types >> - form the replacement tagged fragment >> - replace the coresponding piece of the document body >> >> It is not a very detailed description, so if you find anything vague, >> please ask me back. >> >> Greetings! >> DanKo >> senior developer, KIM >> >> ----- Original Message ----- >> From: Zoran Jeremic >> To: [email protected] >> Sent: Saturday, September 06, 2008 6:13 PM >> Subject: [KIM-discussion] change recognized entity in content >> >> >> Hi, >> >> I have two questions about using KIM : >> >> 1) How can I set KIM annotation not to be case sensitive? >> >> 2) I want to annotate the content that is stored in the database and used >> as the web page content (i.e. discussion forum threads...), to recognize >> the entities, and change those recognized entities (i.e. Abstract >> factory) to the hiperlinks like: "<a title="View suggestions" >> href="/depths/services/online_resources/view_suggestions.php" >> onclick="this.target='message_3';return >> openpopup('/depths/services/online_resources/view_suggestions.php', >> 'message_3', >> 'menubar=0,location=0,scrollbars,status,resizable,width=800,height=600', >> 0);">Abstract factory</a>", and then to put this content back in the >> database. >> >> I know it is possible to get event from KIM that some entity is >> recognized and then using Java to process String and find that entity >> again and change it, but it would be better if I don't have to traverse >> the content twice. Do you have some idea how to use KIM for this? >> >> Thanks, >> Zoran >> >> _______________________________________________ >> 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 >> >> >> >> __________ NOD32 3421 (20080906) Information __________ >> >> This message was checked by NOD32 antivirus system. >> http://www.eset.com >> >> > > > > > > __________ NOD32 3444 (20080916) Information __________ > > This message was checked by NOD32 antivirus system. > http://www.eset.com > > _______________________________________________ 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
