Robert Howard wrote: > Since .NET 2.0 implements covariance, implementing Prolog to traverse these > networks amounts to nesting one YIELD-ing block for each literal in a Horn > Clause. > SEE: http://yieldprolog.sourceforge.net/, which is really all LINQ is doing. > I'd think it would be a natural step from there given the prolog-like syntax > of SPARQL. > Provided there is some fast and reliable way to access and store a network (a LINQ RDF store or an object database like db4o), and some way to do queries (nested iterators / yield Prolog), and some way to do object distribution (I was thinking SOAP), then that's about 90% of the battle. They are all well-understood and commercially supported technologies.
Nice but probably not crucial to have object implementations and queries all in the same formalism, whether that's Prolog, Lisp, XSLT, etc. E.g. the ability to query and program web services without a ad-hoc interpreter running there. Incidentally, I noticed the Java wrapper of Cyc has a SOAP service. It imagine probably would be possible to do serialization of objects to and from Cyc. ============================================================ FRIAM Applied Complexity Group listserv Meets Fridays 9a-11:30 at cafe at St. John's College lectures, archives, unsubscribe, maps at http://www.friam.org
