One of the challenges working with XMLs from sources is that rarely do those sources agree, to a degree of programmatic accuracy, on the implementation of the “standard” for representing information in XML.  This is a significant problem for companies that choose to work in publishing were Onix data and Publisher XMLs are critically important to implementation of a proper system, but are rarely consistent.

At EVN, we have introduced the concept of a “Framework” XML to abstract the XML required for operating a content system from the myriad implementations of publisher standard XML.  A Framework XML differs from regular XML in the following ways:

• The Framework only captures the elements that the content system (such as a website) requires to function
• The Framework enables one or more regular XML’s to “Dock” into it, which means:
  • A publisher’s XML, such as Onix, is mapped into the Framework XML by having each required Framework XML element point to an appropriate element in the publishers XML
  • A second publisher’s XML, which varies from the first has a different mapping of pointers from the Framework XML elements to their elements.
  • The publishers’ XML is not transformed or changed in any way

Once an XML is Docked into the Framework, the Publisher can change it at any time (updates for Onix are regular – at least monthly for most publishers), without changing the Framework XML that the system is operating against.

Utilizing Framework XMLs makes systems implementation easier - abstracting the layer of publisher operation in its XMLs from operation of a content system and the XML it requires to operate correctly.  EVN has substantial expertise in Framework XMLs and is happy to assist in their design, implementation and operation.