You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The image types in NITF are a small set - no compression, jpeg, jpeg2000, etc.
Users may only have DFDL schemas for some of those. So the NITF schema shouldn't require them to be present. Instead, a set of dummy definitions for them should be placed in src/test/resources so that NITF can be used and tested in isolation, but in a "real" use, the classpath would hold the real schemas for the image types.
The image types in NITF are a small set - no compression, jpeg, jpeg2000, etc.
Users may only have DFDL schemas for some of those. So the NITF schema shouldn't require them to be present. Instead, a set of dummy definitions for them should be placed in src/test/resources so that NITF can be used and tested in isolation, but in a "real" use, the classpath would hold the real schemas for the image types.
This is similar to the message_size element that was done in mil-std-2045 DFDL schema. https://github.com/DFDLSchemas/mil-std-2045
The text was updated successfully, but these errors were encountered: