SIST ISO 28560-3:2024

Information and documentation - RFID in libraries - Part 3: Fixed length encoding

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.

Information et documentation — RFID dans les bibliothèques — Partie 3: Encodage de longueur fixe

Informatika in dokumentacija - RFID v knjižnicah - 3. del: Kodiranje z nespremenljivo dolžino

Standard ISO 28560-3:2014 določa podatkovni model in pravila kodiranja za uporabo oznak za radiofrekvenčno prepoznavo (RFID) za elemente, primerne za potrebe vseh vrst knjižnic (vključno z nacionalnimi, akademskimi, javnimi, poslovnimi, posebnimi in šolskimi knjižnicami).
Standard ISO 28560-3:2014 določa pravila za kodiranje
podniza podatkovnih elementov, izvzetih iz celotnega niza podatkovnih elementov iz standarda ISO 28560‑1 v osnovni blok, in drugih podatkovnih elementov v razširitvene bloke na oznako RFID.

General Information

• Status: Withdrawn
• Publication Date: 20-Aug-2024
• Withdrawal Date: 09-Apr-2025
• ICS: 35.040.50 - Automatic identification and data capture techniques
• ICS: 35.240.30 - IT applications in information, documentation and publishing
• Technical Committee: IDT - Information, documentation, language and terminology
• Current Stage: 9900 - Withdrawal (Adopted Project)
• Start Date: 10-Apr-2025
• Due Date: 03-May-2025
• Completion Date: 10-Apr-2025
• Ref Project: ISO 28560-3:2023 - Information and documentation - RFID in libraries - Part 3: Fixed length encoding

Relations

• Replaces: SIST ISO 28560-3:2014 - Information and documentation -- RFID in libraries -- Part 3: Fixed length encoding
• Effective Date: 01-Oct-2024
• Replaced By: SIST ISO 28560-3:2025 - Information and documentation - RFID in libraries - Part 3: Fixed length encoding
• Effective Date: 01-Jun-2025

Overview

SIST ISO 28560-3:2024 - Information and documentation - RFID in libraries - Part 3: Fixed length encoding - defines a standards-based data model and encoding rules for storing library item information on RFID tags. Intended for all types of libraries (national, academic, public, corporate, special and school), the standard specifies a fixed-length basic block plus optional extension blocks for additional data elements. It promotes interoperability of RFID tag encoding and supports migration from legacy systems while providing implementation guidance in informative annexes.

Key topics and technical requirements

• Data model and elements: Uses the data elements defined in ISO 28560-1; a subset is encoded in the fixed-length basic block and other elements in extension blocks. Local codes may be used where allowed by ISO 28560-1.
• Basic block: Occupies the first 272 bits of the tag; if a tag is limited to 256 bits (32 bytes) the basic block is truncated.
• Extension blocks: Support structured and unstructured extension blocks (e.g., library extension block, acquisition extension, title block, ILL block) to encode optional or longer data.
• Encoding rules: Defines string and integer encoding, fixed-length and variable-length fields, memory area layout, writing/reading direction, and CRC (cyclic redundancy check) handling for data integrity.
• RFID air interface: Requires conformance to Mode 1 of the air interface specification (see ISO/IEC 18000-3); tag performance and conformance test methods are referenced (ISO/IEC 18046-3, ISO/IEC 18047-3).
• Page and memory alignment: Uses the concept of a page (minimum read/write unit) and allows filler blocks for page alignment.
• Operational features: Guidance on reading optimization, profiling, locking, and migration between encodings.

Practical applications and users

• Library uses: Item identification for circulation, self-service checkout, security, inventory, materials handling and resource sharing.
• Who benefits:
  • Library systems architects and technical staff implementing RFID
  • RFID equipment and tag manufacturers ensuring compliance
  • Library consortia coordinating interoperable tagging policies
  • Procurement teams specifying tag and reader requirements
  • Software developers integrating tag data into ILS/ILS-like systems
• Practical value: Enables consistent, interoperable RFID tag encoding across vendors and collections, reducing costs and simplifying interlibrary lending and shared services.

Related standards

• ISO 28560-1 - Data elements and implementation guidelines
• ISO 28560-2 - Alternative (mutually exclusive) encoding rules
• ISO/IEC 18000-3 - RFID air interface at 13.56 MHz (Mode 1)
• ISO/IEC 18046-3, ISO/IEC 18047-3 - Tag performance and conformance test methods
• ISO/IEC 10646 - Universal coded character set (UCS)

For implementation examples and technical annexes (CRC, reading optimization, profiling), consult the informative annexes in SIST ISO 28560-3:2024.

Standards Content (Sample)

SLOVENSKI STANDARD
01-oktober-2024
Nadomešča:
SIST ISO 28560-3:2014
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:2023
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 ISO
STANDARD 28560-3
Third edition
2023-04
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
Reference number
© ISO 2023
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: [phone]
Email: [e-mail]
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 . 3
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
iii
Annex B (informative) Encoding examples .18
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 documents 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).
Attention is drawn to the possibility that some of the elements of this document may be the subject of
patent rights. ISO shall not be held responsible for identifying any or all such patent rights. Details of
any patent rights identified during the development of the document will be in the Introduction and/or
on the ISO list of patent declarations received (see www.iso.org/patents).
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 third edition cancels and replaces the second edition (ISO 28560-3:2014), of which it constitutes a
minor revision.
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:2023(E)
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 — 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.
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
HEX
register if 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
HEX
the basic block (see 7.2) shall be written as the 6-byte primary item identifier followed by 10 bytes
00 . It is very important for reading optimization that this rule be followed.
HEX
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 li- If the primary item identifi- Any string If a primary identi-
identifier brary extension er is maximum 16 bytes, fier is not assigned
block it shall be encoded in the yet, the string is
basic block as a string. empty
.
Otherwise, it shall be
encoded 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
use: 0, 2, 3, 4, 5, number shall be
7, 8, 9, 10, 11, 12, applied if and only
13, 14, 15. To be if it refers to a new
able to distinguish version of this part
from tags encod- of ISO 28560, which
ed according to is not backward
ISO 28560-2, the compatible.
value 6 shall not be
used.)
3 Owner institu- Basic block or li- If the ISIL prefix is one or If the tag is lim- The ISIL code
tion (ISIL) brary extension two characters and the ISIL ited to 32 bytes, is defined in
block unit identifier is less than only ISIL codes ISO 15511 as or equal to 11 bytes (or with a prefix of a fix> 9 bytes for 32 bytes tags), maximum of two identifier>, where
the string can be encoded characters and a shall be
in the basic block. In this unit identifier less either an alpha-
case, the string shall be than 9 bytes can be 2 country code
formed as the concatena- encoded. (two upper-case
tion of the prefix and the letters), or another
If the size of the
unit identifier. If the prefix registered string
tag is more than
is only one character, a (non-country code),
32 bytes, any ISIL
blank is added between and where code can, in theory,
the prefix and the unit identifier> can be
be encoded.
identifier. up to 11 characters
long.
If the prefix is more than
two characters or the unit
identifier is longer than
11 bytes, the string can be
encoded in the library ex-
tension 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 inte- gers, the first specifying in item> can take consists of two
the values 0 to 255, parts:
and the second part number>. an unspecified
in item> and number.
nal 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 li- Main qualifier shall be The set of code The data element
brary extension encoded in basic block as a values is specified consists of two
block 4-bit unsigned integer. in ISO 28560-1. parts:
As a supplement, the whole

data element can be encod- and ed in the library extension er>.
block as an 8-bit unsigned
integer.
6 Shelf location Library supple- String Any string specify- See ISO 28560-1.
ment block ing the location of
the item
7 ONIX media Library supple- String ONIX media de- See ISO 28560-1.
format ment block scriptor of two al-
phabetic characters
8 MARC media Library supple- String MARC 21 category See ISO 28560-1.
format ment block of material descrip-
tor
9 Supplier iden- Acquisition ex- String Any string identify- See ISO 28560-1.
tifier tension block ing the supplier of
the item
10 Order number Acquisition ex- String Any string identi- See ISO 28560-1.
tension block fying the order con-
taining the item
11 ILL borrowing ILL block String Any ISIL code in The ISIL code is de-
institution the form (ISIL) > identifier>
12 ILL borrowing ILL block String Any string identify- See ISO 28560-1.
transaction ing the borrowing
number transaction
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
13 GS1 product Acquisition ex- String Any GTIN-13 code See ISO 28560-1.
identifier tension block
15 Local data A Unstructured Locally defined Locally defined See ISO 28560-1.
extension
blocks
16 Local data B Unstructured Locally defined Locally defined See ISO 28560-1.
extension
blocks
17 Title Title block String Any string specify- See ISO 28560-1.
ing the titles of the
item
18 Product identifi- Acquisition ex- String Any string speci- See ISO 28560-1.
er local tension block fying the product
identifier of the
item
19 Media format Library exten- 8-bit unsigned integer 0: Undefined See ISO 28560-1.
(other) sion block
1: Book
2: CD/DVD
3: Magnetic tape
4: Other
5: Other, careful
handling is
required
6: Very small
item, special
handling is
required
20 Supply chain Acquisition ex- 8-bit unsigned integer The set of code See ISO 28560-1.
stage tension block values are specified
in ISO 28560-1.
21 Supplier invoice Acquisition ex- String Any string identi- See ISO 28560-1.
number tension block fying the invoice
containing the item
22 Alternative item Library exten- String Any string identify- See ISO 28560-1.
identifier sion block ing the item
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
23 Alternative Basic block If the non-ISIL code is less Any string identify- See ISO 28560-1.
owner institu- or than or equal to 10 bytes ing the institution
tion library exten- (or 8 bytes for 32 bytes that owns the item,
sion block tags), it should be encod- that is either a na-
ed as a string in the basic tional standardized
block. code not part of
ISIL or a code that
Otherwise, it may be
is neither part of
encoded as a string in the
ISIL nor a national
library extension block.
standard
24 Subsidiary of an Library supple- String Any string defined See ISO 28560-1.
owner institu- ment block by the institution
tion that owns the item
25 Alternative ILL ILL block String Any string identify- See ISO 28560-1.
borrowing insti- ing the institution
tution that borrows the
item
26 Local data C Unstructured Locally defined Locally defined See ISO 28560-1.
extension
blocks
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.
7 Data blocks
7.1 Types of data blocks
The following types of data blocks exist:
— basic block;
— special blocks;
— structured extension blocks;
— unstructured extension blocks.
The rules for encoding these different types of data blocks are given in 7.2 to 7.10.
7.2 Basic block
The basic block contains a number of fixed length data fields. The basic block occupies the first 34 bytes
(272 bits) on the tag. If the tag has only 32 bytes (256 bits), the layout for the truncated basic block shall
be used. In this case, no other data can be stored on the tag.
Table 2 and Table 3 specify the usage and layout of the basic block and the truncated basic block.
Table 2 — Usage and layout of the basic block
a b c
Position Length Content of field
0 (0) 4 bits Content parameter (data element 2)
0 (4) 4 bits Type of usage

(data element 5)
1 2 bytes Set information (data element 4)
and , the first stored in the low byte
and the second in the next byte
3 16 bytes This field can contain the empty string or the primary item identifier (data element 1) if
it is maximum 16 bytes.
Otherwise, the first byte shall be 01 , and the primary item identifier shall be encoded
HEX
in the library extension block.
19 2 bytes This field shall contain the CRC, which is not a data element but a value calculated as part
of the encoding. The purpose is to detect reading and writing errors.
16 12 5
CRC-16-CCITT shall be used with x + x + x + 1 polynomial and FFFF as start value. The
CRC shall be calculated starting from the lowest address and skipping the two CRC bytes.
21 13 bytes This field can contain the empty string or the owner institution (ISIL) (data element 3),
in which case the first two bytes shall be a two-character country code or a one-letter
non-country code followed by a blank. The following bytes shall be the unit identifier. The
country code, the non-country code, and the unit identifier are defined in ISO 15511. The
hyphen specified in ISO 15511 shall not be encoded.
If the third byte is 01 , the owner institution (ISIL) (data element 3) shall be encoded in
HEX
the library extension block; in this case, the value of the other bytes in the field is undefined.
If the third byte is 02 or 03 the string starting from byte 4 shall be the alternative
HEX HEX,
owner institution (data element 23); in this case, the value of the first two bytes in the
field is undefined. 02 shall indicate a national standardized code not part of ISIL and
HEX
03 shall indicate an institution code that is neither part of ISIL nor a national standard.
HEX
Use of ISIL is highly recommended. The escape options should only be used in a transition
period or if ISIL is irrelevant.
a
Start position of the field given as byte number, with bit number in parentheses. If the bit number is not given, 0 is
assumed.
b
Length of field.
c
Content of field. For data elements, refer to Table 1 and for string and integer encoding, refer to 5.4.
Table 3 — Usage and layout of the truncated basic block
a b c
Position Length Content of field
0 (0) 4 bits Content parameter (data element 2)
0 (4) 4 bits Type of usage

(data element 5)
1 2 bytes Set information (data element 4)
and , the first stored in the low byte
and the second in the next byte
3 16 bytes This field can contain the empty string or the primary item identifier (data element 1) if
it is maximum 16 bytes.
Otherwise, the first byte is 01 , and the primary item identifier shall be encoded in the
HEX
library extension block.
a
Start position of the field given as byte number with bit number in parentheses. If the bit number is not given, 0 is
assumed.
b
Length of field measured in bytes or bits.
c
Content of field. For data elements, refer to Table 1 and for string and integer encoding, refer to 5.4.
TTabablele 3 3 ((ccoonnttiinnueuedd))
a b c
Position Length Content of field
19 2 bytes This field shall contain the CRC, which is not a data element but a value calculated as part
of the encoding. The purpose is to detect reading and writing errors.
16 12 5
CRC-16-CCITT shall be used with x + x + x + 1 polynomial and FFFF as start value. The
CRC shall be calculated starting from the lowest address and skipping the two CRC bytes.
See special remark in the next row.
21 11 bytes This field can contain the empty string or the owner institution (ISIL) (data element 3),
in which case the first two bytes shall be a two-character country code or a one-letter
non-country code followed by a blank. The following bytes shall be the unit identifier. The
country code, the non-country code, and the unit identifier are defined in ISO 15511. The
hyphen specified in ISO 15511 shall not be encoded.
If the third byte is 01 , the owner institution (ISIL) (data element 3) shall be encoded in
HEX
the library extension block; in this case, the value of the other bytes in the field is undefined.
If the third byte is 02 or 03 the string starting from byte 4 shall be the alternative
HEX HEX,
owner institution (data element 23); in this case the value of the first two bytes in the
field is undefined. 02 shall indicate a national standardized code not part of ISIL and
HEX
03 shall indicate an institution code that is neither part of ISIL nor a national standard.
HEX
Use of ISIL is highly recommended. The escape option should only be used in a transition
period or if ISIL is irrelevant.
Special remark:
For CRC calculation this field shall be viewed as being 13 bytes long, i.e. the CRC calculation
algorithm shall add two bytes 00 to the end of the field.
HEX
a
Start position of the field given as byte number with bit number in parentheses. If the bit number is not given, 0 is
assumed.
b
Length of field measured in bytes or bits.
c
Content of field. For data elements, refer to Table 1 and for string and integer encoding, refer to 5.4.
7.3 Special blocks
The layout specified in 5.3 operates with two special blocks, each 1 byte of size.
Table 4 specifies the usage and layout of these special blocks.
Table 4 — Usage and layout of the special blocks
Block name Description Encoding
End block If there is room left on the tag, this block shall be added to signal the end of 1 byte = 00
HEX
the data.
Filler data block The block may be used to align other data blocks on page boundaries. If nec- 1 byte = 01
HEX
essary multiple instances may be used.
7.4 Structured extension blocks
7.4.1 Usage of structured extension blocks
Structured extension blocks are used as a supplement to the basic block to encode the full set of data
elements specified in ISO 28560-1.
It is permissible to have two or more structured extension blocks of the same type (i.e. with the same
data block ID).
7.4.2 Format of structured extension blocks
Structured extension blocks use a frame structure of 4 bytes to specify length, type and checksum. The
general structure of the extension blocks is:
()*
Data fields have to occur in the order specified for the specific structured extension block. A data field
can be empty. In th
...

INTERNATIONAL ISO
STANDARD 28560-3
Third edition
2023-04
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
Reference number
© ISO 2023
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: [phone]
Email: [e-mail]
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 . 3
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
iii
Annex B (informative) Encoding examples .18
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 documents 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).
Attention is drawn to the possibility that some of the elements of this document may be the subject of
patent rights. ISO shall not be held responsible for identifying any or all such patent rights. Details of
any patent rights identified during the development of the document will be in the Introduction and/or
on the ISO list of patent declarations received (see www.iso.org/patents).
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 third edition cancels and replaces the second edition (ISO 28560-3:2014), of which it constitutes a
minor revision.
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:2023(E)
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 — 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.
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
HEX
register if 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
HEX
the basic block (see 7.2) shall be written as the 6-byte primary item identifier followed by 10 bytes
00 . It is very important for reading optimization that this rule be followed.
HEX
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 li- If the primary item identifi- Any string If a primary identi-
identifier brary extension er is maximum 16 bytes, fier is not assigned
block it shall be encoded in the yet, the string is
basic block as a string. empty
.
Otherwise, it shall be
encoded 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
use: 0, 2, 3, 4, 5, number shall be
7, 8, 9, 10, 11, 12, applied if and only
13, 14, 15. To be if it refers to a new
able to distinguish version of this part
from tags encod- of ISO 28560, which
ed according to is not backward
ISO 28560-2, the compatible.
value 6 shall not be
used.)
3 Owner institu- Basic block or li- If the ISIL prefix is one or If the tag is lim- The ISIL code
tion (ISIL) brary extension two characters and the ISIL ited to 32 bytes, is defined in
block unit identifier is less than only ISIL codes ISO 15511 as or equal to 11 bytes (or with a prefix of a fix> 9 bytes for 32 bytes tags), maximum of two identifier>, where
the string can be encoded characters and a shall be
in the basic block. In this unit identifier less either an alpha-
case, the string shall be than 9 bytes can be 2 country code
formed as the concatena- encoded. (two upper-case
tion of the prefix and the letters), or another
If the size of the
unit identifier. If the prefix registered string
tag is more than
is only one character, a (non-country code),
32 bytes, any ISIL
blank is added between and where code can, in theory,
the prefix and the unit identifier> can be
be encoded.
identifier. up to 11 characters
long.
If the prefix is more than
two characters or the unit
identifier is longer than
11 bytes, the string can be
encoded in the library ex-
tension 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 inte- gers, the first specifying in item> can take consists of two
the values 0 to 255, parts:
and the second part number>. an unspecified
in item> and number.
nal 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 li- Main qualifier shall be The set of code The data element
brary extension encoded in basic block as a values is specified consists of two
block 4-bit unsigned integer. in ISO 28560-1. parts:
As a supplement, the whole

data element can be encod- and ed in the library extension er>.
block as an 8-bit unsigned
integer.
6 Shelf location Library supple- String Any string specify- See ISO 28560-1.
ment block ing the location of
the item
7 ONIX media Library supple- String ONIX media de- See ISO 28560-1.
format ment block scriptor of two al-
phabetic characters
8 MARC media Library supple- String MARC 21 category See ISO 28560-1.
format ment block of material descrip-
tor
9 Supplier iden- Acquisition ex- String Any string identify- See ISO 28560-1.
tifier tension block ing the supplier of
the item
10 Order number Acquisition ex- String Any string identi- See ISO 28560-1.
tension block fying the order con-
taining the item
11 ILL borrowing ILL block String Any ISIL code in The ISIL code is de-
institution the form (ISIL) > identifier>
12 ILL borrowing ILL block String Any string identify- See ISO 28560-1.
transaction ing the borrowing
number transaction
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
13 GS1 product Acquisition ex- String Any GTIN-13 code See ISO 28560-1.
identifier tension block
15 Local data A Unstructured Locally defined Locally defined See ISO 28560-1.
extension
blocks
16 Local data B Unstructured Locally defined Locally defined See ISO 28560-1.
extension
blocks
17 Title Title block String Any string specify- See ISO 28560-1.
ing the titles of the
item
18 Product identifi- Acquisition ex- String Any string speci- See ISO 28560-1.
er local tension block fying the product
identifier of the
item
19 Media format Library exten- 8-bit unsigned integer 0: Undefined See ISO 28560-1.
(other) sion block
1: Book
2: CD/DVD
3: Magnetic tape
4: Other
5: Other, careful
handling is
required
6: Very small
item, special
handling is
required
20 Supply chain Acquisition ex- 8-bit unsigned integer The set of code See ISO 28560-1.
stage tension block values are specified
in ISO 28560-1.
21 Supplier invoice Acquisition ex- String Any string identi- See ISO 28560-1.
number tension block fying the invoice
containing the item
22 Alternative item Library exten- String Any string identify- See ISO 28560-1.
identifier sion block ing the item
a
This column specifies the data element number, i.e. the number identifying the data element in ISO 28560-1. Data
eleme
...