In the third part of the post, I will continue to discuss the technical aspects of the IMF.
The Status section includes six elements at the highest level, three of the elements are flat.
Security is a flat element and is reasonably straightforward, the classification codes come directly from the S1000D specification. The codes should reflect the associated Data Module. The same will be true of the other flat elements, Responsible Partner Company, and Enterprise Name.
The Data Restrictions element is broken down into two main elements, Instructions and Info. The content of these elements will again reflect the overall project and the associated Data Module.
The <restrictionInfo> element is all about copyright, so should also have mainly boilerplate content.
The BREX reference will be an organization or project specific business rules, the elements are standard S1000D, <dmRef> etc.
The quality assurance element is straightforward, this again has standard S1000D attributes, and should be a flow down from the associated DM.
In summary, there is a high level of effort creating the IMF data file, therefore what are the benefits, I hope to answer this question as the series progresses. Back to Part 3, the Status section largely consists of Boiler Plate content, therefore, a template will be the ideal strategy. In Part 4 we will discuss the content section, and the software solutions required to enable the easy creation of the IMF.
