search

exponential-decay / skeleton-test-suite-generator

DROID Skeleton Test Suite Generator (skeleton-test-suite-generator): Tool for the automated generation of digital objects based on the digital signatures documented in the PRONOM database maintained by The National Archives, UK. The skeleton-test-suite-generator serves to fill the gap that exists whereby the community requires a corpus of digital objects for the validation and evaluation of format identification tools and techniques. The tool should be used to complement a methodology whereby skeleton files are also generated manually by signature developers. The tool takes a signature specified for a digital object in PRONOM and constructs a digital object that will match its footprint. For more information, see the README.md associated with the project...
zlib License
8 stars 2 forks source link

x-fmt/412 does not seem to be written correctly - v84 (JAR) #4

Closed ross-spencer closed 7 years ago

ross-spencer commented 8 years ago

Possibility that variable second sequence is being written somewhere between the wildcard of the first...

ross-spencer commented 7 years ago

This is not an issue in DROID4 and so suggesting it's not a bug and rather, it is related to the way both DROID and SF handle containers. (May test at some point in SF without containers.)

richardlehane commented 7 years ago

image

richardlehane commented 7 years ago

image

richardlehane commented 7 years ago

... if you build your signatures with roy build -doubleup you'll get the expected match.

Where PRONOM defines both container and byte signatures for a format, the default signature file excludes the byte signatures on the basis that the container signatures should give a more accurate result and if they haven't matched there is likely an issue (& I think you raised an issue in the past where including these extraneous byte signatures was causing mismatches).

You can override this behaviour and force inclusion of the additional byte signatures with the -doubleup flag. It is necessary for this skeleton file because of course the container signature doesn't match it.

p.s. great to see all this weekend work you're doing on the suite Ross :)

ross-spencer commented 7 years ago

Great stuff! Thanks Richard.

Yep - just wanted to close these out. Think the structure is looking a little better now too now I'm using classes to store the byte structures.

I need to chat to PRONOM about sequences in the container signature for StarOffice I can't understand - once I've done that I'll release a suite for each of the legacy files and then be up to date again finally.

On 23 Jul 2017, at 13:36, Richard Lehane notifications@github.com wrote:

— You are receiving this because you modified the open/close state. Reply to this email directly, view it on GitHub, or mute the thread.