Adam Retter

@paulyoung84 The Integrity Check was always a mixed-concern :-/ It shouldn't really have been put into the CSV Validator, rather it should have been a separate tool entirely. I think...

@luketebbs IMHO I think supporting both is the wrong approach. This should strictly follow the CSV Language Specification - anything else is a bug and should be removed.

@PedroHFranco There is currently no facility for that. If you would like to contribute one though, it would be welcome.

@LauraDamianTNA Why revert?

@azelenov I see that you are correct, it is not explicit in the CSV Schema language that columns in the CSV Schema should be specified in the same order as...

A big omission from the CSV Schema spec is error conditions. Ideally there should be a code defined in the spec for each class of error, if you did that,...

@DavidUnderdown I think actually we just need this work which I did but hasn't been merged - https://github.com/digital-preservation/csv-validator/pull/156

It would seem like a good idea in the Java API to replace both the resultant `List` and `ProgressCallback` with a single callback mechanism, which is notified on each validation,...

@ctron I did actually try such an approach first but I could not get it to work, which is why we ended up with iterating over the properties.

@ctron I pushed a commit which I think addresses your comments.