Here's the fourth post in this series. In part 3, I related some of the external influences that shaped the timing and architectural direction of the HR XML 3.0. In this post, I'll cover the 3.0 development process itself at a high level and get us up to present day. I'll finish with a "Part 5" that talks about some of the motivations for the HRInterop initiative and what we are trying to achieve.

Architectural Influence

As I mentioned in a prior post, HR XML has enjoyed a long history of liaison with OAGIS. However, before the 3.0 initiative, the two organizations -- like most standards organizations -- had little concrete progress towards interoperability. I've gone into detail about the issues we encountered as we began the migration from 2.5 to 3.0 in past presentations. The process involved taking the HR XML 2.5 content out of these silos (.png), slicing and dicing all the component types, putting them back together within single data model, and organizing the library according to the OAGIS modularity model. Remember that diagram in Part 2 that showed the "god awful" includes within the 2,5 model? All gone in 3.0!