Help with OAGIS schemas, anyone?

I know of a company embarking on an integration initiative.  They’d like to build their own enterprise LDM, and ‘magically’ map it to the OAGIS message schemas. That’ll probably mean that they can’t magically create or update the XML schemas, but they would like to manage a single XML model if they can, mapped to all the XSDs, and use it to regenerate XSDs when they change.

That means they’d have to reverse-engineer a single XML model from the OAGIS schemas, and map it back to those schemas.  Has anyone tried this?

3 thoughts on “Help with OAGIS schemas, anyone?

  1. Mike Rowell April 20, 2010 / 15:28

    There are lots of implementations of OAGIS from both large and small companies around the world. Case studies are available at:

    OAGIS to your company’s point provides a messaging model that a company may use to integrate their portfolio of applications. As it is not specific to a given implementation there may be the need to extend OAGIS for you implementation OAGi provides both documentation and training on how to do this.

    If you have specific questions, please feel free to contact me offline.

  2. Ralph Hertlein April 20, 2010 / 17:23


    Not sure I fully understand but it seems that attempting to map an LDM into a standard is the wrong question.

    When would there ever be a need to do so? An enterprise data model is a unique conceptual representation of how the enterprise sees and relates to itself and to the world. Using such a model for business functions, either internal or external is to say to the world, “I have my own unique standard and if you want to do business with me – you must speak my language … including all my internal apps”

    I see your question as a different challenge – can the enterprise data model (EDM) be represented within a standard for a given business process need. If it can, then they are golden. But it always requires the translation of the EDM through an adapter that will modify the EDM to perform a specific business step or interaction. That adapter transforms the EDM into something that will shield a company from vendors, customers, partners and suppliers individual EDMs or applications. A standard. Will never be a direct map.

    I view business standards like OAGIS as portable, generic databases that instantiate many enterprise data models in such a way that they can be translated and understand through business process. These standards, by requirement, cannot carry all the possible elements and relationships represented in an enterprise model directly as other applications and companies would never understand things that way, but they can represent EDMs correctly for specific business process. These standards by necessity will never and should never be a one-to-one with every enterprise data model. They would be impossible to use if they could ever accomplish this.

    So to me the question is not a one-to-one mapping, but rather a business representation of the EDM, through a common process into an interoperable standard with possibly a technological way to also create and exchange any needed extensions?

    I know from experience that OAGIS does this very well.


    For clarity – I am also contracted on staff for OAGi (

    • George McGeachie May 12, 2010 / 08:44

      Hi Ralph, we’re in agreement on this. The LDM can be regarded as an EDM, which will be mapped (perhaps at a higher level of abstraction) to business processes. When new services are developed, the OAGIS schemas will provide an extendable template. However, the schemas cannot be extended until they’ve ‘mapped’ the contents back to the EDM, so they know what XSD elements to use, add, or amend. Any changes or additions are likely to affect multiple potential schemas, so some way of managing those changes is needed, hence the idea of creating a single model of OAGIS. The OAGIS downloads include PDF extracts from a UML model, so I assume OAGIS uses a similar approach.
      My real question revolves around managing the actual models, the linkages between them, and the mechanism used to generate the XSDs (and any required translation to and from other semantics).

Leave a Reply