Don Mendelson

@david-gibbs-ig and @chrjohn, I agree that Orchestra-to-QuickFIX data dictionary and message code generation should be owned and maintained by the quickfixj project. The module under FIXTradingCommunity should be considered a...

The AppInfo element was intended for application-specific extensions, and firms are free to create their own. For convenience, I suggest that the fixml schema (and any others published by FIX)...

Message definitions in an Orchestra file are intended to represent semantics, not encoding-specific rules. However, StandardHeader and StandardTrailer are *only* relevant to FIX tag-value encoding, not to other protocols. On...

@francescoloconte I have to think about the syntax of your proposals, but totally agree with your summary. We already have mappings for datatypes to various field-level encodings in the mappedDatatype...

First, both ID and name of a referred object are authoritative and are constrained to be unique within its class. For example , the tag and name of a field...

I have no objection to normalizing capitalization.

@parker-berberian a PR would be welcome. I suggest a new unit test that asserts buffer length. io.fixprotocol.silverflash.util.BufferDumper may be helpful.

This type was retained from FIX Unified Repository, but I'm not sure that anyone uses it.

Unfortunately, the JSON standards simply say "A JSON text is a sequence of tokens formed from Unicode code points" and do not peg to a specific version of Unicode. BTW...

Current need: web APIs A major industry driver is REST API architecture with JSON payloads. I propose that we expand the scope of JSON Encoding RC2 to deliver standard API...