W3C home > Mailing lists > Public > public-device-apis@w3.org > September 2011

OMM-XG and Device APIs-WG

From: Alexander Kröner <Alexander.Kroener@dfki.de>
Date: Mon, 12 Sep 2011 13:35:07 +0200
Message-ID: <4E6DEE6B.2020409@dfki.de>
To: Thomas Roessler <tlr@w3.org>
CC: Philipp Hoschka <ph@w3.org>, Felix Sasaki <felix.sasaki@dfki.de>, Massimo Romanelli <massimo.romanelli@dfki.de>, public-xg-omm@w3.org, dom@w3.org, public-device-apis@w3.org, "Kuhn, Christian" <christian.kuhn@sap.com>
Dear Thomas (dear all),

thanks again for the discussion via phone on September 2, 2011, the 
Object Memory Modeling XG members really appreciate your and Philipp's 
feedback! To summarize the OMM XG's request:

* Would it make sense to (re-)design the OM API according to guidelines 
of the Device API WG, and -potentially- to integrate the OM API?

Background: The OMM XG members think that there is a relationship of OMM 
and Device APIs that might be interesting to explore.

An object memory is meant to...
....support collecting data about a physical artifact (at the artifact 
and/or in the Web)
....and to improve this way documentation and communication in 
artifact-driven processes.

As such, the XG members consider an object memory to be a feature of a 
"smart" artifact. Communication with the OMM is supported by an API (OM 
API, reference implementation in progress). Thus, a particular question 
to members of the Device APIs Working Group would be if the XG's 
assumption valid at all, and how to approach this topic.

### OMM Activity summary

* The OMM is based on related activities of several projects with 
partners from industry and research (umbrella: Innovation Alliance 
Digital Product Memory), however, most of them not active at W3C. An 
excerpt: DFKI GmbH, 7x4 Pharma GmbH, BMW Forschung und Technik GmbH, 
DP-DHL AG, SAP AG, Siemens AG, ABB, DB Schenker, Software AG, Fraunhofer.

* Their joint interest is (the application of) a memory-like structure, 
which could be used to associate a continuously growing information set 
with a product. Use cases include product integrity, supply chain 
management, documentation of maintenance processes, community-generated 
content.

* In response to this interest, the OMM XG developed the Object Memory 
Model. There is an XML-based representation of the model as well as 
software artifacts supporting the interaction with the model on the 
basis of a (draft) API.

* The model as such is focused on the memory structure and not on 
content modeling.

* The OMM XG members consider this model on the conceptual side to be 
finished.

* A continuation of the respective discussion in an interest group or 
community group is not expected to produce major modifications of the model.

* Therefore, the group members are interested to know if aspects of the 
Object Memory Model would qualify to become part of a W3C recommendation.

### References

* W3C Object Memory Modeling XG Home
http://www.w3.org/2005/Incubator/omm/

* W3C Object Memory Modeling XG Wiki [public documentation]
http://www.w3.org/2005/Incubator/omm/wiki/Main_Page

* Object Memory Format Specification V 0.98
http://www.dfki.de/~kroener/omm/omm_format_spec_0_98.pdf

* Projects
http://www.semprom.org/
http://www.adiwa.net/
http://www.aletheia-projekt.de/
http://www.smartproducts-project.eu/
http://talesofthings.com/

Best regards,
   Alexander Kröner (OMM XG chair)

-- 

Dr. Alexander Kröner --------- Intelligent User Interfaces Lab
DFKI GmbH  Campus D3 2  Stuhlsatzenhausweg 3 66123 Saarbrücken

Phone  +49.681.85775.5395
Fax    +49 681.85775.5021

http://www.dfki.de/~kroener/
--------------------------------------------------------------
Deutsches Forschungszentrum fuer Kuenstliche Intelligenz GmbH
Firmensitz: Trippstadter Strasse 122, D-67663 Kaiserslautern

Geschaeftsfuehrung:
Prof. Dr. Dr. h.c. mult. Wolfgang Wahlster (Vorsitzender)
Dr. Walter Olthoff

Vorsitzender des Aufsichtsrats:
Prof. Dr. h.c. Hans A. Aukes

Amtsgericht Kaiserslautern, HRB 2313
--------------------------------------------------------------
Received on Monday, 12 September 2011 11:53:47 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 9 May 2012 00:14:22 GMT