Skip to content

Fixes some typos in schema extension mechanism #134

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Dec 13, 2020
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions v2-0-RC3/doc/05SchemaExtensionMechanism.md
Original file line number Diff line number Diff line change
Expand Up @@ -106,7 +106,7 @@ encoding.

Message headers and repeating group dimensions carry a count of the number of repeating groups and a count of variable-length data fields on the wire. This supports a walk by a decoder of all the elements of a message, even when the decoder was built with an older version of a schema. As for added fixed-length fields, new repeating groups cannot be interpreted by the decoder, but it still can process the ones it knows, and it can correctly reach the end of a message.

## Comaptibility strategy
## Compatibility strategy

*This suggested strategy is non-normative.*

Expand Down Expand Up @@ -153,7 +153,7 @@ Second version - a new message is added
<field name="Field1" id="1" type="int8" semanticType="int"/>
</message>

<!-- New message added in this version-->
<!-- New message added in this version -->
<message name="FIX Binary Message2" id="2" blockLength="4"
sinceVersion="1">
<field name="Field2" id="2" type="int16" semanticType="int"/>
Expand Down