From Object Memory Modeling Incubator Group Wiki
Jump to: navigation, search

2011-07-08 Agenda

Participants and Scribe

  • Alexander Kröner (scribe)
  • Boris Brandherm
  • Jens Haupert
  • Marc Seißler
  • Bruno Kiesel
  • Ralph Barthel
  • Daniel Schreiber
  • Barbara Schennerlein

TOP 1 Organizational issues

  • ACTION (DFKI) XG and beyond: The activity chairs have to be contacted.
    • Positive feedback of the Provenance Working Group; the group confirms interest in linking both groups, for now on an informal level
    • Preliminary discussions have shown potential in an alignment of the provenance concept explored by the WG with the OMM.
      • The provenance WG aims at a generic core provenance language, the provenance interchange language "PIL".
      • Assumption: Other provenance models will continue to coexist; therefore, mappings to PIL should be defined.
      • Is the OMM as such a provenance model, or could it benefit from adopting results of the WG?
      • Provenance concepts from the Provenance XG
      • Provenance Vocabulary Mappings
    • Mapping the OMM to PIL?
      • First, the group has to acquire information concerning how a mapping is technically done and verify if it is feasable at all.
      • If the outcome is a positive one, the mapping process will be started - most likely in August, 2011.
      • For the next weeks, Marc Seißler will take over the role of an OMM delegate.
      • An OMM introduction will be offered to the WG members.
      • Information concerning the mapping process will be acquired.
  • Contact to AIM-D, the German chapter of the Association for Automatic Identification and Mobility AIM Global
    • ACTION (DFKI) Preparing a phone conference with an AIM-D representative.
  • ACTION PENDING (DFKI) Contact Common Events Logging group once OMM event model is robust.

TOP 2 Review of open action points

  • ACTION (Siemens) ToC: A formal XML definition of the ToC is required.
    • This will be addressed once the Block Meta Data item is finished.
  • ACTION (Siemens) Block Meta Data: This vocabulary needs to be identified on the basis of work from SemProM.
    • Addressed next.
  • ACTION (UCL) Adapt the external link set example according to the data link proposal.
    • Done.
  • The following items will be discussed at a later point of time.
    • ACTION PENDING (Siemens) Standardized blocks: An overview of all standardized blocks with their particular metadata (MUST, MAY) is required.
    • ACTION PENDING (Siemens) Data Links on the OMM: The relationship between a structure block and a link block requires a deeper analysis.
    • ACTION PENDING (Siemens) Validation of the lifecycle values - current proposal is from SmartProducts, there is a slightly different proposal from SemProM, other value sets might be established in formal business process descriptions.
    • ACTION PENDING (DFKI) Using the Memory: Metadata should be identified, which would support interaction with the memory. A metadata flag “dynamic” should indicate that some block’ content might change.
    • ACTION PENDING (All): Verify MAY / MUST status of metadata in standardized blocks.


Next Telco:

  • July 22, 2011, 10:00