Added a new specification for 850 document for version 5010.… #1
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
… The only real difference between the 4010 version is the addition of an MTX element allowed in an N9 Loop.
|
Guys, I needed a reference for our security people of who is using this Project? |
naiduv
approved these changes
May 29, 2019
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
… The only real difference between the new specification and the 4010 version is the addition of an MTX element allowed in an N9 Loop. There are likely other real differences between the 4010 version and the 5010 version, but I don't know where to find a publication of the full standard. This change came about as a result of testing with a major US retailer that used the MTX element in their implementation. These changes allowed the document to parse correctly where the 4010 specification did not.