{"id":2366,"date":"2021-03-28T15:32:07","date_gmt":"2021-03-28T10:02:07","guid":{"rendered":"https:\/\/www.rangakrish.com\/?p=2366"},"modified":"2021-03-28T15:32:07","modified_gmt":"2021-03-28T10:02:07","slug":"implementing-ilexicon-using-litedb","status":"publish","type":"post","link":"https:\/\/www.rangakrish.com\/index.php\/2021\/03\/28\/implementing-ilexicon-using-litedb\/","title":{"rendered":"Implementing iLexicon using LiteDB"},"content":{"rendered":"

iLexicon<\/strong><\/em> is an “intelligent”<\/strong><\/em> dictionary that can be used to build Natural Language<\/strong><\/em> applications. I have two implementations, one in Lisp<\/strong><\/em> and another in Prolog<\/strong><\/em>. Both implementations are memory-based, in order to speed up performance. I have written several articles referencing it, for example see this<\/strong><\/em><\/a>. \u00a0<\/span><\/p>\n

LiteDB<\/strong><\/em> is a NoSQL<\/strong><\/em> database for .NET<\/strong><\/em>. I wrote<\/strong><\/em><\/a>\u00a0about it a few weeks ago. Since that time, I have been working on implementing ILexicon<\/strong><\/em> using LiteDB<\/strong><\/em> as the back-end. That is almost complete. The primary reason for moving iLexicon<\/strong><\/em> to LiteDB<\/strong><\/em> is that I can now access the lexicon from both Lisp<\/strong><\/em> and Prolog<\/strong><\/em> through the respective COM\/Automation<\/strong><\/em> modules.<\/p>\n

In today’s article, I will show the primary COM Server<\/strong><\/em> interface and how it is used from Sicstus<\/strong><\/em>\u00a0Prolog<\/strong><\/em><\/a>. i<\/strong>Lexicon<\/strong><\/em> is quite feature-rich and it is difficult to demonstrate its capabilities in a single article. You may want to see my other posts related to this.<\/p>\n

Here is the COM Server<\/strong><\/em> layer, written in C#<\/strong><\/em>.<\/p>\n

\"COM<\/a>
COM Server<\/strong><\/figcaption><\/figure>\n

The above exposes two functions:<\/p>\n