From, the Money Wiki
Jump to: navigation, search

Draft Brainstormining defining Vocabularies for ReQuest Ontology using triples.

Also see :


"Transaction Contract" semantic web vocabulary.

Enable scalable, non centralized/distributed, emergent governance and economics, with any type of measurement units, in networked hybrid approaches between various types of relational dynamics.

These can include "existing" NGO's, Cooperatives, and any type of existing legal economic and governance structures,

as to enabling every individual/agent to choose what objectives to define, from where to draw resources, under what conditions, visualizing the inter-dependencies ( choosing what interdependencies to support - or not to support )


Attribution + GPL3 Affero :

Current Planned Approach

I m thinking of using a wiki to test an ontology and emergent folksonomies around interdependencies, with

- agents, and the various condition properties of such agents ( making them legal moral persons such as individuals, not for profits, corporations, cooperatives, ... in various jurisdictions )

- projected requests and support, and their eventual added condition properties

which can turn into

- agreed transactions between requests and supports,

which can turn into

- completed transactions and the histories of their interdependencies

GIS for Goal Oriented Transactions

Dante looks forward to a GIS for Goal Oriented Transactions

Using Netention - Automenta ?

Potentially a useful tool for expressing and visualizing "Transaction Contract Networks" ?

Metamodel and Programming

Use Kermata ?


and use Eclipse / EMF reflexive editor

note - alternative editor ? ?

other approach - declarative programming ?

Defining Triples to use in "ReQuest"

Check out Ontology Components

from wikipedia

Contemporary ontologies share many structural similarities, regardless of the language in which they are expressed. As mentioned above, most ontologies describe individuals (instances), classes (concepts), attributes, and relations. In this section each of these components is discussed in turn.

Common components of ontologies include:

  • Individuals: instances or objects (the basic or "ground level" objects)
  • Classes: sets, collections, concepts, classes in programming, types of objects, or kinds of things.
  • Attributes: aspects, properties, features, characteristics, or parameters that objects (and classes) can have
  • Relations: ways in which classes and individuals can be related to one another
  • Function terms: complex structures formed from certain relations that can be used in place of an individual term in a statement
  • Restrictions: formally stated descriptions of what must be true in order for some assertion to be accepted as input
  • Rules: statements in the form of an if-then (antecedent-consequent) sentence that describe the logical inferences that can be drawn from an assertion in a particular form
  • Axioms: assertions (including rules) in a logical form that together comprise the overall theory that the ontology describes in its domain of application. This definition differs from that of "axioms" in generative grammar and formal logic. In those disciplines, axioms include only statements asserted as a priori knowledge. As used here, "axioms" also include the theory derived from axiomatic statements.
  • Events: the changing of attributes or relations

Ontologies are commonly encoded using ontology languages.

Ontology editing tools

WebProtege is an open source, lightweight, web-based ontology editor. Our main goal in developing WebProtege is to support the process of collaborative ontology development in a web environment.

also see :

" suite of tools to construct domain models and knowledge-based applications with ontologies "

Agents URI ( "with potential write permissions" )

- Person ( can include history meta data, relations metadata, interests, etc )

- Project ( meta data : defined in time and space , has a "founder" , or several founders, broader intention(s) , and other types of affiliation from other uri agents to the project )

- Organizations ( which itself can include meta data of Persons affiliated to it , missions , ... )

Objects URI

- "Representation of" ( one of the above agents ) - which has no write permissions / is not an agent, but can symbolize an agent

- "Representation of" an object

Representations of Unique objects ( which are not agents ) can become confirmed objects based on their metadata and contracts

For example, the representation of a unique design of an object can become "an object" based on its history and the requirements it may have to become an object. For example, a physical object may require further Research and Development, Aggregation of Resources and Logistics, further Financial solutions, and Manufacturing processes, before being confirmed into physical reality, and being confirmed so in the data base through the spinning off into a new URI representing such physical object, and all the metadata related to its history.


"write permissions"

depends on "conditions created".

Starts by "Person" Creating "other objects" : creating other non-person agents ( mostly projects ).

Organizations can be created by persons, and get legal value through contracts made with persons who represent the legal framework.

Legal frameworks can be expressed through making links with data and persons, and through creating or expressing existing contracts, with the signatures of the persons or organizations involved in such contracts.


A person can also make a "representation of" what it sees from its viewpoint :

an agent can also "make a representation of" agents that have no write permissions, such object being defined as an interpretation. Such "representations" can be confirmed by other agents who have access to them.



Agents can "see" triples and contract networks that triples form based on the status of the objects created. Some agents may prefer to "hide" the graphed objects they create behind a key ( public key / cryptography ), but an agent, defacto, can choose to share the data created with everyone.


Actions :


"ReQuest to receive"

"ReQuest to support"


more actions can be defined based on the needs of the system

examples of more verbs in relation to contracts providing access to usufruct :