Re: [opencog-dev] Current status of the Space/Time Server

2019-05-18 Thread Ben Goertzel
*** The other meta-question is "who is managing this process?" -- it feels like progress is at a dead stand-still; no one is communicating on any communications channels visible to me. *** This is because you are not on SingularityNET's internal Slack where a lot of the current discussion is

Re: [opencog-dev] Current status of the Space/Time Server

2019-05-18 Thread Linas Vepstas
Ben, You really don't need any fancy words for this. The design for this was done last spring, it was done for Alexey's Potapov's team. Its called "Values" and the RandomValue example shows how to use it. You can do continuations to your hearts-delight under the covers. There's no technical

Re: [opencog-dev] Current status of the Space/Time Server

2019-05-18 Thread Linas Vepstas
Ugh. With great trepidation. 1) It's private, as you point out, not public. 2) with Slack, even if it was public, it is impossible to make any kind of record of what was said, collect it, publish it. In particular, that means that you cannot use a google/yahoo/bing/duckduck-go to search for

Re: [opencog-dev] Current status of the Space/Time Server

2019-05-18 Thread Linas Vepstas
On Fri, May 17, 2019 at 10:23 AM Vitaly Bogdanov wrote: > Hi Linas, > > The intended design is that there is a well-known Value that is attached >> to red-cube. That Value is knows how to obtain the correct 3D location >> from the SpaceServer (or some other server, e.g. your server). That Value

Re: [opencog-dev] Current status of the Space/Time Server

2019-05-18 Thread Ben Goertzel
*** For example if generic predicate uses value to verify whether object is "red", then what it expects from value is pair of doubles (mean, confidence). If our value returns such pair of doubles it forgets all computation graph which led to this result. It means that we are not able to propagate