An Operations and Maintenance Information Open System Alliance

CCOM and other XML Schemas

One of the principles that guides the development of MIMOSA CCOM is to capitalize on the work that other standards bodies and industry groups produce. This is particularly significant as these other groups will have specialized domain expertise that MIMOSA does not want to reinvent.

As such, MIMOSA CCOM supports the ability attribute objects with XML constructs that use XML Schemas other than the MIMOSA CCOM XML Schema. Examples of these XML constructs include:

  • SVG for representing vector diagrams such as an asset component diagram
  • MathML for representing mathematical equations
  • HDF5 for representing multidimensional data such as pump curves

This is physically accomplished through the use of the XML ValueContent, which uses the XML Schema XMLAny type. For example, the XML example below demonstrates associating a MathML equation with an asset. An appropriate AttributeType must be identified whose Value is set to XML.

<CCOMData xmlns:xsi="" xmlns="">
  <Entity xsi:type="AttributeType">
    <ShortName>Calculation, MathML</ShortName>
  <Entity xsi:type="Asset">
        <ShortName>Calculation, MathML</ShortName>
        <XML format="MathML">
          <math xmlns="">

When undertaking XML Schema validation with XML documents that use external schemas, this will need to be done in multiple steps.

  1. As per normal, the root document can be validated against either the MIMOSA CCOM XML Schema or BOD XML Schema.
  2. As the XML ValueContent uses the lax attribute of XMLAny, each Attribute that uses the XML ValueContent needs to be validated against the appropriate XML Schema.