In this the fourth part of the post I will continue to discuss the technical aspects of the IMF.
The Contents section, <imfContent> contains metadata pertaining to the ICN Object. The ICN Object can be in different file formats, not just CGM, however, CGM is the only format containing hotspot information. The <icnVariation> element provides the metadata for one particular format/notation, for example CGM. It is possible to have multiple <icnVariation>’s for additional formats, for example, a raster image, facilitating the multimedia object use in a different context.
The <icnInfoItemGroup> element provides the ability specific information about the ICN in text form.
There is also a required attribute, icnInfoItemType, see table below for details.
The <icnContents> is used to identify the metadata in the CGM file, for example, hotspots. Therefore, the interactive metadata can be revised externally of the CGM graphic. The example below shows the attributes of the individual hotspots, the ID and name, also the tooltip in the <icnObjectTitle>.
The final top-level element is <icnSupportingFiles> allowing the referencing of supporting information. This is achieved using standard S1000D referencing such as <dmRef> and <externalPubRef>. There are two types of supporting files, source and resource, it is difficult to differentiate between the two, perhaps only one was needed.
Using the <icnSupportingFiles> element also requires the use of an attribute, see below. However, the meaning, if required, will probably be project driven.
In conclusion, the Contents section should be easily populated if the multimedia object is anything other than a CGM with interactive hotspots.
In the final part, I will discuss the implementation of the IMF file and the dependencies dictating its use.
