-
Notifications
You must be signed in to change notification settings - Fork 6
CR 1.8 CHECKSUMENCODING
Leah Prescott edited this page May 29, 2014
·
1 revision
Defer
From the Board meeting notes:
Need encoding as well as CHECKSUM & CHECKSUMTYPE. Needed to verify CHECKSUM. Consider adding ENCODING attribute. Action Item: Adam will create a use case for consideration by the Board next time.
The issue is that the value encoded in the CHECKSUM attribute is usually a string of hex digits, but why? Couldn't it be octal, decimal, base64 or something else. Also, a string of hex digits is not case sensitive; so any matching / processing of the value needs to take this into account.
Requested by Adam Farquhar, Adam.Farquhar@bl.uk