Difference between revisions of "12 Dimensions/Description"

From OMPLanet Wiki
Jump to: navigation, search
Line 1: Line 1:
The '''[[:Category:OMPlanet|OMPlanet network ecosystem]]''' is built around ''social objects''. The social objects can be of different types - material objects, virtual objects, human beings, actions, events, cultural memes, etc. The OMPlanet specifies '''12 dimensions each of them representing a specific type of object or a specific dimension of human activity hosted by specific web platform or a service'''.
+
The '''[[:Category:OMPlanet|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 decentralised standard descriptions.
  
Explained in the object oriented design style each dimension contains objects specific to its domain which are interacting and in relation with each other as well as with objects from possibly all other dimensions. One of main objectives is to achieve interoperability by simple and uniform design. We have used the terms 'Data', 'Actions', 'Relations' or 'Services' to describe the specificity of each dimension:
+
The decentralised standard descriptions enable data portability and toolchain interoperability among different database systems, web services and applications. OMPlanet network ecosystem follows the [http://en.wikipedia.org/wiki/Resource_Description_Framework RDF] specification recommended by W3C.
  
*''Object Type (Dimension)'' Defines clearly what the objects are.
+
OMPlanet network ecosystem is similar to an [http://en.wikipedia.org/wiki/Ontology_(information_science) ontology model]. It specifies '''a set of 12 dimensions each of them representing a specific group of ''social objects'' (e.g people, places, events, etc.).  
  
*''Data'' holds an 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, interest tags, etc.
+
Each of the 12 domains/dimensions is organised into a specific data structure (social graph for people, map for places, calendar for events, etc.) that can be provided/hosted by different platforms and web services with corresponding 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/domains.
  
*''Actions'' are the VERBS which show what users can do with the objects. Usually each object is given a unique URL that enables users to share, comment, tag, link, buy, join, help, etc.
+
OMPlanet model resembles to class hierarchies in object-oriented programming but it is more flexible as it is meant to represent information coming from all sorts of heterogeneous data sources. One of the main objectives is to define a compact all-inclusive set of data models to achieve interoperable, simple and uniform design.
  
*''Relations'' holds 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 "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.
+
We recommend using [http://en.wikipedia.org/wiki/JSON-LD JSON-LD] notation to create evolvable and interoperable RESTful services (JSON-LD is a method of transporting Linked Data using JSON and provides mappings from JSON to an RDF model, JSON-LD requires relatively little effort from developers to transform their existing JSON to JSON-LD).
 +
 
 +
We have used the ontology terms 'Dimension', 'Attributes', 'Actions', 'Relations' or 'Services' to describe the OMPlanet model:
 +
 
 +
*''Dimension'' The object type or class. Defines clearly what the object is.
 +
 
 +
*''Attributes'' Parameters that objects can have. Holds an object's member variable specific to its dimension: e.g. People object is a user profile and as its data contains profile name, unique ID, interest tags, etc.
 +
 
 +
*''Actions'' are the ''verbs'' which show what users can do with the object. Usually each object is given a unique URI and enables to do actions with it like share, comment, tag, link, buy, join, help, etc.
 +
 
 +
*''Relations'' holds relational reference to other 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.
  
 
*''Services'' describes specific types of web services that are related to the object and provided in a client-server way: e.g. global unique ID generation, geographic map service, etc.
 
*''Services'' describes specific types of web services that are related to the object and provided in a client-server way: e.g. global unique ID generation, geographic map service, etc.

Revision as of 00:48, 22 January 2015

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 decentralised standard descriptions.

The decentralised standard descriptions enable data portability and toolchain interoperability among different database systems, web services and applications. OMPlanet network ecosystem follows the RDF specification recommended by W3C.

OMPlanet network ecosystem is similar to an ontology model. It specifies 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 domains/dimensions is organised into a specific data structure (social graph for people, map for places, calendar for events, etc.) that can be provided/hosted by different platforms and web services with corresponding 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/domains.

OMPlanet model resembles to class hierarchies in object-oriented programming but it is more flexible as it is meant to represent information coming from all sorts of heterogeneous data sources. One of the main objectives is to define a compact all-inclusive set of data models to achieve interoperable, simple and uniform design.

We recommend using JSON-LD notation to create evolvable and interoperable RESTful services (JSON-LD is a method of transporting Linked Data using JSON and provides mappings from JSON to an RDF model, JSON-LD requires relatively little effort from developers to transform their existing JSON to JSON-LD).

We have used the ontology terms 'Dimension', 'Attributes', 'Actions', 'Relations' or 'Services' to describe the OMPlanet model:

  • Dimension The object type or class. Defines clearly what the object is.
  • Attributes Parameters that objects can have. Holds an object's member variable specific to its dimension: e.g. People object is a user profile and as its data contains profile name, unique ID, interest tags, etc.
  • Actions are the verbs which show what users can do with the object. Usually each object is given a unique URI and enables to do actions with it like share, comment, tag, link, buy, join, help, etc.
  • Relations holds relational reference to other 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.
  • Services describes specific types of web services that are related to the object and provided in a client-server way: e.g. global unique ID generation, geographic map service, etc.