| 27 February 1996 | Rail Industry Forum |
| Forward to the Electronic Parts Catalog Exchange Standard |
Rail Industry parts catalog information consists of Text; Data (parts information); Images (raster representations of drawings or pictures); and Drawings (vector formatted drawings). Each of these information "objects" has special treatment in the EPCES as follows:
Standard Generalized Markup Language (SGML) is utilized by the EPCES to encode text, data and provide for the linking of information elements. SGML, an International Standard, provides an unambiguous syntax for describing whatever a user chooses to identify within a document.An SGML DTD provides the structure that categorizes all information in an SGML encoded document. A tighter DTD structure yields a more reliable information exchange by reducing ambiguity in encoding documents. In the course of defining the EPCES, it was agreed to develop a tightly structured DTD by applying the following guidelines:
Focus markup (define data elements) on the content of traditional OEM parts catalogs (as opposed to Industrial Supply catalogs and maintenance manuals).
Provide a structure that accommodates a minimal use of text - typical of over 80% of the Rail Industry parts catalogs reviewed in Phase II.
Pattern the best practices of other Industry DTD's when applicable to the EPCES.
The EPCES specifies ATA's Tagged Image File Format (TIFF) 5.0 profile with CCITT Group IV compression for the exchange of bi-tonal images. ATA's TIFF specification is a subset of TIFF 5.0. Further, ATA's TIFF specification is a subset of TIFF 6.0. Therefore both TIFF 5.0 and 6.0 products support the EPCES. However, as EPCES is implementing a subset of TIFF, TIFF compliant products may generate non-EPCES compliant graphics.The initial release of EPCES does not specify the encoding of grayscale or color Images. There are noted difficulties with TIFF 6.0 compression specifications.
The EPCES specifies ATA's profile for Computer Graphics Metafile (CGM) Version 3 for the exchange of vector information.There are two exceptions to the Rail Industry's adaptation of ATA's profile for CGM:
First, the EPCES prohibits the use of drawing layers. Although layered drawings are potentially useful in an EPC, the lack of definition of the meaning of layers in the ATA specification allows for ambiguity and hence, an inability to exchange layering information without negotiation of layer definitions in every exchange.
Secondly, the EPCES is not allowing the use of "any" fonts beyond the baseline of fonts listed in the ATA specification.
RIF requirements for the EPCES are that users have "point and click" drill down, from major component to minor component information. When an individual part is visually identified, users must have the capability to navigate to that specific part's data. This drill down capability requires that drawings, images, text and data (parts information) be logically interconnected or "linked". SGML encoding and an SGML application, HyTime, support the exchange of these navigational links.
The RIF-EPC DTD, by means of it's hierarchical and by ID/IDREF cross referencing allows linking an information element (drawing, text, data) to another information element, and thus provides drill down capability.
Essential to an EPC application is the capability to select a graphical "call-out" resulting in a link to information specific to that "call-out". EPCES defines a coordinate system utilizing HyTime tools specifically for (and restricted to) the linking of graphics "call-outs" to other EPCES information.
In addition to being compliant to the ISO 8879-1986 specification, EPCES SGML tools must have HyTime capabilities. There is an emerging base of SGML tools with HyTime, but as HyTime implementations are relatively new it will be important to specifically request this capability.