Suggested output improvements (jpylyzer 2.x)

[bitsgalore]

Dev Effort

2D

Description

These are some ideas for future improvements of jpylyzer's output:

• Harmonize behavior when using -wrapper flag and default (e.g. wrap by default; this would mean one additional level of nesting when only 1 image is analysed) Better: wrap by default, deprecate -wrapper flag and keep it only for backward compatibility (i.e. it should only take effect if --legacyout is activated, and ignored otherwise)
• In that case toolInfo could be moved one level higher in the output hierarchy (no need to repeat this for each analysed image)
• Make validation outcome more generic. E.g., change:

<isValidJP2>True</isValidJP2>

into this:

<isValid format="jp2">True</isValid>

(This would allow future extensions to e.g. JPX)

These changes would all break current deployments, but might be worth considering for next major version (2.0), whenever that would come up.

UPDATE

See also: Proposed jpylyzer output format changes

[bitsgalore]

See also comments/suggestion by @tledoux here. Implemented by https://github.com/openpreserve/jpylyzer/commit/eca9824d9acef1c560fa447cd3a21b5563e887c4 and https://github.com/openpreserve/jpylyzer/commit/25a913c131e71883d07283435baf2c38a1a7e6d2.