"Applications that use SQLite as their application file-format should set the Application ID integer to a unique integer so that utilities such as file(1) can determine the specific file type rather than just reporting "SQLite3 Database". A list of assigned application IDs can be seen by consulting the magic.txt file in the SQLite source repository."
The sparsity, and age of the entries in magic.txt is a strong suggestion that some other mechanism should be used. The clues file(1) and "magic" suggest searching through unix (or unix-like) documentation, and that might tell you how to determine if an integer you picked is currently registered, and how to register it for yourself.
So, it appears the "correct" answer is that folk (ie: me) who want their application file formats to be recognized should send a patch for libmagic and file(1) -- and that the magic.txt file that is part of the SQLite codebase is really just a hint/pointer/clue of what to put in libmagic
Perhaps the SQLite codbase magic.txt file could be updated to point FNG like me to go elsewhere for submitting the patch (I assumed SQLite maintained their list and worked with up-stream to get into file(1) codebase)
The file(1) utility magic(5) information forRelease 3.X of Ian Darwin's implementation of the file utility (asdistributed by FreeBSD and most Linux distributions) is included in theBerkeley DB distribution. This magic.txt informationis correct for both big-endian and little-endian architectures. 041b061a72