Work on the guidance on creating and submitting new PRONOM signatures

[anjackson]

e.g.

• Scan all these unknown files and generate initial signatures, using TRiD-ish logic, but generating PRONOM-compatible signatures?
• Look at practicalities of using WikiData as a format ID signature source?
• Create walkthrough documentation for generating submissions for PRONOM, especially based on a local collection?
• Document how to test or use a new signature in a Preservica instance?

There's rather a lot of existing good work here...

• https://github.com/digital-preservation/PRONOM_Research of course, but especially https://github.com/digital-preservation/PRONOM_Research/blob/main/Resources/PRONOM%20Starter%20Guide%20(1).pdf which looks great but seems a bit hidden away?
• https://ffdev.info/ (src https://github.com/exponential-decay/signature-development-utility)
• Existing Wikidata support https://github.com/richardlehane/siegfried/wiki/Wikidata-identifier
• Custom Wikibase is possible https://openpreservation.org/blogs/using-a-custom-wikibase-with-siegfried/
• Roy https://github.com/richardlehane/siegfried/wiki/Building-a-signature-file-with-ROY
• Learn from ClamAV guidance? https://docs.clamav.net/manual/Signatures.html

I'm particularly interested in whether this can be made easier be building for the browser

• https://siegfried-js.glitch.me/
• Extend workflows to support WASM releases? https://github.com/richardlehane/siegfried/tree/main/.github/workflows
• Also build WASM version of the signature development utility?

But also whether some central test corpus would be useful?

• Misidentification / FIDO vs. Siegfried richardlehane/siegfried#76 (comment) interesting case