In a relatively recent signature update, the fmt/44 signature was updated to in allow some data after the stated EOF marker (ff d9).

In the case that started this off, a number of fmt/44 jpg files were found that had a couple of bytes after what DROID looks for as an absolute EOF.

I had a look into the specs for jpg, trying to unravel this story - were the extra bytes useful to someone? were we missing something by ignoring these bytes?

This will be my shortest blog post ever. Following up on my previous blog post on a prototype JP2 validator and properties extractor (jpylyzer), there is now a comprehensive User Manual of the tool. Just follow the link below:

I'm really pleased to be writing a quick blog post on a new digital preservation project we'll be running over the next couple of years. After running 3 AQuA style hackathon/mashups last year I felt we'd managed to develop a useful formula for solving digital preservation problems and beginning to foster a bit more of an active practitioner community.