https://www.oreilly.com/ideas/fishing-for-graphs-in-a-hadoop-data-lake
So . . . . who wants to port MOSES?
https://www.oreilly.com/ideas/fishing-for-graphs-in-a-hadoop-data-lake
So . . . . who wants to port MOSES?
--
You received this message because you are subscribed to the Google Groups "opencog" group.
To unsubscribe from this group and stop receiving emails from it, send an email to opencog+unsubscribe@googlegroups.com.
To post to this group, send email to ope...@googlegroups.com.
Visit this group at https://groups.google.com/group/opencog.
To view this discussion on the web visit https://groups.google.com/d/msgid/opencog/00bd01d39b75%24e5a570a0%24b0f051e0%24%40gmail.com.
For more options, visit https://groups.google.com/d/optout.
We are undertaking now to port MOSES into the Atomspace (specifically
to make each MOSES deme an Atomspace, while leaving the
deme-management, feature-selection etc. code intact...)...
However as Linas notes, the intersection btw Atomspace and graph-DBs
is not about MOSES in particular....
A few of us have been thinking about potentially connecting Atomspace
to Apache Ignite,
so that Ignite could serve as a sort of distributed
backing-store, and the current Atomspace code would serve as the
"local cache" Atomspace on each machine in the distributed network....
Ignite is an interesting beast which is a sort of middleware layer
between data store and application.... This is not quite the same as
porting Atomspace logic to a graph DB, but perhaps it's in a similar
spirit...
-- Ben
On Fri, Feb 2, 2018 at 2:50 AM, Linas Vepstas <linasv...@gmail.com> wrote:
> Not sure why you say "moses" .. it would be "atomspace" to me.
>
> Atomspace has been a kind-of graph database since forever, but there was no
> promotion of it as such on internet forums, and so no one ever heard of it,
> and things like spark/haddoop have taken over 99.99% of the mindshare and
> actual usage. What to do in that world? The atomspace still offers some
> neat ideas and concepts, that these other systems can't yet do ... but its
> only a matter of time. So I'd say: port the atomspace to these graph db
> systems.
>
> --linas
>
> On Thu, Feb 1, 2018 at 10:01 AM, Mark Waser <mark....@gmail.com> wrote:
>>
>> https://www.oreilly.com/ideas/fishing-for-graphs-in-a-hadoop-data-lake
>>
>>
>>
>> So . . . . who wants to port MOSES?
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "opencog" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to opencog+unsubscribe@googlegroups.com.
>> To post to this group, send email to ope...@googlegroups.com.
>> Visit this group at https://groups.google.com/group/opencog.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/opencog/00bd01d39b75%24e5a570a0%24b0f051e0%24%40gmail.com.
>> For more options, visit https://groups.google.com/d/optout.
>
>
>
>
> --
> cassette tapes - analog TV - film cameras - you
>
> --
> You received this message because you are subscribed to the Google Groups
> "opencog" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to opencog+unsubscribe@googlegroups.com.
> To post to this group, send email to ope...@googlegroups.com.
> Visit this group at https://groups.google.com/group/opencog.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/opencog/CAHrUA36ScSdVJdgBr%3DmhPPz27-S-JYOAsLcocTEXgibrWsTpuw%40mail.gmail.com.
>
> For more options, visit https://groups.google.com/d/optout.
--
Ben Goertzel, PhD
http://goertzel.org
"In the province of the mind, what one believes to be true is true or
becomes true, within certain limits to be found experientially and
experimentally. These limits are further beliefs to be transcended. In
the mind, there are no limits.... In the province of connected minds,
what the network believes to be true, either is true or becomes true
within certain limits to be found experientially and experimentally.
These limits are further beliefs to be transcended. In the network's
mind there are no limits." -- John Lilly
--
You received this message because you are subscribed to the Google Groups "opencog" group.
To unsubscribe from this group and stop receiving emails from it, send an email to opencog+unsubscribe@googlegroups.com.
To post to this group, send email to ope...@googlegroups.com.
Visit this group at https://groups.google.com/group/opencog.
To view this discussion on the web visit https://groups.google.com/d/msgid/opencog/CACYTDBfgoj_4vb65EtwDrBERkEh-_s8F%2BWMAk%3DcqFHwomFbbEA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
On 02/03/2018 06:29 AM, Ben Goertzel wrote:
Nil, what are your thoughts on
https://github.com/opencog/atomspace/issues/1502
?
I seem to agree, however I don't think SetLink should be banished, instead it should probably be parsimoniously used, when for instance the user/agent wants to represent an immutable concept, probably a small one.
Although, I've been thinking why not replace, at least underneath, ListLink by ConsLinks (and perhaps SetLink by SetConsLinks)? This would solve the arity limit on the persistent storage side. For instance
List A B C
would be represented by
Cons A
Cons B
Cons C
List
and
Set A B C
by
SetCons A ...
not sure how to deal with the canonical ordering, I suppose the user/agent would enter a tree of SetCons in any order, and the AtomSpace may automatically re-order it.