From Object Memory Modeling Incubator Group Wiki
Participants and Scribe
- Barbara Schennerlein (BS)
- Bruno Kiesel (BK, scribe)
- Daniel Schreiber (DS)
- Alexander Kröner (AK)
- Jens Haupert (JH)
- Ralf Barthel
TOP 1 XG and beyond
- Final report
- AK has made a first proposal of the outline. All participants should take a look at it.
- AK will fill the final report with existing material during the next week. After this action it is necessary to clarify how the different contributions of all participants can be integrated in this document.
Introduction (what is the standard about - charter) Scope Why W3C State of the Art (Discussion of related work mentioned in the Wiki) Requirements (charter + key statements from use cases) OMM Structure (should make reference to requirements) Basics (to be discussed on an abstract level, probably in combination with examples) Block-based structure Header Metadata ... Table of Contents Standardized Blocks (why standardized blocks, followed by these blocks' description and XML encoding) Example Use Cases (All or selection? With examples?) Conclusions Recommendations Challenges (reference implementation) (best practice guide) (open issues from roadmap)
- Communicating OMM results within the W3C
- There is still no feedback from the Provenance-group. AK will stick at it and keeps us posted.
- Translating the OMM to other encodings
- AK has established connections with higher levels of the W3C. One finding of the new contact is the fact that we should communicate the OMM as model concept which can be incorporated in HTML 5. An independent XML-standard for OMM might be more difficult to place. HTML 5 is the driving force and it would be smart to connect the OMM-activities with it.
- The discussion showed that the technologies RDFa and Microdata might play a role in integrating OMM in HTML 5 and expressing semantic content. JH will check the impact of these technologies on OMM.
- After next week there will be a phone-conference with W3C-officials on the OMM-topic.
TOP 2 OMM XML
- Review of the OMM-XG Format Specification
- The specification is available in version 0.9 as a PDF-document and feedback from all participants is requested. The comments should be addressed directly to JH.
- The specification will be part of the final report. At the moment it is uncertain, whether this document will be integrated in the content of the final report or added as an attachment.
- Standardized blocks
- AK raises the question how we cover standardized blocks. Besides the encoding it is essential which metadata is mandatory or optional. A clear notation is essential.
- BS will try to clarify this issue till the next telco.
TOP 3 OMM Binary
- DS has checked the possibilities to convert XML to a binary format. Based on the SemProM binary format he has identified two different approaches: "Thrift" and "Protocol Buffers".
- Thrift is a software framework for scalable cross-language services development. It combines a software stack with a code generation engine.
- Protocol Buffers are a way of encoding structured data in an efficient yet extensible format. Google uses Protocol Buffers for almost all of its internal RPC protocols and file formats.
- According to DS Thrift seems the better approach for OMM, though it does not allow an exact mapping to the SemProM-binary format.
- Next action: Since a possible binary representation of the OMM would simplify the placement of the OMM in W3C it was decided that JH and BK explore the Thrift approach in context with the SemProM-binary format.
- September 9, 2011, 10:00