How is the {n,*} syntax processed by PRONOM?

The document http://www.nationalarchives.gov.uk/aboutapps/fileformat/pdf/automatic_format_identification.pdf defines the syntax for binary PRONOM signatures.

In it, it says you can specify wildcard matches as follows:

{m-n}: wildcard matching between m-n bytes inclusive, where m and n are integers or ‘*’.

e.g.: 0x03 {1-2} 4D would match 0x03 3C 4D or 0x03 3C 88 4D. 

e.g.: 0x03 {2-*} 4D would match 0x03 3C 88 4D or 0x03 3C 88 3F 4D

Are there actually any signatures that support the second form using the * wildcard?

One way it could work, using the example given above, gives two SubSequences:

0x03 {2-*} 4D

becomes:

SubSequence 1: 0x03 ?? ??
SubSequence 2: 0x4D

I’ve added two ?? bytes - since we’re saying there has to be a minimum gap of two between the two SubSequences.

Is this how PRONOM processes such syntax? Is there an example of one in PRONOM currently?

[nishihatapalmer]

Awesome! I googled around bit didn’t find that.

On Fri, 6 Sep 2019, 18:16 Ross Spencer, [e-mail] wrote:

PRONOM exports can all be found here https://zenodo.org/record/3269467#.XXKTpXUzY5k in their full and native XML @nishihatapalmer https://github.com/nishihatapalmer. I was researching your problem earlier and it was easy enough to search across files in a text editor for the results you need.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/digital-preservation/droid/issues/274?email_source=notifications&email_token=ABBY4JB55FDQAQZPPY474ODQIKF6XA5CNFSM4IUI6Z22YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD6DPIZA#issuecomment-528938084, or mute the thread https://github.com/notifications/unsubscribe-auth/ABBY4JEYH6A2DB7NCLX6JL3QIKF6XANCNFSM4IUI6Z2Q .

[ross-spencer]

PRONOM exports can all be found here in their full and native XML @nishihatapalmer. I was researching your problem earlier and it was easy enough to search across files in a text editor for the results you need.