fix-simple-binary-encoding
fix-simple-binary-encoding copied to clipboard
FIXTradingCommunity
A FIX standard for binary message encoding
I have a problem using the Visual Studio for CME iLink3 SBE schema editing. After I've added `semanticAttributes` to the `simpleDataType`, `memberDataType` and `compositeDataType` elements, the VS started to complain...
Posted on FIX website (https://forum.fixtrading.org/t/public-comment-period-simple-binary-encoding-sbe-v2-0-rc1/14182/2) by user sorabai (Sorabain de Lioncourt): Pretty minor, but noticed an error in “standard encoding of MonthYear” … a uint16 could never contain the value...
I'd like to discuss some possible ways to add extensibility to SBE schema. SBE schema has its main purpose to define the protocol "on-the-wire". In addition it contains some additional...
Chapter about message schema explains the attributes of various elements. It seems that copy/paste errors were made that lead to the wrong terms being used. Please review the following items:...
Chapter on message schema uses backticks to highlight attribute names , e.g. "... `semanticType` attribute ..." just like element names. Other chapters do not. Suggest to make consistent one way...
Proposal explained [here](https://github.com/real-logic/simple-binary-encoding/issues/831)
While correct, the schema extension example could be misinterpreted due to vocabulary used. For example, a new reader who missed the implicit zero based versioning, could misunderstand how version 1...
Each FIX datatype is already mapped to a field encoding in SBE. To aid mapping to other protocols, each SBE encoding should also be mapped to a semantic type as...
Since unit is not constant, it should be on the wire. See:  The nanoseconds should be there  (nanoseconds = 9) Unless unit time is constant.
Metadata
Owner
Metadata
A FIX standard for binary message encoding