Constantinos Leftheris

Edi Reader does not respect X12 advised control characters

18

In all known EDI formats there are default control characters these are documented in the default `EdiGrammar` presets. - `EdiGrammar.NewEdiFact()` - `EdiGrammar.NewX12()` - `EdiGrammar.NewTradacoms()` Now in the EdiFact and X12...

Because of the loose structure of the EDI format there is not definitive way to know the EDI file is not valid by checking for example the existence of the...

Revisit the formatting and the PICTURE syntax.

1

either fully support the cobol picture syntax as described [here](http://www-personal.ksu.edu/~mchaney/mn670/cobol4.htm) and [there](http://www.pgrocer.net/Cis12/cobol3.html), or maybe map to a dotnet friendly alternative like implementing the [IFormatProvider](https://msdn.microsoft.com/en-us/library/system.iformatprovider%28v=vs.110%29.aspx) and [ICustomFormatter](https://msdn.microsoft.com/en-us/library/system.icustomformatter%28v=vs.110%29.aspx) interfaces and using `string.Format`.

when a property type is nullable and the value is `null` then there must be a check to the Mandatory indicator upon the `EdiValueAttribute` in order to decide if we...

While I have used your implementation and it works like a charm I have a conceptual question maybe enhancement. In your [article](http://bitoftech.net/2014/10/27/json-web-token-asp-net-web-api-2-jwt-owin-authorization-server/) you are referring to audience as the "Relying...