An ORM-like interface to treat the atomspace similarly to a regular relational DB needs to exist. about opencog HOT 4 CLOSED

While I don't disagree, you might want to expand on what you mean by "ORM-like interface". Do you mean a query language like SQL, or a better defined API, or an declarative ORM that automatically maps entities/relationships to atoms?

from opencog.

I concede that was more rant than design document, and I apologize. Exposing the cogserver's query API to network clients via some well-defined RPC standard would seem to be a good move, with the goal being to make the semantics of accessing the atomspace as familiar as possible to web developers used to, e.g., the Ruby on Rails workflow. I'll try to flesh this out more completely; in the meantime I'd like to leave this up to attract attention.

from opencog.

That's completely understandable. As I mentioned on the mailing list, this was the first api I built several years ago and I'll be the first to admit it's lacking.

However, having worked with the C++ API a lot, I think it's also got problems. I was intentionally trying to avoid a direct link.

Happy to have a redesign, or start from a Python/Ruby web interface and create the json API to fit. Thanks for the feedback and sorry for the frustration ;-)

from opencog.

There are a nearly infinite number of thins wrong with opencog. This would need a detailed use-case and design plan.

from opencog.