[GRASS5] Ideas

[Eric G . Miller]

Yes, XML would be better for such a beast.  In theory, you could write
XSLT scripts to translate the XML into targets usable by whatever.

You might be interested in entity http://entity.evilplan.org/ .  It's
currently hooked up with C, perl, and python.  It is rather new code,
but looks very interesting.

-- 
/bin/sh ~/.signature:
Command not found

---------------------------------------- 
If you want to unsubscribe from GRASS Development Team mailing list write to:
minordomo at geog.uni-hannover.de with
subject 'unsubscribe grass5'