Difference between revisions of "12 Dimensions"

From OMPLanet Wiki
Jump to: navigation, search
(Fix broken links)
Line 2: Line 2:
  
 
==OMPlanet 12 Dimensions==
 
==OMPlanet 12 Dimensions==
 
 
{{:12_Dimensions/Description}}
 
{{:12_Dimensions/Description}}
  

Revision as of 09:09, 19 June 2017

Web community graph.jpg

OMPlanet 12 Dimensions

The OMPlanet network ecosystem is a distributed model of interlinked data systems that expose, exchange and share data among different systems in the network and outside of its boundaries based on decentralized standard descriptions.

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.

We specify the OMPLanet Social Graph with a set of 12 dimensions each of them representing a specific group of social objects (e.g people, places, events, etc.).


Draft Overview of the OMPLanet Social Graph with 12 Dimensions

We describe the OMPlanet network ecosystem similar to an ontology. We specify the OMPLanet Social Graph with a set of 12 dimensions each of them representing a specific group of social objects (e.g people, places, events, etc.).

Each of the 12 dimensions is organised into a specific data structure that can be provided/hosted by different local/personal clouds with corresponding web service interfaces. Usually each object is given a unique URI and it has different types of relations with other objects of the same dimension or in relation with objects from possibly all other dimensions.

Used terms:

  • Dimension: A general descriptive name for the group of object classes in a specific sub-domain, represents the top concept.
  • Type: The specific class describing the set of objects with the same type. E.g. the class Person to specify all the objects in the domain People.
  • Relationships: denotes a relationship between objects, one object can reference to another object/s 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 Places objects with relation types as work place, home or meeting place, or to Services objects with relations as needed or offering, or references to Events objects as participant or organiser, etc.
  • Data Properties or "Atributes": Parameters that objects can have. Holds an object's member variable specific to its dimension: e.g. People object can be a user profile with the attributes profile name, unique ID, interest tags, etc.
  • Actions: the verbs which show what action is possible to do with the specific object. E.g. share, comment, tag, link, buy, join, help, etc.
  • Services: describes specific types of web services that are related to the object class: e.g. social network, geographic map service, etc.
  • Structures: describes the data model or the common structure handling with the objects of the specific dimension. E.g. social graph for people, calendar for events, map for places, timeline for projects, etc.
  • Schemas: provide a data-modelling vocabulary for RDF data.

People

People with their social graphs and profiles. People objects are persons from different social graphs with extendable profile fields (the FOAF ontology descriptions can be used here).

Type: Person
 Subtypes: student, employee, artist, member, legal entity
 
Relationships:
 Relation types: friend, knows, in relationship, group member, from place, owns.
 Relation objects: list of friends, office address, etc.

Data Properties: User unique ID (e.g. WebID), name, address, contact, interests, competence, responsibility, messaging space (e.g. inbox, wall), etc.

Actions: Send message, send media object, invite, etc.

Services: distributed/central user authentication; search for profiles; messaging; etc.

Structures: social graph, social network, etc.

Schemas:
 • http://schema.org/Person

Examples:

 • Federated social networks - StausNet, PeerSon, Diaspora, etc.
 • FOAF - a machine-readable ontology describing persons, their activities and their relations to other people and objects.
 • WebID - A way to uniquely identify a person, company, organization, or other agent using a URI.
 • OAuth - an open standard for authorization, allows users to share their private resources (e.g. photos, videos, contact lists)


Places

A place as a logical description of an area such as a park, university, organization, etc. (with or without geographic coordinates of longitude and latitude). POI specifications by W3C are preferred to be used to representation of the Places objects.

Places objects will 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).

Type: Place
 Subtypes: couch, house, hotel, venue, city

Relationships: Events (event calendar of the place), Services (provided at the place), People (as owners, visitors, etc.), etc.

Data Properties: name, location, coordinates, description, etc.

Actions: geotag, add description, add comment, ...

Services: Web based maps with layers representing OMPlanet objects (Google Maps, Bing Mpas, etc.).

Structures: Map, building plan, geographic map, etc.
 
Schemas:
 • http://schema.org/Place

Examples: Google Places, Facebook Places

Events, Activites

For self-organized activities or events. People can publish real-time information about their current activity in their current location, initiate new activities, organize events or look for real-time events happening around them, or publish a demand for a specific type of event in a given area.

OMPlanet also provides distributed calendars to share and search events globally. hCalendar can be used as a simple, distributed calendaring and events format.

Type: Event
 Subtypes: group meeting, lecture, festival, concert, etc.

Relationships: createdBy, organizedBy, inPlace, etc.

Data Properties: Name, Description, past, present, upcoming.

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)

Structures: Calendar, program

Schemas:
 • http://schema.org/Event

Examples:

  • Eventful, Eventbright

Collectives, Organizations

Dimension that holds objects which are representing different types of virtual or non-virtual groups of people united within a specific field. E.g. communities with many members, tribes, neighborhood, a city, groups representing workplace, college, virtual or real organisation, NGOs, etc.

Type: Group same as Organization
 Subtypes:  Organization (members), City (citizens), Club (funs), Tribe, Neighborhood, NGO, Company, Corporation, team, social hub, circle of friends, company, corporation, social body, etc.

Relationships: group members, linked groups, (each object contains also list of People objects as its members and
  possibly relations to other related objects, e.g. Services, Projects, Events, etc.)

Data Properties: name, description, location, size, etc.

Actions: join, leave, send message, send object, ...

Services:

Structures:

Schemas:
 • http://schema.org/Organization

Examples:

  • Virtual groups of people, social networks, discussion groups, forums, virtual games, etc. 
  • Non-virtual communities of people (sharing living or working space) - Global Ecovillage Network

Collective Governance

Undefined yet....

These are the instruments to enable participatory decision making and acting processes. Place where multiple individuals can collectively vote and decide upon certain actions that the community might benefit, which, however, have an associated cost making it implausible that any one individually can or will undertake and solve it alone.

It can be only collection of votes to rise the public awareness or find consensus upon issues but not always the instruments to guarantee the complete realization of decisions.

Type: Decision
 Subtypes: Action proposal, vote, etc

Properties: Connection with People, Groups

Services: Power organization/distribution, politics, decision making, ownership, property, rights, rules 

Examples:

Avaaz - connecting citizens to drive sustainable political decisions, etc.

Projects

To be defined...

Type: project
 Subtypes: project, task, activities, practice, sport game, etc.

Media, Communication

Undefined yet....

Type: Item
 Subtypes: 

Data Properties:

Examples:

Transport, Travels

Travel sharing, route sharing and planning. For example car sharing on the go, with alerts on mobile devices, can allow drivers to take travelers if destinations match. This can reduce the amount of cars driving 3/4 empty.

Type: Travel Plan
 Subtypes: transport or traveler, transportation or trip

Relationships: 

Data Properties: Start point, Destination (from A to B), date/time, Longitude, Latitude, Direction, 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).

Actions: 

Services:

Structures:

Schemas:

Examples:

  • Travel sharing: GPS rout matches, etc.
  • Place-to-stay sharing: CouchSurfing, Airbnb
  • P2P Car Sharing: ...

Needs, Offers

Service exchange markets. All kinds of services offered P2P, voluntary based or paid. The currency can be the real money, virtual currencies or the 'spend-time' as a currency unit.

Type: Service
 Subtypes: cleaning, accounting, product, car, food, etc.

Relationships:

Data Properties: free/rent/sale, price value, virtual/real, price per hour, available district

Actions: 

Services

Structures

Schemas

Examples:

  • Some professional services
  • Couch-sharing, garden-sharing, car-sharing, etc.: CouchSurfing, Hospitality Club, etc.
  • Community insurance: Friendsurance
  • Buying, selling, exchanging: eBay, etc.
  • Free-markets of material goods.

Finance

Distributed and digital currencies and currency authorisation/exchange systems (banks 3.0). Transparent and fair lending structures, time banks and non-monetary value exchange systems.

Peer-to-peer currencies with no central authority that issues new money or tracks transactions and where these tasks are managed collectively by the distributed network.

Monetary systems that encourage people to exchange directly within their local communities with fair and transparent value exchange system, rather than centralising the resources in the global private banks managed by corporate entities driven by the profit of only few shareholders.'

Type: Money same as Currency
 Subtypes: digital currency,  state currency unit

Services: bitcoin, ripple, transparent banks, value exchange systems

Examples:

  • Digital currencies: Bitcoin, Etherium, Ripple
  • Crowdfunding: ....
  • Peer to Peer lending, Microfinancing: KIVA
  • Community Powered Capital: VenCorps
  • Crowd funded mortgage: Crowdhyptheek
  • Folk Banks: WIR Bank, JAK Medlemsbank
  • Currency Management System (CMS)
  • The initial Visa card system designed by Dee Hock which was a revolutionary example of such an attempt
  • MonedaBcn, a social network created to build a social currency alternative to money in the area of Barcelona and surroundings.

- 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 resources and volunteers can donate and choose for what need their contribution is going to be used and track it.

Games

Not defined yet...

Type: Community
 Subtypes:
Relationships: members, groups, resources,

Data Properties: name, description, etc.

Actions: play, join, leave, share, ...

Services:

Structures:

Schemas:
 • http://

Examples:

P2P Web Services

P2P hosted files, websites and web services. Undefined yet....

Type: Data
 Subtypes: text, article, binary data, wiki article, idea, message, multimedia file, web page, web service, etc.

Services/Structures: directory, wiki, web site, personal data stores (e.g. Project Danube), etc.


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 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 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.

System draft design

See also