I got a request for my ebook, JHOVE Tips for Developers. It’s no longer for sale on Smashwords, since I haven’t updated it since 2012, but if anyone wants it, you can download JHOVE Tips for Developers from this site.
- Gary McGath
This blog is no longer available at madfileformatscience.garymcgath.com but will remain available at fileformats.wordpress.com. The RSS feed is fileformats.wordpress.com/rss. Please update your bookmarks as necessary. - Follow Mad File Format Science on WordPress.com
-
Join 142 other subscribers
-
Recent Posts
How to approach the file format validation problem
For years I wrote most of the code for JHOVE. With each format, I wrote tests for whether a file is “well-formed” and “valid.” With most formats, I never knew exactly what these terms meant. They come from XML, where they have clear meanings. A well-formed XML file has correct syntax. Angle brackets and quote marks match. Closing tags match opening tags. A valid file is well-formed and follows its schema. A file can be well-formed but not valid, but it can’t be valid without being well-formed.
With most other formats, there’s no definition of these terms. JHOVE applies them anyway. (I wrote the code, but I didn’t design JHOVE’s architecture. Not my fault.) I approached them by treating “well-formed” as meaning syntactically correct, and “valid” as meaning semantically correct. Drawing the line wasn’t always easy. If a required date field is missing, is the file not well-formed or just not valid? What if the date is supposed to be in ISO 8601 format but isn’t? How much does it matter?
Continue reading →
Comments Off on How to approach the file format validation problem
Posted in commentary
Tagged archiving, JHOVE, preservation, standards