SIST ISO 28560-3:2025

SLOVENSKI STANDARD
01-junij-2025
Nadomešča:
SIST ISO 28560-3:2024
Informatika in dokumentacija - RFID v knjižnicah - 3. del: Kodiranje z
nespremenljivo dolžino
Information and documentation — RFID in libraries — Part 3: Fixed length encoding
Information et documentation — RFID dans les bibliothèques — Partie 3: Encodage de
longueur fixe
Ta slovenski standard je istoveten z: ISO 28560-3:2024
ICS:
35.040.50 Tehnike za samodejno Automatic identification and
razpoznavanje in zajem data capture techniques
podatkov
35.240.30 Uporabniške rešitve IT v IT applications in information,
informatiki, dokumentiranju in documentation and
založništvu publishing
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.

International
Standard
ISO 28560-3
Fourth edition
Information and documentation —
2024-10
RFID in libraries —
Part 3:
Fixed length encoding
Information et documentation — RFID dans les bibliothèques —
Partie 3: Encodage de longueur fixe
Reference number
© ISO 2024
All rights reserved. Unless otherwise specified, or required in the context of its implementation, no part of this publication may
be reproduced or utilized otherwise in any form or by any means, electronic or mechanical, including photocopying, or posting on
the internet or an intranet, without prior written permission. Permission can be requested from either ISO at the address below
or ISO’s member body in the country of the requester.
ISO copyright office
CP 401 • Ch. de Blandonnet 8
CH-1214 Vernier, Geneva
Phone: +41 22 749 01 11
Email: copyright@iso.org
Website: www.iso.org
Published in Switzerland
ii
Contents Page
Foreword .v
Introduction .vi
1 Scope . 1
2 Normative references . 1
3 Terms and definitions . 1
4 Requirements . 3
4.1 Data elements .3
4.2 RFID air interface .3
4.2.1 Air interface conformance .3
4.2.2 Tag performance .3
4.3 Data protocol .3
5 General encoding rules . 3
5.1 Distinguishing from other applications and encodings .3
5.2 Writing/reading direction .4
5.3 Memory area layout .4
5.3.1 Specifications .4
5.3.2 Layout for tags greater than 32 bytes .4
5.3.3 Layout for 32-byte tags .4
5.4 Strings and integers .4
5.4.1 String encoding .4
5.4.2 Integer encoding .5
5.5 Writing the tag .5
5.5.1 Cyclic redundancy check (CRC) .5
5.5.2 Unused space .5
5.5.3 End of tag.5
5.6 Reading optimization .5
5.7 Profiling .5
5.8 Locking .5
6 Data elements . 5
7 Data blocks . 9
7.1 Types of data blocks .9
7.2 Basic block .9
7.3 Special blocks.11
7.4 Structured extension blocks .11
7.4.1 Usage of structured extension blocks .11
7.4.2 Format of structured extension blocks . 12
7.4.3 Length . 12
7.4.4 Data block ID . 12
7.4.5 Checksum . 12
7.5 Library extension block . 13
7.6 Acquisition extension block . 13
7.7 Library supplement block .14
7.8 Title block .14
7.9 ILL block . 15
7.10 Unstructured extension blocks . 15
7.10.1 Usage of unstructured extension blocks . 15
7.10.2 Format of unstructured extension blocks .16
8 Miscellaneous .16
8.1 Migration .16
Annex A (informative) Information about ISO 28560 RFID in libraries . 17
Annex B (informative) Encoding examples .18

iii
Annex C (informative) Cyclic redundancy check (CRC) .22
Annex D (informative) Reading optimization .23
Annex E (informative) Guidelines for regional profiling .24
Bibliography .25

iv
Foreword
ISO (the International Organization for Standardization) is a worldwide federation of national standards
bodies (ISO member bodies). The work of preparing International Standards is normally carried out through
ISO technical committees. Each member body interested in a subject for which a technical committee
has been established has the right to be represented on that committee. International organizations,
governmental and non-governmental, in liaison with ISO, also take part in the work. ISO collaborates closely
with the International Electrotechnical Commission (IEC) on all matters of electrotechnical standardization.
The procedures used to develop this document and those intended for its further maintenance are described
in the ISO/IEC Directives, Part 1. In particular, the different approval criteria needed for the different types
of ISO document should be noted. This document was drafted in accordance with the editorial rules of the
ISO/IEC Directives, Part 2 (see www.iso.org/directives).
ISO draws attention to the possibility that the implementation of this document may involve the use of (a)
patent(s). ISO takes no position concerning the evidence, validity or applicability of any claimed patent
rights in respect thereof. As of the date of publication of this document, ISO had not received notice of (a)
patent(s) which may be required to implement this document. However, implementers are cautioned that
this may not represent the latest information, which may be obtained from the patent database available at
www.iso.org/patents. ISO shall not be held responsible for identifying any or all such patent rights.
Any trade name used in this document is information given for the convenience of users and does not
constitute an endorsement.
For an explanation of the voluntary nature of standards, the meaning of ISO specific terms and expressions
related to conformity assessment, as well as information about ISO's adherence to the World Trade
Organization (WTO) principles in the Technical Barriers to Trade (TBT), see www.iso.org/iso/foreword.html.
This document was prepared by Technical Committee ISO/TC 46, Information and documentation,
Subcommittee SC 4, Technical interoperability.
This fourth edition cancels and replaces the third edition (ISO 28560-3:2023), of which it constitutes a minor
revision.
The change is as follows:
— in 7.4.4, “1: Acquisition extension block” has been corrected to read as “1: Library extension block.”
A list of all parts in the ISO 28560 series can be found on the ISO website.
Any feedback or questions on this document should be directed to the user’s national standards body. A
complete listing of these bodies can be found at www.iso.org/members.html.

v
Introduction
Libraries are implementing radio frequency identification (RFID) as item identification to replace bar codes.
RFID streamlines applications like user self-service, security, and materials handling. This standard data
model for encoding information on RFID tags increases the cost-effectiveness of the technology within
libraries, particularly through greater interoperability of RFID tags and equipment, and enhance support for
resource sharing between libraries.
This document deals with the encoding of a basic set of data elements in a fixed length format and the rest of
the data elements in optional extension blocks. ISO 28560-1 defines the set of mandatory and optional data
elements.
ISO 28560-2 and this document are mutually exclusive with respect to an RFID tag being applied to a loan
item. In other words, the RFID tag is encoded according to the rules of this document, or to the rules of
ISO 28560-2, or to some proprietary rules. Depending on the technologies being used, and other features
of tags that are claiming compliance with ISO 28560-2, the reading system might achieve a degree of
interoperability.
This document provides essential standards-based information about RFID in libraries. Ongoing advice
needs to be provided because of the evolving nature of RFID technology, and the opportunities to migrate
between different types of legacy system and encoding rules of this document.

vi
International Standard ISO 28560-3:2024(en)
Information and documentation — RFID in libraries —
Part 3:
Fixed length encoding
1 Scope
This document provides a data model and encoding rules for the use of radio frequency identification
(RFID) tags for items appropriate for the needs of all types of libraries (including national, academic, public,
corporate, special, and school libraries).
This document specifies the rules for encoding
— a subset of data elements taken from the total set of data elements listed in ISO 28560-1 into a basic
block, and
— other data elements into extension blocks onto the RFID tag.
A source of additional information about implementation issues is provided in Annex A.
2 Normative references
The following documents are referred to in the text in such a way that some or all of their content constitutes
requirements of this document. For dated references, only the edition cited applies. For undated references,
the latest edition of the referenced document (including any amendments) applies.
ISO 28560-1, Information and documentation — RFID in libraries — Part 1: Data elements and general
guidelines for implementation
ISO/IEC 10646, Information technology — Universal coded character set (UCS)
ISO/IEC 18000-3, Information technology — Radio frequency identification for item management — Part 3:
Parameters for air interface communications at 13,56 MHz
ISO/IEC 18046-3, Information technology — Radio frequency identification device performance test methods
— Part 3: Test methods for tag performance
ISO/IEC 18047-3, Information technology — Radio frequency identification device conformance test methods —
Part 3: Test methods for air interface communications at 13,56 MHz
3 Terms and definitions
For the purposes of this document, the terms and definitions given in ISO 28560-1 and the following apply.
ISO and IEC maintain terminology databases for use in standardization at the following addresses:
— ISO Online browsing platform: available at https:// www .iso .org/ obp
— IEC Electropedia: available at https:// www .electropedia .org/

3.1
basic block
data block occupying the first 272 bits of the RFID tag
Note 1 to entry: If the RFID tag is limited to 256 bits (i.e. 32 bytes), the basic block is truncated.
3.2
byte
8-bit byte
group of eight consecutive bits
Note 1 to entry: A byte can represent one character (3.3) or be part of a representation of a character.
3.3
character
one or more bytes (3.2)
3.4
CRC
cyclic redundancy check
value calculated from the data on the tag
3.5
data block
container for encoding data elements, CRC (3.4), filler, and end mark
3.6
end block
data block (3.5) containing the end mark terminating the information on the RFID tag
3.7
extension block
optional data block (3.5) following the basic block (3.1)
3.8
field
entry in a data block (3.5)
3.9
filler data block
optional data block (3.5) that can be inserted to align other data blocks on page (3.11) boundaries
3.10
fixed length field
field (3.8) of prescribed size in a data block (3.5)
3.11
page
minimum data unit that can be read from or written to a tag
Note 1 to entry: This is measured in bytes (3.2).
3.12
string
sequence of characters (3.3)
3.13
unsigned integer
binary value of a number of consecutive bits

3.14
variable length field
field (3.8) of variable size in a data block (3.5)
4 Requirements
4.1 Data elements
The data elements shall be as defined and compliant with those listed in ISO 28560-1.
NOTE There is a degree of flexibility in using locally defined codes that enable enhancements and variations to be
implemented while still complying with the basic set of data elements.
4.2 RFID air interface
4.2.1 Air interface conformance
The air interface for compliant tags shall be in accordance with the specification for Mode 1.
For migration purposes, additional non-compliant air interfaces used in legacy systems can be supported
during a transition period, which is permitted to remain in place for years, as necessary.
The air interface conformance shall be tested in accordance with ISO/IEC 18047-3.
4.2.2 Tag performance
Where there are requirements for test tag performance, these shall be performed in accordance with
ISO/IEC 18046-3.
4.3 Data protocol
The fixed length encoding described in this document does not require a separate data protocol.
5 General encoding rules
5.1 Distinguishing from other applications and encodings
The value of the application family identifier (AFI) is used to distinguish tags for library applications from
other applications. The values of AFI for library applications are defined in ISO 28560-1.
ISO 28560-1 describes how the data storage format identifier (DSFID), if present in the system memory as
a programmable register, is used to distinguish tags in the library application area, i.e. with the same AFI.
Tags encoded according to this document shall be programmed with the value 3E in the DSFID register if
HEX
the tag contains a programmable DSFID register.
This document is not able to encode the DSFID if the tag does not contain a programmable DSFID register.
In this case, ISO 28560-2 encodes the DSFID in the first byte of the working area of the tag. To take this
situation into account, the content parameter (see Table 1) shall not take the value 6 on RFID tags encoded
according to this document.
If and only if the tag does not contain a programmable DSFID register, it is permissible to distinguish tags
encoded according to this document from other encodings by verifying the cyclic redundancy check (CRC)
encoded in the basic block (see 7.2).

5.2 Writing/reading direction
Data shall be written to and read from the tag as specified in ISO/IEC 18000-3, Mode 1, such that the first
bit transmitted to or from the tag is the least significant bit of the first field of the basic block. This field
contains the content parameter (see Table 1). From that starting point, bytes are transmitted to or from
the tag in order from left to right, with byte 0 to the left of bytes 1, 2, and 3, as shown in the memory map in
Annex B.
5.3 Memory area layout
5.3.1 Specifications
The memory area shall be encoded starting with a basic block with fixed length encoding of a basic set of
data elements for use in the library.
If the size of the RFID tag is limited to 256 bits (32 bytes), the RFID tag can only contain a truncated basic block.
If the size of the RFID tag is greater than 256 bits, extension blocks (structured or unstructured) can be
inserted after the basic block up to the capacity of the chip. If extension blocks are inserted, the order of
these is optional. The length of an extension block is determined by the first byte of the block. The type of
extension block is defined in the following two bytes.
Filler data blocks may be inserted between blocks to align to page boundaries.
An end block shall terminate the encoding, unless the basic block and possible extension blocks take up the
whole space on the RFID tag, in which case an end block is not needed.
5.3.2 Layout for tags greater than 32 bytes
The layout for tags greater than 32 bytes (256 bits) shall be as follows:
[()*]*()*()
The end block is mandatory if the tag is not full (see 5.3.1). Basic block, filler data block, structured extension
blocks, unstructured extension blocks, and end block are specified in Clause 7.
An example is given in Annex B.
5.3.3 Layout for 32-byte tags
The layout for 32-byte tags shall be as follows:

The truncated basic block is specified in Clause 7.
An example is given in Annex B.
5.4 Strings and integers
5.4.1 String encoding
All strings shall be encoded in UTF-8 in accordance with ISO/IEC 10646, with the first character of the string
stored in the lowest memory location. Note that UTF-8 encoding implies that a character can occupy more
than one byte.
The end of a string can be defined in the following different ways:
— with one byte 00 ;
HEX
— with the length of a fixed length field;

— with the end of a structured extension block.
For fixed length fields, all unused bytes shall be 00 .
HEX
For variable length fields, one byte 00 shall be used between each field.
HEX
5.4.2 Integer encoding
Integer-encoded fields shall use 4, 8, or 16 bits unsigned integers.
5.5 Writing the tag
5.5.1 Cyclic redundancy check (CRC)
For RFID tags with only 32 bytes (256 bits) user data space of the basic block is truncated two bytes, but the
CRC shall be calculated for a full-length basic block with the two missing bytes assumed to be 00 .
HEX
See 7.2 and Annex C for a description of CRC.
5.5.2 Unused space
Any unused space in blocks shall be filled with 00 , i.e. a 6-byte primary item identifier encoded in the
HEX
basic block (see 7.2) shall be written as the 6-byte primary item identifier followed by 10 bytes 00 . It is
HEX
very important for reading optimization that this rule be followed.
5.5.3 End of tag
If a data block ends on the last user byte of a tag, no “end block” is required. The length specified in the last
data block shall not indicate a size larger than the tag.
5.6 Reading optimization
Guidelines for reading optimization are given in Annex D.
5.7 Profiling
Guidelines for regional profiling are given in Annex E.
5.8 Locking
It is technically possible to lock parts of the tag, but this document does not prescribe any strategy for
locking. Such a strategy is left for regional profiling.
6 Data elements
Table 1 shows for each data element defined in ISO 28560-1 the data block where it is encoded, how it is
encoded, and the values it can take. Note that some data elements can be encoded in different data blocks.
The data blocks are described in Clause 7.

Table 1 — Data elements
Name of data Requirements
a c d e
N Data block Encoding Values
b f
element and remarks
1 Primary item Basic block or If the primary item identifi- Any string If a primary identi-
identifier library extension er is maximum 16 bytes, it fier is not assigned
block shall be encoded in the basic yet, the string is
block as a string. empty
.
Otherwise, it shall be encod-
ed as a string in the library
extension block.
2 Content param- Basic block 4-bit unsigned integer 1 The value defines a
eter version number.
(14 values are
reserved for future A new version num-
use: 0, 2, 3, 4, 5, 7, 8, ber shall be applied
9, 10, 11, 12, 13, 14, if and only if it refers
15. To be able to dis- to a new version
tinguish from tags of this document,
encoded according which is not back-
to ISO 28560-2, the ward compatible.
value 6 shall not be
used.)
3 Owner institu- Basic block or If the ISIL prefix is one or If the tag is limited The ISIL code is
tion (ISIL) library extension two characters and the ISIL to 32 bytes, only defined in ISO 15511
block unit identifier is less than or ISIL codes with a as equal to 11 bytes (or 9 bytes prefix of a maximum phen> for 32 bytes tags), the string of two characters er>, where
can be encoded in the basic and a unit identifier shall be either an
block. In this case, the less than 9 bytes can alpha-2 country
string shall be formed as the be encoded. code (two up-
concatenation of the prefix per-case letters), or
If the size of the
and the unit identifier. If the another registered
tag is more than
prefix is only one character, string (non-country
32 bytes, any ISIL
a blank is added between the code), and where
code can, in theory,
prefix and the unit identifier. can
be encoded.
be up to 11 charac-
If the prefix is more than
ters long.
two characters or the unit
identifier is longer than
11 bytes, the string can be
encoded in the library exten-
sion block. In this case, the
string shall be the ISIL code,
including the hyphen.
a
This column specifies the data element number, i.e. the number identifying the data element in ISO 28560-1. Data elements
14, and 27 to 31 are reserved for future use, and therefore not listed in Table 1. When usage and type for these data elements are
defined, a mapping should be considered and specified, and then published at the informational website in Annex A.
b
This column specifies the data element name, i.e. the name identifying the data element in ISO 28560-1.
c
This column specifies the names of the data blocks in which the data element is encoded.
d
This column specifies how the data element is encoded. For encoding of strings and integers, see 5.4.1 and 5.4.2.
e
This column specifies the values the data element can take.
f
This column gives additional requirements and remarks.

TTabablele 1 1 ((ccoonnttiinnueuedd))
Name of data Requirements
a c d e
N Data block Encoding Values
b f
element and remarks
4 Set information Basic block Two 8-bit unsigned integers, the first specifying can take sists of two parts:
of parts in item> and the sec- the values 0 to 255,
ond . where 0 indicates an
item> and unspecified number.
part number>
See examples in
number> can take
ISO 28560-1.
the values 0 to 255,
where 0 indicates
the first item in a
set, where not all
items have an RFID
tag.
5 Type of usage Basic block or Main qualifier shall be The set of code The data element
library extension encoded in basic block as a values is specified in consists of two
block 4-bit unsigned integer. ISO 28560-1. parts:
As a supplement, the whole