There are many aspects to HR-XML’s ongoing “version 3.0″ re-architecture. As I’ve previously written, HR-XML 3.0 represents a major re-vamping of the HR-XML data model. We’re aligning on the Open Application Group’s modularity model, design principles, and implementation of UN/CEFACT core component library. The result will be something with much more utility as canonical data model than our current data model.
Another aspect of the re-architecture is the use of OAGi’s Business Object Document (BOD) messaging framework. A BOD is a message. It brings together a verb and a noun. For example, “ProcessTimecard.” The BOD architecture provides the best of both worlds — course-grain verbs useful for working with arms-length trading partners and features such as action codes and expressions with which to perform fine-grain operations. For HR-XML, the adoption of OAGi BODs provide a terrific opportunity to apply a consistent messaging approach across our almost a dozen diverse HR sub-domains. By plugging into this framework with a proven track record and growing support by tool vendors and other vertical industries, HR-XML will advance the state-of-the-art in the HR services industry — which is very uneven at best. You certainly can find vendors using HR-XML as part of their web services and service oriented architectures. However, you can also find many vendors who are using HR-XML almost as if it were just another flat-file format (e.g., ftp’ing large batch files for processing).
At our recently concluded Atlanta meeting, we had the opportunity to learn more about BODs from experts within the OAGi community. The videos below and the accompanying slide deck should be useful to anyone wanting a solid technical introduction to BODs. Another opportunity to learn more is by registering to attend the upcoming OAGIS meeting, April 29-30, in Gaithersburg, MD.
Part 1
Part 2
Part 3