Transaction Graphs

The purpose of this page is to discuss the development of Ontologies and Softwares enabling, midst others, "Transaction Graphics", as to visualize and understand interdependencies, suggest requests, and support requests, within graphs using metadata.

It can also be used for further facilitating "sharing" transactions.

also see : http://cashwiki.org/en/ReQuest

excerpts from conversation - reply from S.

=Using Netention?=

1) there are several versions of Netention prototype, the source codes all of which are in github:

http://github.com/automenta

they are all made with Java, some of the versions are desktop application, and some are web-server based.

i consider them all prototype and very incomplete, so their value mainly lies in the potential they demonstrate.

if i continue working on it, it will probably be from scratch. and it doesnt need to be called Netention as its just a working codename... i'd feel fine if the ideas were transplanted into someone else's project too. so to be clear, i'm not attached to the Netention name for whatever is to become of its concepts: the philosophy, user-interface design, and algorithm design.

if you'd like to try the prototypes, i could try to package a runnable distribution. but there isn't much to evaluate besides what's in the videos. though i dont know if i made a video of the latest web-server prototype, so i might just make a video of that.

regarding transaction graphs
yes i suppose we are talking about the same overall process. but in netention i wanted to explore how simple of user-interface could provide that functionality. i concluded that all it needed was to essentially let someone describe what's on their mind in terms of actual (ex: i have) and virtual (ex: i want) objects.

hybrid of both a object-oriented and prototype-oriented system
2) with regard to the existential article (which i havent read in detail yet) http://existentialprogramming.blogspot.com/2010/08/not-all-properties-are-created-equal.html

i'm well aware of the shortcomings of object-oriented systems. in contrast, there are prototype-based programming languages:

http://en.wikipedia.org/wiki/Prototype-based_programming

i would consider Netention to be somewhat of a hybrid of both a object-oriented and prototype-oriented system (i was using the term Pattern to describe a template, several of which can be utilized when describing one Object=Idea=Thought=Concept ...), in that the ontology only suggests, but does not require, which properties=aspects=details one may specify (ie. whatever details come to mind about a particular idea).

this means that Netention ontologies could be evolved passively by a group of people utilizing the system. the ontologies would also be probabalistic in the sense that pattern Pa is likely to have Property X with 45% and pattern Pb is likely to have Property X with 3% etc... these probabilities would determine the ordering and visibility of certain user-interface parts. though, these ontologies would benefit from being seeded by existing ontologies, many of which are available, for example:

http://protegewiki.stanford.edu/wiki/Protege_Ontology_Library#OWL_ontologies

'''Netention descriptions, would in effect, be a programming language for reality. you could describe how things are, and how you would like things to be, and it would solve for whatever changes are necessary to bring your desired reality into existence. this would happen for everyone, piece by piece, so conflicts could be detected and resolved in the open like a wikipedia of the world's desires.'''