fix-simple-binary-encoding
fix-simple-binary-encoding copied to clipboard
FIXTradingCommunity
A FIX standard for binary message encoding
Hi, in [Euronext MDG schema](https://connect2.euronext.com/sites/default/files/it-documentation/mdg_binary_sbe_input_316.xml) there are bitset (``) and enum (``) fields marked as `optional`, is it legal? My understanding is that `field` with a non-built-in encoding always inherits...
1. https://github.com/FIXTradingCommunity/fix-simple-binary-encoding/blob/master/v1-0-STANDARD/doc/02FieldEncoding.md#general-1 says that > `nullValue` is mutually exclusive with `presence = required/constant`. > `presence=requires` is mutually exclusive with `nullValue` My understanding of that phrase is that having a `nullValue`...
Extension mechanism is based on required `blockLength` and optional `numGroups` and `numVarDataFields`. The latter two tell how many groups/var-data fields we have but they tell nothing about their dimension types...
Currently, `offset` and `message.blockLength` are specified as `unsignedInt` (32-bit) while `type.length` is `nonNegativeInteger` which is by spec "unbounded" which I guess can be treated as "at least 64-bit". In this...
[Here](https://github.com/FIXTradingCommunity/fix-simple-binary-encoding/blob/master/v1-0-STANDARD/doc/02FieldEncoding.md#variable-length-string-encoding), it says: > On the wire, length immediately precedes the data. Which is 100% logical and correct. What bothers me is the next part [Encoding specification](https://github.com/FIXTradingCommunity/fix-simple-binary-encoding/blob/master/v1-0-STANDARD/doc/02FieldEncoding.md#encoding-specifications-for-variable-length-string). It says: >...
Although this was allowed in SBE v1.0, the current schema does not allow semanticType attribute on encoding types. This would be useful to map `` to a FIX datatype. For...
An SBE message schema should have a standardized way to tell about the artifact--who issued it, when it was published, any copyright or license information, and so on. Fortunately, there...
Monetary amounts and prices are mostly *exact decimal* numbers. It is well documented that monetary amounts are poorly represented by *binary* single- and double-precision floating-point numbers that programmers are familiar...
Looks like there is an invalid character (copyright) in the [sbe-2.0rc3.xsd ](https://github.com/FIXTradingCommunity/fix-simple-binary-encoding/blob/20df0aa1016133949b469d9976ff1ff07ad3e30c/v2-0-RC3/resources/xsd/sbe-2.0rc3.xsd#L8) file. Both `Visual Studio` and `XML (Red Hat) VS Studio Code plugin` application complain. I think `©` should...
I am making this proposal to get feedback from the community... SBE version 1.0 is a FIX final technical standard (as well as a forthcoming ISO standard), and therefore cannot...
Metadata
Owner
Metadata
A FIX standard for binary message encoding