Task #2107
Feature #1764: Finalize dataoneTypes schema for public release
Types.Checksum: Representation of the checksum string
Status:
Closed
Priority:
Normal
Assignee:
Category:
Documentation
Target version:
Start date:
2011-12-07
Due date:
% Done:
100%
Milestone:
CCI-1.0.0
Product Version:
*
Story Points:
Sprint:
Description
Should there be something in the docs about how the checksum strings are represented? For instance, lower case hex, without any prefixes (like $ or 0x). If we don't specify case, maybe we should describe that checksum equality comparisons are case insensitive within DataONE.
On Python, when calculating an SHA-1 and asking for a "hexdigest", the result is string with 40 lower case hex characters, but if asking only for a "digest", it's 16 raw bytes.
History
#1 Updated by Matthew Jones over 12 years ago
- Status changed from New to Closed
- % Done changed from 0 to 100
Updated documentation to indicate that hex digests can be both lower and upper case, and checksum algorithms should deal with both.
