12 Dimensions/Architecture - Revision history

Narek at 13:45, 19 June 2017

2017-06-19T13:45:09Z

Narek: 4 revisions imported

2017-06-19T11:49:32Z

4 revisions imported

Narek: /* Architecture */

2015-02-03T09:00:18Z

‎Architecture

Narek at 15:37, 4 February 2012

2012-02-04T15:37:48Z

Narek at 15:28, 4 February 2012

2012-02-04T15:28:42Z

Narek: Created page with "==Architecture== ===Federation and Interoperability=== By providing the federation and interoperability of platforms and web services, OMPlanet aims to make an ecosystem not fal..."

2012-02-04T15:26:24Z

Created page with "==Architecture== ===Federation and Interoperability=== By providing the federation and interoperability of platforms and web services, OMPlanet aims to make an ecosystem not fal..."

New page

==Architecture==

===Federation and Interoperability===
By providing the federation and interoperability of platforms and web services, OMPlanet aims to make an ecosystem not fallible to attempts of exploiting or manipulating it for personal benefit, to centralize and misappropriate resources for vested interests of few shareholders.

Federated networks are designed upon the same principles of confederation. In simple words: in a federated environment there are many service providers from different domains for similar types of service but they are all interconnected and it is possible for the users to interact across the platforms. Everyone is able to choose his/her preferred platform to access his/her web service (e.g. social network) which is in turn interoperable with other platforms.

===Public Web Services===
However preferable it is to have such platforms interacting in federated or peer-to-peer manner with decentralized management and all data in distributed servers and DBs, it is too complex to make it possible without using some global centralised services. For example to make available services such as unique ID generation, user authentication, offline messaging, sharing access to public/protected data, etc., centralized public web services and centrilized data storage is necessary.

Considering these limitations, the OMPlanet ecosystem will also hold public client-server based systems. The necessary services and servers will be transparently maintained by community volunteer efforts. Explained in P2P logic there needs to be enough super-peers that are willing to host some part of server functionality and light-weight peers who are only users in the environment (e.g. users accessing via limited mobile devices).

Below is one of the early stage sketches of the ecosystem that represents real world dimensions interacting with [[:Category:OMPlanet|OMPlanet]] public web services.

[[File:omplanet_architecture1.png|center|700px|System draft design]]

← Older revision		Revision as of 13:45, 19 June 2017
Line 12:		Line 12:
	Below is one of the early stage sketches of the ecosystem that represents real world dimensions interacting with [[:Category:OMPlanet\|OMPlanet]] public web services.		Below is one of the early stage sketches of the ecosystem that represents real world dimensions interacting with [[:Category:OMPlanet\|OMPlanet]] public web services.

−	[[File:omplanet_architecture1.png\|center\|~~700px~~\|System draft design]]	+	[[File:omplanet_architecture1.png\|center\|600px\|System draft design]]

@@ Line 1: / Line 1: @@
 ==Architecture==
-=== Object-oriented Sociality===
+===Object-oriented Sociality===
 ===Federation and Interoperability===

← Older revision		Revision as of 15:28, 4 February 2012
Line 1:		Line 1:
	==Architecture==		==Architecture==
		+	=== Object-oriented Sociality===

	===Federation and Interoperability===		===Federation and Interoperability===

← Older revision	Revision as of 11:49, 19 June 2017
(No difference)

@@ Line 1: / Line 1: @@
 ==Architecture==
 ===Federation and Interoperability===
-By providing the federation and interoperability of platforms and web services, OMPlanet aims to make an ecosystem not fallible to attempts of exploiting or manipulating it for personal benefit, to centralize and misappropriate resources for vested interests of few shareholders.
+By providing the federation and interoperability of platforms and web services, OMPlanet aims to make an ecosystem not fallible to attempts of exploiting or manipulating it for personal benefit, to centralize and misappropriate resources for interests of few shareholders.
 Federated networks are designed upon the same principles of confederation. In simple words: in a federated environment there are many service providers from different domains for similar types of service but they are all interconnected and it is possible for the users to interact across the platforms. Everyone is able to choose his/her preferred platform to access his/her web service (e.g. social network) which is in turn interoperable with other platforms.
 ===Public Web Services===
-However preferable it is to have such platforms interacting in federated or peer-to-peer manner with decentralized management and all data in distributed servers and DBs, it is too complex to make it possible without using some global centralised services. For example to make available services such as unique ID generation, user authentication, offline messaging, sharing access to public/protected data, etc., centralized public web services and centrilized data storage is necessary.
+However preferable it is to have such platforms interacting in federated or peer-to-peer manner with decentralized management and all data in distributed servers and DBs, it is too complex to make it possible without using some global centralized services. For example to make available services such as unique ID generation, user authentication, offline messaging, sharing access to public/protected data, etc., centralized public web services and centralized data storage is necessary at some point.
-Considering these limitations, the OMPlanet ecosystem will also hold public client-server based systems. The necessary services and servers will be transparently maintained by community volunteer efforts. Explained in P2P logic there needs to be enough super-peers that are willing to host some part of server functionality and light-weight peers who are only users in the environment (e.g. users accessing via limited mobile devices).
+Considering these limitations, the OMPlanet ecosystem will also hold public client-server based systems in a specific way. The necessary services and servers will be transparently maintained by community volunteer efforts. Explained in P2P logic there needs to be enough super-peers that are willing to host some part of server functionality and light-weight peers who are only users in the environment (e.g. users accessing via limited mobile devices).
 Below is one of the early stage sketches of the ecosystem that represents real world dimensions interacting with [[:Category:OMPlanet|OMPlanet]] public web services.
 [[File:omplanet_architecture1.png|center|700px|System draft design]]