I remember taking a quick peek at Eresye when it was announced a while back. My first impression was that it implemented a lot of prolog-like features directly in Erlang. Another option would be to code in Erlog which is a prolog. As it is written in Erlang there is no problem in passing data between them, though the interface does need some work. I didn't have an application in mind when I wrote it so I didn't really know the best way to build the interface.
<br><br>Robert<br><br><div><span class="gmail_quote">On 05/12/2007, <b class="gmail_sendername">Joel Reymont</b> <<a href="mailto:firstname.lastname@example.org">email@example.com</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<br>On Dec 5, 2007, at 1:37 PM, Robert Virding wrote:<br><br>> Is there a specific application or use you have in mind?<br><br><br>Dialog systems based on natural language.<br><br>There's GoDIS  and its underlying TrindiKit. These use SICStus
<br>Prolog and I thought of hooking these up to Erlang. On a second<br>thought, I don't have an extra 4K EUR for two SICStus licenses. I'll<br>try to implement the dialog management engine in Erlang, using ERESYE<br>
 and lots of elbow grease.<br><br> Joel<br><br> <a href="http://www.ling.gu.se/grupper/dialoglab/godis/">http://www.ling.gu.se/grupper/dialoglab/godis/</a><br> <a href="http://sourceforge.net/projects/eresye">