01 |
File format |
Resource Version Feature Value carries a code from List 178 |
02 |
Image height in pixels |
Resource Version Feature Value carries an integer |
03 |
Image width in pixels |
Resource Version Feature Value carries an integer |
04 |
Filename |
Resource Version Feature Value carries the filename of the supporting resource, necessary only when it is different from the last part of the path provided in <ResourceLink> |
05 |
Approximate download file size in megabytes |
Resource Version Feature Value carries a decimal number only, suggested no more than 2 or 3 significant digits (eg 1.7, not 1.7462 or 1.75MB) |
06 |
MD5 hash value |
MD5 hash value of the resource file. <ResourceVersionFeatureValue> should contain the 128-bit digest value (as 32 hexadecimal digits). Can be used as a cryptographic check on the integrity of a resource after it has been retrieved |
07 |
Exact download file size in bytes |
Resource Version Feature Value carries a integer number only (eg 1831023) |
08 |
SHA-256 hash value |
SHA-256 hash value of the resource file. <ResourceVersionFeatureValue> should contain the 256-bit digest value (as 64 hexadecimal digits). Can be used as a cryptographic check on the integrity of a resource after it has been retrieved |
09 |
ISCC |
International Standard Content Code, a ‘similarity hash’ derived algorithmically from the resource content itself (see https://iscc.codes). <IDValue> is the ISCC-CODE generated from a digital manifestation of the work, as a variable-length case-insensitive alphanumeric string (or 55 characters including three hyphens if using ISCC v1.0, but this is deprecated). Note alphabetic characters in v1.x ISCCs use Base32 encoding and are conventionally upper case. The ‘ISCC:’ prefix is omitted |
10 |
Previous filename |
<ResourceVersionFeatureValue> carries the previous filename of the supporting resource, necessary only when it is different from the last part of the path provided in <ResourceLink> and from the filename provided using <ResourceVersionFeatureType> code 04, and when the data sender suggests the recipient delete this old file. Note that the ‘trigger’ to update the resource and delete the old file is provided by the Resource version’s <ContentDate> |