I did some banditry for my thesis - not surprised no one cited it though - it's pretty abstract. Thanks for this.
On 07/05/2010 07:15 AM, Dante-Gabryell Monson wrote:
http://teytaud.over-blog.com/article-35709049.html
*Slides in english: http://www.lri.fr/~teytaud/nicta.*pdf
http://www.google.be/search?sourceid=chrome&ie=UTF-8&q=monte+carlo+tree+search
I like the ideas. Although a caveat: an annotation system is not a
programming language.
If you are truly looking to create a "programming language":
http://en.wikipedia.org/wiki/Universal_Turing_machine could be a
useful reference. It would actually be a good idea to think about
what you are talking about above in terms of "Turing Completeness"
because this would give you a set of building blocks to create
basically any type of accounting possible.
Yet, it'd likely be most useful to people now to not create anything
that would force people to adopt one standard, or way of doing things.
The harder problem, with the larger payoff, is to think about how to
make existing alternative financial systems actually inter-operable.
First, there needs to be a way to abstract the financial system. What
is it typically used for? etc
We (Future Forward Institute/Forward Foundation) hope to release some
form of toolkit for accounting in wealth generating ecologies by late
fall.
--
--
Sam Rose
Future Forward Institute and Forward Foundation
Tel:+1(517) 639-1552
Cel: +1-(517)-974-6451
skype: samuelrose
email: samue...@gmail.com
http://forwardfound.org
http://socialsynergyweb.org/culturing
http://flowsbook.panarchy.com/
http://socialmediaclassroom.com
http://localfoodsystems.org
http://notanemployee.net
http://communitywiki.org
http://p2pfoundation.net
"The universe is not required to be in perfect harmony with human
ambition." - Carl Sagan
On Mon, Jul 5, 2010 at 8:38 AM, Dante-Gabryell Monson
<dante....@gmail.com> wrote:
> Thanks Sam !
> Can we create a form of representation/annotation which can also be used as
> a programming language ?
annotation cannot be used as a programming language. However, a
programming language could possibly use annotations applied, depending
on how the system is architected.
> Hence would there be an existing programming language that would be most
> suitable to express the objects and processes used ?
Any "Turing Complete" programming language could work to do the basic
processes that make up computation. It is best to create an abstract
of "objects and processes" which can then be implemented in any
existing or future programming language.
> Can we create a universal language
I was just thinking to myself yesterday that it is often a bad idea to
use the word "universal" in relation to languages. Because, in this
context, nothing can ever truly be "universal". There will always be
either cases you are not aware of, and/or languages that are not aware
of your "universality" effort. Thus, you'll always fall short of truly
being "universal". Therefore, using the word "universal" is inaccurate
and could be bad for present and future participant understanding of
the real nature of the system. It could create expectations which are
actually impossible.
>which can enable users to participate in,
> or even create any kind of architecture, building from a set of relations,
> objects, processes... and architectures of processes ( engines ? )
The funny thing is that what you describe above has already been done.
people *have* made this possible with basically any programming
language. There's a barrier to entry to those who are not programmers,
and even to programmers who do not have the time bandwidth to address
the problem properly.
> I m curious - What programming language(s) do you intend to use when
> creating an accounting toolkit ?
We started to implement in erlang. Although our initial creation will
likely be simple enough to be recreated in other languages.
> Does it correspond to the type of
> languages that could be used to define what I tried to express in this last
> message ?
The real mission is not to create one toolkit, or one programming
language, or one system, but convince as many participants as possible
to either implement a way for their systems to talk to other systems,
or get them to adopt a system that is designed for interoperability.
We have thousands of systems, but few people who understand that they
need to give the rest of the world some simple way to talk with their
system. It can be *any* standard, so long as it is decipherable and
callable outside of the local program it is deployed in. This would
then create an ecology that would allow *many* systems to be deployed,
*many* metaprogramming languages, etc.
The limit would then only be
the limit of the physical resources of servers and machines to serve
data. Many information ecologies have already transitioned towards
this type of ecology (they all usually implement some form of API,
etc).
The other major mission that I see, also not creating a toolkit, but
rather making it easier for people to *be* participants. For example,
automating participation through barcode, RFID tracking, GPS tracking
etc
The above 2 combined are the ecology needed, I believe, for what you describe.
(Dante, I removed the 2 email lists you had CC'ed as I am not
subscribed to them and my message is definitely be blocked from being
sent to them. I include p2presearch list which may be interested in
this discussion, as well as Michel, Paul and Richard)
> Thanks !
On Mon, Jul 5, 2010 at 10:06 AM, Dante-Gabryell Monson
What you have in mind is what we are now working on in Forward
Foundation/FFI, which is a way to create working models of the various
logics and dynamics of human interaction. Everything we've published
so far is a piece of the puzzle, and there are more coming, with a
large tying-together to follow.
If people want us to publish our work on this faster, we recommend
that they can donate to us (paypal: samue...@gmail.com ) so that
we can dedicate more time and development cycles in the short-term
future to creating this work and releasing it under an open license
(both software and theory).
On Mon, Jul 5, 2010 at 11:11 AM, Dante-Gabryell Monson
<dante....@gmail.com> wrote:
> Thanks Sam,
> I guess I will not wait till then, and will find access to telepathic
> channels in the ether of the noosphere ;)
> I also formulated such protocol in one of my last messages, pasted on
> http://cashwiki.org/en/A_Financial_Programming_Language
> although the difficulty is often to find a way of bringing words and phrases
> together in a way that others may understand,
> and then find other tools to make it more explicit :)
> ( even though we may use verbal language, and wiki's in the meantime )
> I imagine the protocol I shared to be able to express most existing
> financial architectures I have heard of,
> while also enabling them to be included into one distributed system.
> Its about turning it into a tool...
> real fun, to me :)
I promise I am not trying to be rude, and we'll always share as much
as we can. Yet, we all agree (myself, Richard, Paul) that there is
value in our taking time we've invested together in topics like this
to make sure that we can see some form of return on the investment of
time that we have into the hours and hours we've spent together
thinking, synthesizing, and building. The best return on investment
that we can get, given our commitment to releasing things in
copylefted and open way, is to create and publish/release things in a
way that helps us sustain our ability to do this type of work.
All of that said, I will share with you this:
Knowing the full scope of what you are thinking about, the best
approach you could take if you cannot actually work with real human
participants, would be to use http://ccl.northwestern.edu/netlogo/ or
python programming language, and create a "model" of the complex
adaptive system you are imagining and talking about on cashwiki. This
would help to generate some basic abstract operating principles, and
could show your idea in action. Logo is fairly easy to learn, and
Netlogo has built in visualization. Plus, in netlogo many of the basic
game theory concepts are already implemented, so this can make it
easier to borrow from existing code examples.
This example comes close to what you are probably talking about:
http://ccl.northwestern.edu/netlogo/models/DiningPhilosophers
It helps to understand the problems of "starvation" and "deadlock"
that are inherent in concurrent systems
(see also pdf attached which has lots of info)