Difference between revisions of "Foundation ontology"
(rv, put in wrong article) |
(clear and start restructuring) |
||
| Line 3: | Line 3: | ||
The [[W:OOP|OOP]] paradigm was designed to allow software and systems to be designed where the description of the program which is interpreted and acted upon by the computer has a direct relationship with the high-level ''model'' of the system. [[W:Prototype-based language|prototype-based language]]s make objects even more isomorphic to the real world by allowing any collections of functionality and information to be used as either an [[instance]] or a [[class]] on which other instances are based. The [[web3|semantic web]] also extends the object paradigm by creating a universal concept network which can be knitted together in a uniform way to create standard ontologies. | The [[W:OOP|OOP]] paradigm was designed to allow software and systems to be designed where the description of the program which is interpreted and acted upon by the computer has a direct relationship with the high-level ''model'' of the system. [[W:Prototype-based language|prototype-based language]]s make objects even more isomorphic to the real world by allowing any collections of functionality and information to be used as either an [[instance]] or a [[class]] on which other instances are based. The [[web3|semantic web]] also extends the object paradigm by creating a universal concept network which can be knitted together in a uniform way to create standard ontologies. | ||
| − | + | As of April 2016, a new attempt at refining all of the concepts of [[the nodal model]] within a more recent context where the idea is more refined and there is technology available now which covers nearly all of its requirements. Technologies like [[Telehash]], [http://nanomsg.org NanoMsg], [[Filament]] and [[Docker]]. | |
| − | |||
| − | + | The role of the foundation ontology is to define the [[system]] by which we can all organise our resources together in a fair and harmonious way (i.e. [[alignment|aligned]] with the [[core values]]). We can think of this ontology as defining a ''multiplexer'' or ''scheduler'' which is a tree of events triggering connections between roles and resources (also in the same tree). Any resource that needs to be connected with this multiplexer needs to be accessible by a compatible API. This unified tree of changing resource connection is the tree of moments and can be clearly defined in terms of information technology, see [[moment]]. | |
| − | |||
| − | + | The foundation ontology is the basic functionality common to all the network that is inherited by every node (moment) in the tree. The ontology can be thought of as a fundamental group of operating patterns that apply regardless of the specifics of the resources involved, and thus is the foundation of all node's functionality. | |
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
== See also == | == See also == | ||
| Line 51: | Line 15: | ||
*[[System]] | *[[System]] | ||
*[[Bottom line]] | *[[Bottom line]] | ||
| − | |||
| − | |||
Revision as of 22:58, 18 April 2016
|
A system of operating as an evolving organisation is common to all nodes in the Ontology, the conceptual structure of this kind of organisation that captures these principles of collaboration and self-governance is considered to be the Foundation Ontology for the Organic Design system. The Foundation Ontology is a common form of organisation that spans both real-world organisation, and informational systems alike, it defines what it is to be a node in the unified Ontology. Since the Foundation Ontology defines the attributes that are common to all organisations in the network, it's important that the bottom lines designed in its system remain aligned with the core values and common vision.
The OOP paradigm was designed to allow software and systems to be designed where the description of the program which is interpreted and acted upon by the computer has a direct relationship with the high-level model of the system. prototype-based languages make objects even more isomorphic to the real world by allowing any collections of functionality and information to be used as either an instance or a class on which other instances are based. The semantic web also extends the object paradigm by creating a universal concept network which can be knitted together in a uniform way to create standard ontologies.
As of April 2016, a new attempt at refining all of the concepts of the nodal model within a more recent context where the idea is more refined and there is technology available now which covers nearly all of its requirements. Technologies like Telehash, NanoMsg, Filament and Docker.
The role of the foundation ontology is to define the system by which we can all organise our resources together in a fair and harmonious way (i.e. aligned with the core values). We can think of this ontology as defining a multiplexer or scheduler which is a tree of events triggering connections between roles and resources (also in the same tree). Any resource that needs to be connected with this multiplexer needs to be accessible by a compatible API. This unified tree of changing resource connection is the tree of moments and can be clearly defined in terms of information technology, see moment.
The foundation ontology is the basic functionality common to all the network that is inherited by every node (moment) in the tree. The ontology can be thought of as a fundamental group of operating patterns that apply regardless of the specifics of the resources involved, and thus is the foundation of all node's functionality.
