Smart-M3: Wikis


Note: Many of our articles have direct quotes from sources you can cite, within the Wikipedia article! This article doesn't yet, but we're working on it! See more info or our list of citable articles.


From Wikipedia, the free encyclopedia

Smart-M3 is a name of an open source software project that aims to provide a "Semantic Web" information sharing infrastructure between software entities and devices. It combines the ideas of distributed, networked systems and semantic web. The ultimate goal is to enable smart environments and linking of real and virtual worlds.

The key idea in Smart-M3 is that devices and software entities can publish their embedded information for other devices and software entities through simple, shared information brokers - a "push"-based information sharing model rather than specific publish-subscribe. The understandability of information is based on common ontology models common data formats. Another key idea is that Smart-M3 is device, domain, and vendor independent. It is free to use, open source solution available in BSD license. So, Smart-M3 refers to a piece of software technology, a number of software products encoding this software technology, a computing platform that the software products make available and any computing system that has been developed and deployed by using this computing platform.

The Smart-M3 software technology[1] is an evolving development of the Semantic Web with some specialized properties[2][3]. The Smart-M3 software products are open source software. They are available at sourceforge[1]. The Smart-M3 software products enable implementation of an Smart-M3 computing platform. The Smart-M3 computing platform allows to store and retrieve information based on tuple space mechanisms. Like in Linda (coordination language), a small defined set of semantically based interaction capabilities exists. A programmer can develop pieces of software that will make use of these interaction capabilities. A number of Smart-M3 software products are available that support such software development. Any such software must comply to the defined interface of the Smart-M3 computing platform, the defined communication protocol and the general design principles. A Smart-M3 system[4] is existing when such pieces of software have been built and deployed together with the Smart-M3 computing platform.

The Smart-M3 is being developed at Artemis JU programme in Sofia (smart objects for intelligent applications) and in Finnish national DIEM (Device interoperability ecosystem) research projects [5][6].



Smart-M3 takes aim of the multi-vendor, multi-device and multi-part issue[7][8][9] (that's where the term M3 comes from). This M3 issue means that many kinds of devices shall interact with each other, for instance a mobile phone, a television set and a laptop. A device may be composed of parts that are considered as individual partners for interaction with another device. For instance, a user makes use of the keyboard of a desktop computer for typing input to a mobile phone. Further, the user shall be free in choosing the manufacturer. Any piece of software engaging this M3 issue must at least be able to work properly in an environment constrained by these issues. Moreover, the Smart-M3 technology allows to build pieces of software that are able to take advantage of the opportunities such an environment offers[10][11].

When humans make use of the Web, they produce and consume human readable information and exchange this information based on the paradigm of 'persistently publish and actually read'. A piece of software executing in a device used by humans may transform, render, analyze and index that human readable information, but this software will not understand the information[12]. Also the technology of the Smart-M3 approach does not make such human-human communication machine-understandable. Instead, Smart-M3 follows the principle of the Semantic Web that machine-understandable information has to be prepared explicitly for software reasoning[13]. However, instead of specifying explicitly the means of interaction between a piece of software producing data and sending it across the internet to a piece of software consuming that data, Smart-M3 follows exactly the human-human interaction paradigm of 'persistently publish and actually read' also when software interacts with software across the internet[14].

While the notion of the Semantic Web embodies the vision of a single, universal web of machine-understandable information, Smart-M3 organizes the machine-machine communication by setting up in the Web many distinct spots of information exchange. At each spot a number of pieces of software executing in potentially many devices of potentially many kinds may publish and read information. This information has been prepared not only explicitly in machine readable form but also explicitly for each particular spot. Any particular spot of information exchange has a particular purpose or focus. All information that a particular spot of information exchange makes available will be dedicated to the particular purpose or focus of that spot. The number of pieces of software exchanging information at a particular spot is consequently limited to those that share this dedication.

At the core of the M3 issue is the issue of interoperability. The Smart-M3 approach deviates direct point-to-point interoperability because it applies the 'publish and read' mechanism at dedicated spots of information exchange in the Web. The publishing entity does not need to be interoperable with the reading entity. In fact the two even do not need to know about each other. Instead, Smart-M3 simply takes means that the publisher is able to publish at the selected spot of information exchange and the reader is able to read there.

System decomposition

Figure 1 shows a top view of a single system based on the software technology of the Smart-M3 approach. At the heart of the system is the corpus-M3 which decomposes further into a semantic information broker (SIB) and the real physical storage of data. Of course, this corpus-M3 must be hosted by a device. A number of devices hosts many M3-agents, including optionally the device already hosting the corpus-M3.

Figure 1: System decomposition

The SIB is the access point for receiving information to be stored or retrieving such stored information. In the data storage all this information is stored as a graph that conforms to the rules of the Resource Description Framework (RDF).

A M3-agent is a piece of software that has been produced and deployed for the purpose of communicating with a SIB and publishing or reading information there. A particular M3-agent is in range of a particular SIB if this M3-agent physically is able to communicate with this SIB by using one of the potentially many communication means this SIB is capable of and this M3-agent has been produced and deployed explicitly for publishing or reading information at this SIB. A particular M3-agent is associated with a particular SIB if this M3-agent is in range of this particular SIB and this M3-agent has been accepted by this SIB for publishing or reading information due to a positive result of some negotiation performed when this M3-agent made the initial communication attempt.

Various domains and application areas involve devices of many kinds and these devices may have different communication capabilities. In order to achieve interoperability in such an heterogeneous situation, the SIB supports multiple transport mechanisms, such as TCP/IP, HTTP, Bluetooth and NoTA[15]. Depending on the actual operating environment the most suitable transport technology is selected.

Notion of application

Applications are not constructed in the monolithic manner but rather from collaborating - through information sharing - sets of agents (M3-agents). Said set of agents depends upon the particular situation and context that the user is either experiencing or requires at that time. Agents may by provide a monolithic style user-interface but this is purely a user-interface and not functionality concept. The programming model is analogous to that of the actor model.

The Smart-M3 approach envisions computing beyond the traditional monolithic application program. Instead, scenarios are considered in which a set of M3-agents executing in various devices mash-up the information that these M3-agents store and retrieve in/from a particular SIB. This collaboration of M3-agents forms the application. Which collaboration and mash-up of information occurs depends on the data available and is not even known a priori [16].

Based on the data available within a space, a Smart-M3 system allows maintenance of an up-to-date digital representation of an environment covered by a set of devices executing M3-agents. If any information about the surrounding environment is easily available, an unlimited number of mash-up scenarios can be imagined that benefit from this information [17].

Development of technology and software products

Two examples of the application of this technology have been demonstrated in so called Smart Home environments[18] and in social networkinging situations[19].

Above entries to be expanded!

some words of how this work has been done and will continue....

list of contributors, what each has contributed e.t.c. ...

Developing and deploying a system

What is available (open source code, tools) for which purpose ...

who can use the stuff...

what can be done ....

how it has to be done...


  1. ^ Oliver Ian, Jukka Honkola(2008). “Towards the Dynamic Semantic Web”. Presented at TripCom 2008
  2. ^ Oliver Ian, Honkola Jukka (2008). “Personal Semantic Web Through A Space Based Computing Environment”. Presented at ICSC 2008
  3. ^ Oliver Ian, Honkola Jukka, Ziegler Jurgen (2008). “Dynamic, Localized Space Based Semantic Webs”. IADIS WWW/Internet 2008. Proceedings, p.426, IADIS Press, ISBN 978-972-8924-68-3
  4. ^ Honkola Jukka, Laine Hannu, Brown Ronald, Oliver Ian (2009). “Cross-Domain Interoperability: A Case Study”. Lecture Notes in Computer Science, Volume 5764/2009, p. 22, ISBN 978-3-642-04188-4. Presented at ruSMART 2009
  5. ^ Liuha, P., Lappeteläinen, A., and Soininen, J-P. Smart Objects for Intelligent Applications - first results made open, ARTEMIS Magazine, October 2009, No. 5, pages 27-29.
  6. ^ Koljonen, T. ARTEMIS and the rest of the world, ARTEMIS Magazine, October 2009, No. 5, pages 30-31.
  7. ^ Soldatos John, Alexopoulos Dimitris (2006). “Web Services-based network management: approaches and the WSNET system”. International Journal of Network Management, Volume 17 Issue 1, Pages 33 - 50. Wiley InterScience.
  8. ^ Farley P., Capp M (2005). “Mobile Web Services”. BT Technology Journal, Volume 23, Number 3, p. 202-213, ISSN 1358-3948 (Print) 1573-1995 (Online) . Springer.
  9. ^ Liuha Petri, Soininen Juha-Pekka (2008). “DEVICES AND INTEROPERABILITY ECOSYSTEM (DIEM)”.
  10. ^ Oliver Ian, Törma Seppo, Nuutila Esko (2009). “Context Gathering in Meetings: Business Processes Meet Agents and The Semantic Web”. Presented at TCoB 2009
  11. ^ Jantunen Joni, Boldyrev Sergey, Oliver Ian, Honkola Jukka (2009). ”Agent/Space-Based Computing and Radio Frequency Memory Tag Interaction”. Presented at IWERT 2009
  12. ^ Web Architecture from 50,000 feet. W3C
  13. ^ Berners-Lee Tim, James Hendler, Ora Lassila (2001). "The Semantic Web". Scientific American Magazine.
  14. ^ Triple Space Communication
  15. ^ NoTA World Open Architecture Initiative.
  16. ^ Soininen Juha-Pekka, Lappeteläinen Antti (2009). ”M3 Smart Environment Infrastructure”.
    NoTA 2009 Conference.
  17. ^ Cinotti Tullio Salmon, Bartolini Sara, D’Elia Alfredo, Roffia Luca, Spadini Federico, Trevisan Riccardo, Vergari Fabio, Zamagni Guido (2009). “Approaching the design of interoperable smart environments applications”.
    NoTA 2009 Conference.
  18. ^ Kary Främling, Ian Oliver, Jukka Honkola, and Jan Nyman (2009) Smart Spaces for Ubiquitously Smart Buildings. UBICOMM 2009.
  19. ^ Sergey Balandin, Ian Oliver, and Sergey Boldyrev (2009) Distributed Architecture of a Professional Social Network on Top of M3 Smart Space Solution Made in PCs and Mobile Devices Friendly Manner. UBICOMM 2009.


Got something to say? Make a comment.
Your name
Your email address