Skip to content
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

Improve validation - add charset constraints #8

Open
mbeckerle opened this issue May 27, 2020 · 4 comments
Open

Improve validation - add charset constraints #8

mbeckerle opened this issue May 27, 2020 · 4 comments

Comments

@mbeckerle
Copy link
Member

Various NITF elements are supposed to have specific characters only. E.g,, are not allowed to have any ascii chars but only 0x20-0x7F only for some elements (e.g., excludes all control chars, line-endings, etc.)

These requirements can be expressed using pattern facets, but are missing from the NITF schema.

@mbeckerle
Copy link
Member Author

Additionally, range checks on numbers are not expressed even though they can be captured using facets.

@bradh
Copy link

bradh commented Nov 9, 2022

Note that the rules changed between MIL-STD-2500C CN2 and the new Joint BIIF Profile.

@mbeckerle
Copy link
Member Author

Note that the rules changed between MIL-STD-2500C CN2 and the new Joint BIIF Profile.

Do you think it will be needed to handle both, or are the new rules a tightening to where the contraints should have been all along?

@bradh
Copy link

bradh commented Nov 9, 2022

The definition of BCS, ECS, etc has not changed. The difference is that ECS-A is now allowed in places where previously only BCS-A was valid.

The basic concept is that a union of NITF and NSIF valid ranges went into JBP. So everything that was valid is still valid, but things that were not valid might now be valid..

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants