Hi Amirouche, I skimmed th PDF's. Some of the goals are laudable: I quote: "the exchange of partial graphs, personalised views on data and a need for trust. A strong versioning model supported by provenance".
So, at a meta-level, yes. In practice, a triple-store strikes me as worthless, pointless, hopeless. Perhaps I am wrong -- I would love it if someone explained it to me. So from the PDF: ":Adam :knows :Bob" Great. Who? Fat Bob or skinny Bob? Did you mean Robert? Robert, like the guy down the hall, or Robert, the salesman who visits every Tuesday? Are you 100% certain about that? Or are you just guessing? In my personal experience, triples are wholly inadequate to deal with knowledge representation of the above form. If I'm wrong, let me know how. The atomspace was designed to hold arbitrary expressions, like "Adam knows Bob, the curly-haired, fat and always-smiling Bob, and I know this because Carol overheard it while standing in line at the cafeteria for lunch. So I'm 98% certain that Adam knows Bob." Should the atomspace also include some default model for exchange of partial graphs, versioning and provenance? Maybe. So far, we have little or no experience with any of this - no one has needed or asked for this, so I cannot guess if our current infrastructure is adequate, or if we need yet more. In a certain sense, versioning and provenance is already built into the atomspace, in a "strong" way. But no one uses it. -- linas On Sun, Feb 18, 2018 at 9:40 AM, Amirouche Boubekki <[email protected]> wrote: > I think I found the correct union of features that would be helpful in a > data science context. That is a database that works like git or git for data > kind of database. > > It's mainly inspired from datomic and two papers: > > - Git for triples http://www.hyperdev.fr/projects/neon/ldow2013-paper-01.pdf > - Revisions for triples > http://www.hyperdev.fr/projects/neon/10.1.1.662.1619.pdf > > Unlike datomic, the history is direct-acyclic-graph (DAG). That is, you can > have branches. I think that's the feature that makes all of this worthy. You > can populate your database with wikidata and then create a branch to add > edits and test your program against both versions of the database and > compare the results. The data is stored efficiently without copying. > > Do you think this kind of database can be useful in your work? > > -- > 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 [email protected]. > To post to this group, send email to [email protected]. > 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/db0ce7d7-5c27-4151-94a0-37ad1bf179f4%40googlegroups.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 [email protected]. To post to this group, send email to [email protected]. 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/CAHrUA34Ae29cos_owuG1vDqpLU%2BEBWS6Z6WiTLCHvy0tjkWjeA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
