The final part of the series provides some thoughts, conclusions, and ideas on a 2D graphics strategy. There is currently a lot of hype around 3D graphics and delivering this information to aid repair and maintenance activities. This is a great idea and a step forward for the maintenance of equipment. However, there is a huge amount of 2D graphics being created and legacy material that must be revised and published.
The requirement to maintain and publish 2D graphics is going to be critical for many years to come. Therefore, the requirement for a 2D archive and publishing format will be a necessity. The CGM format is usually implemented when a technical publications specification dictates it as a requirement. Also, there are very good reasons to use CGM, it is ideal to preserve legacy data because TIFF data can be included in the file. CGM can also contain metadata, for example, hotspots, ideal for interactive illustrations. The CGM format also has reliable data exchange capabilities, resulting in excellent interoperability.
The SVG format does not have the data exchange credentials of CGM. SVG was primarily designed to view vector graphics in a web browser. The ability to reopen the SVG file even in the software that exported it can be problematic. SVG can also include a raster image, although not a TIFF, and hotspot information providing interactivity. The big advantages of SVG over CGM, the XML formatting and native graphics viewing in a web browser.
The viewing of a CGM graphic in web browser requires a plug-in technology, e.g. ActiveX. The solution was viable until the browser developers decided to abandon support for the plug-in technology. At this point, the search for an alternative format was high on the agenda. A raster format is an easy choice, but quality can be an issue and the addition of hotspots will not be seamless.
Therefore, what format should we select? The short answer is both formats are viable. Utilizing the Larson VizEx View HTML5 technology you can still use CGM files in a web browser, without a plug-in. SVG can also be used, however, consider the interoperability issues, the best advice, only use the SVG for display purposes. The other consideration with SVG, you will need to develop an SVG viewing environment for the web browser, especially if you require the same functions available in a plug-in technology. In conclusion, evaluate and review the best strategy, and consider carefully before implementing a new graphics format.
