The metamodel provides two key functions for the JUMPER technology.

  First, it provides the formal structure of metadata tags that are necessary for a crosswalk mapping of metadata elements from one metadata 'standard' to another.

  Second, it meets the essential prerequisite to a meaningful mapping which requires a clear and precise definition of the elements in each 'standard'.

Each of these requirements is critical if we are to build a universal crosswalk using JUMP models. Our real world challenge, when we are mapping proprietary metadata, is that there are no 'standard' tags to easily align and no clear or concise understanding of the metadata from a descriptive, technical, or business metadata perspective to make it easily and universally understood.