TPEG RTM was intended as the ""one size fits all"" application. However, early implementations soon showed that the RTM structure was too broad to be used in navigation systems as a replacement for TMC. This first generation TPEG applications (TPEG generation 1, or "TPEG1") also provided only a binary encoding, having in some cases a separate specification for the mapping to an XML encoding. Consequently, a revision of both the general information modelling style and the design approach was done, moving TPEG towards more clearly defined and separated applications for specific use cases and a top-down data modelling approach. This second generation TPEG applications (TPEG generation 2, or TPEG2) is now specified with an UML model, from which automatically both a binary encoding and XML encoding are derived. A TPEG2 application specification includes both the binary and XML encodings as integral part of the specification.