Naming and branding:
So here's a proposal. Four things. Four names. Four brands:
* OpenCog Classic
* OpenCog AtomSpace
* OpenCog Hyperon
* OpenCog Incubator
"OpenCog Classic" consists of everything abandoned and obsolete; This includes PLN, URE, Attention, SpaceTime, Ghost, Relex, R2L, ROS, Eva/Sophia, MOSES (but not as-moses, see below).
"OpenCog AtomSpace" includes:
-- base AtomSpace
-- CogServer and atomspace-cog (for networking, json, websockets)
-- atomspace-rocks (disk I/O subsystem)
-- Proxy Nodes (for data routing, replaces attention bank)
-- Link Grammar
OpenCog Hyperon
-- the stuff you're working on
OpenCog Incubator
-- atomspace-prolog proof-of-concept
-- chemistry proof-of-concept
-- agi-bio
-- visualization
-- as-moses
-- vision proof-of-concept
-- hyperon-on-top-of-atomspace proof of concept.
-- etc.
The above is the branding and website design that I would like to see. It makes it clear what's what, what goes where, what's alive, what's dead. what's stable, what's new. what's broken, what's experimental. Does this work for you?
Two extra remarks:
The hyperon-on-top-of-atomspace proof of concept. Not sure if you didn't see the announcement, or you saw it and just hated it. I think putting Hyperon on top of the AtomSpace is not too hard, and I think it might work quite well, given that the code base is debugged and performance tuned. I understand that the current devel crew does not care for such a thing. But it is a viable path, and a kind of insurance policy.
Link Grammar. I've been working to integrate Link Grammar more closely with the base AtomSpace. It turns out that Link Grammar is a generic structure parser. Or rather, is close to one, although some fair amount of bending, welding and hammering is still required. I think it can be used to process visual/video data, audio data, sensory data in general. Part of the big deal is that link-grammar is now really really fast: Amir Plivatsy has performance-tuned the heck out of it, it runs about 100x faster than it did a decade ago. And since CPU's have also gotten faster, ... wow. So that is the dataflow, or structure-flow idea. Converting any kind of streaming data into a "streaming semantic graph" in real time.
AS-MOSES: As a whole, it is problematic. There are a few pieces/parts I'd like to rip out and breathe new life into. In particular, generic "knob-turning" and deme management would be excellent stand-alone plugins for the AtomSpace. I need knob-turning in order to train on video and audio feeds.
-- Linas