Saturday, August 14, 2004
On the issues of separation of
syntax and semantics pragmatics à .
Previous proposed technology evaluation à .
Architectural discussion
2:12 PM
Thank
you for making a response quickly on a technical issue that has to be thought
about. This bead is one of a series that
will be on architectural issues and on how the new software might be
packaged. [68]
First,
bead [66] is now edited
so that the discussion about the phenomenon in which the deep innovation
community is getting no income is moved to and side note and we will await the
response or non-response of others on what happens with this
communication. This is a larger issue
that must lead to a National Project to
redefine computer science.
I
personally have done the Hilbert encoding in both Linux and Windows, but it is
not licensed and is a bit different from the patent. (We will leave this issue...
as it is my anticipation that funds will eventually be found to take
care of the issue in a proper fashion.)
I will also say here, and remind myself, that the Orb notational paper
and my subject matter indicator software was strongly influenced by Applied
Technical System’s “CCM” (Contiguous Connection Model) patent.
My sense is, Ken, that the, what I am calling the, Readware knowledge of language repository can be read out and read back into a structure that resides in an Intel processor environment and which is addressed by Forth, which is the native language for the Hilbert engine. The Forth "OS" for the Hilbert Engine (TM) makes functions calls to the Windows kernel - but these can be reoriented to a Linux kernel. Nathan is good at this.
You
will have “services” that need to be ported also. Your interfaces are in Linux, so we have to develop an API to the
interfaces. Can you see that this might
be doable in the time allocated?
I
will also say that I have lived in the Linux kernel and in the Java virtual
machine while doing work with Sandy Klausner on his CoreSystem engine, last
year,.... and this is where we
eventually will go... since data regularity in context allows a compression
dictionary to be used to replace the overheads in present day "web
services".
I
have not followed the Hilbert engine architecture for the past two years, since
I worked for a short period of time for Bjorn (2002?).
Bjorn
will know how to do this, and given that you have patent on your work and we
can sign a very narrow agreement between Readware and PriMentia, then the
absorption of your technology by a Hilbert engine should take the few weeks
that I think it will take.
comments...?