List 162: Resource version feature type

ValueDescriptionNotesIssue numberModified in Issue
01File formatResource Version Feature Value carries a code from List 1781011
02Image height in pixelsResource Version Feature Value carries an integer1011
03Image width in pixelsResource Version Feature Value carries an integer1011
04FilenameResource 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>1144
05Approximate download file size in megabytesResource 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)1117
06MD5 hash valueMD5 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 retrieved12
07Exact download file size in bytesResource Version Feature Value carries a integer number only (eg 1831023)17
08SHA-256 hash valueSHA-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 retrieved28
09ISCCInternational 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 omitted5062
10Previous 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>66