------ Object Memory Model Provenance Task Group

--- Motivating questions:

Is the Object Memory Model as such a model of Provenance for a physical artifact? If that is the case - which are the implications? How to deal with provenance of contained information?

### Short description:

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. The Object Memory Model (OMM) describes the structure of an object memory. 

### Alternative/existing provenance standard? (Or a complementary concept?)

Physical Markup Language (PML)
Logging standards (in particular, logging business processes)

### Domain specific? (If yes, is it only a domain specific convention for a general provenance standard? If yes, which one?)

No.

### Subject specific? (Are there any restrictions on the subject of the provenance information?)

(?)

### Based on existing data model? (Is the standard/concept embedded in an existing general standard or data model?)

No. The working draft is expressed via XML; other format encodings are currently investigated.

### Are there bridges/crosswalks to other standards?

The OMM does not address modeling contents of an object memory. Thus, it serves as a content container. The container description includes metadata, which are based on Dublin Core Metadata.

### Are there documented use cases that should be taken into consideration for the Provenance WG?

User-generated Data for Documenting Object Provenance: In retail scenarios it is often perceived as desirable to have provenance information about the origin of an object or previous interactions with an object that may impact consumer behavior. Examples of this are added information about the producer of a product such as in a fair trade shop, previous owners of the object in scenarios that deal with second hand goods and more generally peoples interactions with a product over the course of its lifecycle, and other kinds of product experiences ranging from ratings to extensive reviews.

Event Logging for Process Documentation: Complex production processes are error-prone. For more efficiency of production process, to avoid errors and to increase product quality the real life process data will be record on an object memory linked with objects. These objects can be products as well as the machines and tools which are needed for production. The objects interact and communicate with each other. So a product is able to communicate about a failure during a routing process, in consequence the next routing process cannot start. Besides of that such specific process information might be interesting for other companies or end users.

### Known, relevant issues?

### Website:
http://www.w3.org/2005/Incubator/omm/

### Contact for Provenance WG?
Alexander Kröner
alexander.kroener@dfki.de