|
ISO 28560-3:2011 Clarification |
|
Authors : |
|
Identifier: http://biblstandard.dk/rfid/docs/clarification_28560-3.htm
|
|
Status : For information Bemark : Valid for ISO 28560-3:2011, not for ISO
28560-3:2014 |
|
Published by ISO/TC46/SC4/WG11 RFID in Libraries Information and documentation, Technical
interoperability Contact : rfid@bs.dk
|
|
First version: 4 November 2011 |
This document provides clarification relevant to ISO 28560 Part 3. Some references are made to ISO 28560-1 or
its associated clarification document. The headings (below) are referencing
entries in table 1 Data elements in ISO 28560-3.
Clause 6, Table 1, entry 1 –
Primary item identifier
ISO 28560-3
tells that this data element can be encoded in two different data blocks,
either basic block or library extension block, and specifies how to do it. For information
a supplementary description is given below. See also Annex B for encoding
examples.
The basic
block is designed with fixed length fields. The encoding therefore depends on
the length of the data element. If the
primary item identifier is less
than or equal to 16 bytes (octets), it shall always be encoded in the basic
block as specified in table 2 (Usage and layout of the basic block).
Otherwise byte position
If the RFID tag
is limited to 32 bytes, it can only
contain a truncated basic block, see table 3 (Usage and layout of the truncated
basic block). In this case only primary item identifiers less than or equal to 16 bytes (octets) can
be encoded on the tag.
Clause 6, Table 1, entry 3 – Owner institution (ISIL)
ISO 28560-3
tells that this data element can be encoded in two different data blocks, either
basic block or library extension block, and specifies how to do it. For
information purpose a supplementary description and a few examples are given
below. See also Annex B for encoding examples.
The basic
block is designed with fixed length fields. The encoding therefore depends on
the length of the data element. If the ISIL prefix is one or two bytes (octets)
and the unit identifier is less than or equal to 11 bytes (octets), the ISIL
shall always be encoded in the basic block as specified in table 2 (Usage and
layout of the basic block). In this case the string shall be formed as the
concatenation of the prefix and the unit identifier. If the prefix is only one
character, a blank (U+0020) is added between the prefix and the unit
identifier.
Otherwise byte position
If the RFID tag
is limited to 32 bytes, it can only
contain a truncated basic block, see table 3 (Usage and layout of the truncated
basic block). In this case only ISIL identifiers with a one or two character
prefix and a unit identifier less than or equal to 9 bytes (octets) can be
encoded on the tag.
Note:
ISIL is defined in ISO 15511. It is a variable length identifier that
shall consist of a maximum of 16 characters, using digits (Arabic numerals 0 to
9), or letters from the 26-character Roman alphabet (excluding the use of any
diacritical marks) and the following special marks solidus (/), hyphen (-) and
colon (:). Each ISIL identifier shall be unique in accordance with the
repertoire of characters specified in ISO/IEC 10646-1 without regard to case.
For each character and special mark in this limited character
repertoire the utf-8 encoding (which is used for encoding of strings in ISO
28560-3) occupies 1 byte (also called octet).
Examples:
The ISIL identifier "O-FITHE" is encoded in the basic block as
the string "O FITHE" (note: the prefix "O" is a short ISIL
form of the non-country code "OCLC"; the hyphen is omitted, but a
blank is added because the prefix is only one character.)
The ISIL identifier "DK-820010" is encoded in the basic block
as "DK820010".
The hypothetic ISIL identifier "WXYZ-ABCD" is encoded in the
library extension block as "WXYZ-ABCD".
The hypothetic ISIL identifier "AB-DEFGHIJKLMNOPQRS" is
encoded in the library extension block as "AB-DEFGHIJKLMNOPQRS".
Clause
6, Table 1, entry 5 – Type of
usage
ISO 28560-3 only state how to encode main qualifier of
usage code (ref. ISO 28560-1, Annex C).
In a later update of these clarifications will follow
guidelines how to encode the sub-qualifier. The editors of ISO 28560-3 are in
dialogue with vendors to ensure an optimal solution. If you have an actual
need, please contact the convenor of ISO TC46/SC4/WG11, email rfid@bs.dk
Clause
6, Table 1, entry 19 – Media
format (other)
The values
of this data element are not specified in ISO 28560-1, but are included in the
clarification document for ISO 28560-1, section 4.2.19.
Clause
6, Table 1, entry 20 – Supply
chain stage
ISO 28560-1
defines the code points as decimal values.
The clarification note for ISO 28560-1 4.2.20 adds the hexadecimal
values. In ISO 28560-3 the values shall be encoded as an 8-bit unsigned integer
as specified in Table 1 (Data elements) and table 6 (Usage and layout of the
acquisition extension block).
To achieve
interoperability in host systems, ISO 28560-2 and ISO 28560-3 require a common
basis for input to their respective encoding processes and common output from
their decoding processes. Each
input/output value is required as an 8-bit unsigned integer.
Clause
6, Table 1, entry 23 –
Alternative owner institution
ISO 28560-3
tells that this data element can be encoded in two different data blocks,
either basic block or library extension block, and specifies how to do it. For
information a supplementary description is given below. See also Annex B for
encoding examples.
The basic
block is designed with fixed length fields. The encoding therefore depends on
the length of the data element. If alternative
owner institution is less than or
equal to 10 bytes (octets), it shall always be encoded in the basic block as
specified in table 2 (Usage and layout of the basic block). In this case bytes
21 and 22 are undefined and byte 23 is either 02HEX or 03HEX, where 02HEX indicates a national standardized code not
part of ISIL and 03HEX
an institution code that is neither part of ISIL nor a national standard.
Otherwise byte position
If the RFID tag
is limited to 32 bytes, it can only
contain a truncated basic block, see table 3 (Usage and layout of the truncated
basic block). In this case only alternative owner institution less than or equal to 8 bytes (octets) can
be encoded on the tag.
Annex
B, Encoding examples (informative), Table B.1
There is an
error in the last row of table B.1. The length of the field is specified to be
13 bytes, but can only be 11 bytes (because the block is limited to 32 bytes).
The correct version of table B.1 shall be:
Table 1 — Example 1, data elements to be
encoded
|
Content |
Length |
Value |
Encoding
(hex value) |
|
2.
Content parameter |
4 bit |
1 |
1 |
|
5. Type
of usage |
4 bit |
1 (item
for circulation) |
1 |
|
4. Set
information |
2 bytes |
Item 1
of 1 |
0101 |
|
1.
Primary item identifier |
16
bytes |
1000000056 |
31303030303030303536000000000000 |
|
CRC |
2 bytes |
|
98A4 |
|
3.
Owner institution (ISIL) |
11 bytes |
DK-718500 |
444B373138353030000000 |