|
|
| (79 intermediate revisions by 2 users not shown) |
| Line 1: |
Line 1: |
| − | A draft description of the 12 web dimensions of OmPlanet, explained with an object oriented design style:
| + | [[File:web_community_graph.jpg|thumb|700px| ]] |
| | | | |
| − | ''Data'' holds object's member variables specific to its dimension: e.g. People object is a user profile and as its data contains profile name, unique ID, interests tags, etc.
| + | ==OMPlanet 12 Dimensions== |
| | + | {{:12_Dimensions/Description}} |
| | | | |
| − | ''Relations'' holds semantic relational references to other objects from the same dimension or from other dimensions: e.g. "People" object can have relations as "friend" or "co-worker" to several other "People" objects from the same dimension and as well can have several references to "Real Places" objects with relations like "work place", "home" or "meeting place", to "Services" objects with relations like "needed" or "offering", several references to "Events" objects as "participant" or "organiser", etc.
| |
| | | | |
| − | ''Services'' describes specific types of web services that are possible to provide only in a client-server way: e.g. unique ID generation or geographical maps, etc.
| + | {{:12_Dimensions/Architecture}} |
| | | | |
| − | ===People=== | + | ==See also== |
| − | People (with their social graphs). Objects of social network user profiles from different social graphs with extendable profile fields.
| + | *[[:Category:OMPlanet| About OMPlanet]] |
| | + | *[[Network_of_Social_Networks]] |
| | + | *[[Source Codes]] |
| | | | |
| − | '''Data''': User name, ..., messaging space (e.g. inbox, wall).
| + | [[Category:OMPlanet]] |
| − | | |
| − | '''Functions''': Send message, send object, ...
| |
| − | | |
| − | '''Relations''': Each object contains also relational references to other similar objects(e.g. list of friends),
| |
| − | as well relational references to other objects from other OmPlanet dimensions (e.g. Files, Places, Events, etc.).
| |
| − | | |
| − | '''Services''': Services for necessary centralized functionalites of a
| |
| − | common social network - user authentication, control of unique IDs, search for profiles, offline messaging.
| |
| − | | |
| − | '''Examples''':
| |
| − | • PeerSon - p2p social network
| |
| − | • Facebook - server based proprietary social network
| |
| − | | |
| − | ===Groups===
| |
| − | This dimension holds objects which are representing different types of virtual groups of common interest people on the web
| |
| − | | |
| − | '''Data''': E.g. groups representing workplace, college or virtual community.
| |
| − | | |
| − | '''Relations''': Each object contains also list of People objects as its members and
| |
| − | possibly relations to other related objects (e.g. Services, Projects, Events, etc.)
| |
| − | | |
| − | '''Services''':
| |
| − | | |
| − | '''Examples''':
| |
| − | • Social network groups, discussion groups, forums, virtual games, etc.
| |
| − | | |
| − | ===Places===
| |
| − | A place as a logical description of an area such as a park, university, organization, etc. (whereas a location is a geographic coordinate with longitude and latitude).
| |
| − | | |
| − | '''Data''': Description of the place of interest, information about its type, characteristics and the geo location data (longitude, latitude).
| |
| − | | |
| − | '''Relations''': Events (event calendar of the place), Services (provided at the place), People (as members), etc.
| |
| − | | |
| − | '''Services''': Web based maps with layers representing OmPlanet objects (Google Maps, Bing Mpas, etc.).
| |
| − | | |
| − | - to enable users to instantly form communities based on location. - to identify specific places and to provide location-based histories (such as every important event that occurred at a specific address). Examples: Hospitality Club - This web site is for people who offer or search for free to share accomodations for travelers in many countries of the world.
| |
| − | | |
| − | - Omplanet is expanding the virtual world of SNs into the user's real world, encourageing people to interact in real time at real places based on shared interests or shared activities carried out with or without computers.
| |
| − | | |
| − | ===Events, Activities ===
| |
| − | | |
| − | '''Data''': Local Events, Concerts, Festivals, Workshops, Parties, etc. Past, present, upcoming.
| |
| − | | |
| − | '''Relations''':
| |
| − | | |
| − | '''Services''': Services to publish events, register to an existing event or demand/propose future events.
| |
| − | - Search for events by time, location, performer or descriptive keyword.
| |
| − | - Alerts which automatically notify users when events matching their search criteria are added or modified.
| |
| − | - Post feedback/question by People to past/upcoming events.
| |
| − | - Events Calendar (Aggregation and user friendly visualization of selective calendars from the global calendar
| |
| − | selected by a user according to his/her interests. subscription to such personalized views of calendars.) (e.g. Eventful)
| |
| − | | |
| − | '''Examples''':
| |
| − | • Eventful, ...
| |
| − | | |
| − | ===Travel, Transport===
| |
| − | Travel sharing, route sharing and planning, ride sharing... (e.g. hitchhikers can request for a ride and car drivers can accept if they share some part of their road, freesonar can help finding people around).
| |
| − | | |
| − | '''Data''': Start point (Longitude, Latitude), Endpoint(Longitude, Latitude), Direction (NE,NW, etc.),
| |
| − | Available Places(how many more can join), Means of Travel(Car, Bike, etc),
| |
| − | Purpose of Travel(Description), Places to Visit(Places objects), Traveling People(People objects).
| |
| − | | |
| − | '''Relations''':
| |
| − | | |
| − | '''Services''':
| |
| − | | |
| − | '''Examples''': Hospitality Club, Couchsurfing, Airbnb, Waze...
| |
| − | | |
| − | - Airbnb ...a wonderful service for travelers that don't want to spend a fortune on expensive hotels. The service allows anyone with a space to spare to connect with those who are looking for a place to stay. People can easily list and showcase their place to the millions of people who're traveling around the globe to help them find inexpensive (or not) places to stay, anywhere.
| |
| − | | |
| − | - Car Sharing on the go, alerts on mobile navigator with someone open to share the ride if destinations match.
| |
| − | | |
| − | - Making cars green (reducing the amount of cars driving 3/4 empty).
| |
| − | | |
| − | ===User Defined===
| |
| − | ...
| |
| − | | |
| − | ===Files===
| |
| − | | |
| − | '''Data''': Represents digital files that can be shared through network.
| |
| − | | |
| − | '''Relations''':
| |
| − | | |
| − | '''Services''':
| |
| − | | |
| − | '''Examples''':
| |
| − | • P2P file sharing, torrents
| |
| − | | |
| − | ===Web Content P2P===
| |
| − | Federated/Decentralized Internet...
| |
| − | | |
| − | '''Data''':
| |
| − | | |
| − | '''Relations''':
| |
| − | | |
| − | '''Services''':
| |
| − | | |
| − | '''Examples''':
| |
| − | • Federated social networks: OStatus...
| |
| − | • P2P hosting of web site contents that a web browser can read.
| |
| − | • Creation of Decentralized DNS system. Decentralized p2p based DNS systems: P2P-DNS
| |
| − | | |
| − | ===Services===
| |
| − | Direct free service exchange markets...
| |
| − | | |
| − | ===Transparent Banks===
| |
| − | '''Data''':
| |
| − | | |
| − | '''Relations''':
| |
| − |
| |
| − | '''Services''':
| |
| − | | |
| − | '''Examples''':
| |
| − | • Visa designed by Dee Hock,
| |
| − | • JAK Medlemsbank
| |
| − | • MonedaBcn is a social network created to build a social currency alternative to money in the area of Barcelona and surroundings.
| |
| − | • http://www.bitcoin.org/ - Bitcoin is a peer-to-peer currency. Peer-to-peer means that no central authority issues new money or
| |
| − | tracks transactions. These tasks are managed collectively by the network.
| |
| − | | |
| − | - https://barcelona.ecoxarxes.cat/ Interest free, owned by members, all transactions are transparent and trackable. It is possible to use it for funding projects - projects can publish public list of needed recources and volunteers can donate and choose for what need their contribution is going to be used and track it.
| |
| − | | |
| − | ===Items===
| |
| − | Material goods...
| |
| − | ...
| |
| − | | |
| − | ===Projects===
| |
| − | '''Data''':
| |
| − | | |
| − | '''Relations''':
| |
| − | | |
| − | '''Services''':
| |
| − | | |
| − | '''Examples''':
| |
| − | • Free software development projects, environmental volunteering projects, business projects...
| |
OMPlanet systems are similar to distributed local/personal clouds each of them managed and owned by its community members. Each OMPLanet system describes it's own data structure and models of interaction with other heterogeneous systems and data sources. One of the main objectives is to define a compact all-inclusive set of data models using decentralised standard descriptions to achieve data portability and toolchain interoperability among different web services, database systems and applications across the ecosystem.
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.
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 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 OMPlanet public web services.
