PUBLIC COMMENT PERIOD - Encoding FIX using Google Protocol Buffers - Release Candidate 2

This proposal entails the use of GPB (Google Protocol Buffers) technology within FIX to produce fast and compact encodings of FIX messages. The use of GPB is one of the three major approaches to the efficient encoding of FIX that have been developed and are being proposed by the High Performance Working Group; the others being the use of a new, FIX-specific binary encoding called Simple Binary Encoding (SBE) and the use of Abstract Syntax Notation (ASN.1). The mapping to GPB defined in the proposed technical specification can be used for any FIX message (as defined in the FIX Unified Repository), and generates a set of definitions in the GPB notation (i.e., an GPB schema). The resulting GPB message definitions can then be encoded by applying standard encoding rules to produce efficient binary encodings.

The second release candidate documents for Encoding FIX using GPB can be found here.
https://www.fixtrading.org/standards/gpb

The proposed technical standard for Encoding FIX using GPB is following the technical standards review process described in the document found here.
https://www.fixtrading.org/fix-tech-std-lifecycle

This second release candidate now enters a public comment period in which public review and feedback is encouraged. The public comment period will run for a period of 90 days beginning on Wednesday the 16th of July, 2014.

Please post feedback, comments, and questions as replies to this discussion thread.

Are .proto files available in beta version somewhere?
It would be nice to populate Technical Proposal Appendix A (Usage Examples) to get a feel for the real thing.

As FIX continues to evolve rapidly, it would be challenging to maintain an up-to-date complete set of .proto files. Additionally, since it is expected that each implementation will utilize only a subset of the available FIX fields, the focus of the Google Protocol Buffers Encoding Subgroup has been on providing guidelines and examples for mapping FIX fields to protobuf, rather than delivering a static set of proto files.

There are two relevant documents which should be consulted:

  1. "Encoding FIX using Google Protocol Buffers - Release Candidate 2 -Technical Proposal"
    Contains complete instructions for an automated mapping of the entire FIX repository to .proto files.
    Appendix A contains a sample mapping of the IOI message.

  2. "Encoding FIX using Google Protocol Buffers - Release Candidate 2 - User Guide"
    Provides guidelines and recommendations for encoding FIX with Protobuf.
    Chapter 8 contains a sample .proto for the OrderCancelRequest message.

Above specifications are now posted on the FPL -> TechSpecs -> Presentation Layer -> Google Protocol Buffers page:
https://www.fixtrading.org/stanards/gpb

Please let us know if further assistance in mapping FIX to GPB is needed.