W3C home > Mailing lists > Public > www-archive@w3.org > December 2006

Re: N3 in JSON, euler.py, euler.js, unify() was: euler state of the art?

From: <jos.deroo@agfa.com>
Date: Sun, 17 Dec 2006 02:45:34 +0100
To: jos.deroo@agfa.com
Cc: Dan Connolly <connolly@w3.org>, Daniel Krech <eikeon@eikeon.com>, Chimezie Ogbuji <ogbujic@bio.ri.ccf.org>, public-cwm-talk@w3.org, public-cwm-talk-request@w3.org, www-archive@w3.org
Message-ID: <OFC247FADC.EB7E55D4-ONC1257247.00089B3D-C1257247.00099E58@agfa.com>

[correction]
> To unify {} nodes I was testing a case
> http://eulersharp.sourceforge.net/2005/11swap/xanthippe.n3
> where such nodes are rewritten as a collection of 3-tuples 
> and also found a rather nasty bug in unify (took 1/2 day
> to fix..) but the case now seems to be happy and gives
>
> :Xanthippe a (:Mortal :Woman).
>
> For the moment I've put the new version at

http://eulersharp.cvs.sourceforge.net/*checkout*/eulersharp/2005/11swap/euler.py?revision=1.49
and the differences are
http://eulersharp.cvs.sourceforge.net/eulersharp/2005/11swap/euler.py?r1=1.46&r2=1.49
(and will try a hg push when http://homer.w3.org:8765/ runs)

It was actually not an issue with unify but with eval 
(found it when fixing above issue for euler.js)


-- 
Jos De Roo, AGFA http://www.agfa.com/w3c/jdroo/
Received on Sunday, 17 December 2006 01:46:30 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 7 July 2008 08:09:54 GMT