This document discusses metadata mapping as a solution for metadata interoperability between systems. It defines metadata as data that describes other data and explains that metadata has building blocks like schemes and element definitions. The document also outlines some of the heterogeneities that can exist with metadata between systems. Metadata mapping is presented as a way to maintain representations of metadata and formally declare relationships between different metadata schemas to allow for metadata transformation and querying across sources.

1. Metadata Mapping
Presentation By Vladimir Bukhin on Oct 8th

2. Contents
• Metadata interoperability goals.
• Definition of Metadata.
• Metadata Building Blocks.
• Heterogeneities with metadata .
• Interoperability Solutions.
• Metadata Mapping.
• Conclusion.

3. Metadata
Interoperability Goals
• Metadata interoperability:
• Systems and applications can work with or use metadata across system
boundaries.
• Requirements:
• Machines need to communicate to exchange metadata.
• Machines must be able to read/process the data received.
• Machines + humans must be able to interpret the metadata correctly.

4. What is Metadata
• Metadata:
• “the sum total of what one can say
about any information object at any
level of aggregation, in a machine
understandable representation.”
• Information Object:
• “anything that can be addressed and
manipulated by a human or a
system as a discrete entity.”

5. Metadata Building Blocks
- Define Schemes, meta-meta-model,
UML, XML, SQL DLL.
- Defines how attribute like ‘title’ will be
semantically presented.
- Element Definitions.
- Content Rules.
- Descriptive Metadata elements

6. Metadata Heterogeneities

7. Interoperability Solutions
• Agreement on a certain model:
• Accredited institution like W3C or ISO.
• Consensus, Standard, or assurance of uniform implementation.
• Agreement on meta-model:
• Schema is defined by the same language (standard model with different
implementations)
• Reconciliation of structural and semantic
heterogeneities:
• Mapping schema languages to others’ language.
• Instance transformation (changing meta attributes to correspond)

8. Metadata Mapping
Maintaining
representations Start Find relationships and
heterogeneities
Metadata transformation.
Formal Declaration of
Answer queries over
mapping relationships
metadata sources.

9. Conclusion
• Mapping suggested over Standards.
• Standards require licensing, software
tools, personnel costs.
• Mapping has high discovery cost.

10. Bibliography
• Haslhofer, Bernhard and Wolfgang Klas. 2010. A survey of techniques
for achieving metadata interoperability. ACM Comput. Surv. 42, 2,
Article 7 (February 2010), 37 pages.