ISO 10161-2:1997

SLOVENSKI STANDARD
SIST ISO 10161-2:2013
01-julij-2013
,QIRUPDWLNDLQGRNXPHQWDFLMD6NXSLQD]DSRYH]RYDQMHRGSUWLKVLVWHPRY
6SHFLILNDFLMDDSOLNDFLMVNHJDSURWRNROD]DPHGNQMLåQLþQRL]SRVRMRGHO,]MDYDR
VNODGQRVWLL]YHGEHSURWRNROD3,&6SURIRUPD
Information and documentation -- Open Systems Interconnection -- Interlibrary Loan
Application Protocol Specification -- Part 2: Protocol implementation conformance
statement (PICS) proforma
Information et documentation -- Interconnexion de systèmes ouverts (OSI) --
Spécification du protocole d'application pour les prêts entre bibliothèques -- Partie 2:
Proforma d'établissement de conformité pour la mise en oeuvre du protocole (PICS)
Ta slovenski standard je istoveten z: ISO 10161-2:1997
ICS:
35.240.30 Uporabniške rešitve IT v IT applications in information,
informatiki, dokumentiranju in documentation and
založništvu publishing
SIST ISO 10161-2:2013 en,fr,de
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.

---------------------- Page: 1 ----------------------

SIST ISO 10161-2:2013

---------------------- Page: 2 ----------------------

SIST ISO 10161-2:2013
INTERNATIONAL IS0
10161-2
STANDARD
First edition
1997-06- 15
Information and documentation - Open
Systems Interconnection - Interlibrary
Loan Application Protocol Specification -
Part 2:
Protocol implementation conformance
statement (PIGS) proforma
Information et documentation - lnterconnexion de systgmes ouverts
(OSI) - Spkcification du protocole d’applica tion pour les p&s entre
bibliothkques -
Partie 2: Proforma d’6tablissement de conformit pour la mise en cwvre du
protocole (PICS)
Reference number
IS0 10161-2:1997(E)

---------------------- Page: 3 ----------------------

SIST ISO 10161-2:2013
IS0 10161-2:1994(E)
Contents
A.9 INTEIILIBRARY LOAN APPLICATION
SCOPE . . . . . . . . . . . . . . . . .0. 1
SERVICES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
NORMATIVE REFERENCES
. . . . . . . . . . . . . . . . . . . . 1
A.9.1 Support for Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9
DEFINITIONS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .o. 1
A.9.2 Optional APDUs
. . . . . . . . . . . . . . . . . . . . . . . .*. 10
ABBREVIATIONS . . . . . . . . . . . . . . . . . . .o. 1 A. 10 SUPPORT FOR APDU PARAMETERS . . . . . . 12
A. 10.1 ILL-Request-APDU
..*.........a.............. 13
LAYOUT
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .~. 2
A. 10.2 Forward-Notification APDIJ . . . . . . . . . . . . .16
CONFORMANCE . . . . . . . .*. 2
A. 10.3 Shipped APDU
. . . . . . . . . . . .o. 17
NOTATIONS DEFINED IN THE
A. 10.4 Ill-Answer APDU
. . . . . . . . . . . . . .“.O. 18
PROFORMA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .r. 2
A. 10.5 Conditional-Reply APDU . . . . . . . . . . . . . . . . . .19
A. 10.6 Cancel APDU
PICS NUMBERS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .*. 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
A. 10.7 Cancel-Reply APDU
. . . . . . . . . . . . . . . . . . . . . . . . . . 20
9 COMPLETION OF THE PICS . . . . . . . . . . . . . . . . . . . .3
A. 10.8 Received APDU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
A. 10.9 Recall APDU
ANNEXES . . . . . . . . . . . . . . . . . . . . . . . . . . .a. 21
A.lO.10
Returned APDU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
A PICS PROFORMA FOR THE
A.10.11 Checked-In APDU
. . . . . . . . . . . . . . . . . . . . . . . . . . . 22
INTERLIBRARY LOAN
A.10.12 Overdue APDU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
PROTOCOL . 4
A.10.13 Renew APDU
. . . . . . . . . . . . . . . . . . . . . . . . .“. 23
A. 1
IMPLEMENTATION DETAILS . .4
A.10.14 Renew-Answer APDU . . . . . . . . . . . . . . . . . . . . .23
A. 1.1 Date of Statement . 4
A.10.15 Lost APDU . . . . . . . .“.S.
24
A. 1.2 Identification of the Implementation
.... .4
A.10.16
Damaged APDU . . . . . . . . . . . . . . . .*. 24
A.2 GLOBAL STATEMENT OF CONFORMANCE .4
A.10.17 Message APDU . . . . . . . . . . . . . . . . . . . . . . . . . . .e.
25
A.3 IS0 10161-l DETAILS
............................... 5
A.10.18
Status-Query APDU . . . . . . . . . . . . . . . . . . . . . . . . .2 5
A.4 APPLICATION-CONTEXT NAMES .
.5
A.10.19 Status-Or-Error-Report . . . . . . . . . . . . . . . . . . . .26
A.5 ROLES SUPPORTED . 5
A.10.20
Expired APDU . . . . . . . . . . . . . . . . . . . . .*. 27
A.6 ILL SERVICE TYPES SUPPORTED . .5
A. 1 1 COMMON PARAMETERS . . . . . . . . . . . . . . . . . . . . . . . .2 8
A.7 TRANSACTION TYPES SUPPORTED
........... .6
A. 12 SUPPORT FOR CHOICE TYPES . . . . . . . . . . . . .3 1
A.8 SYNTAXES . 7
A. 13 ENUMERATED TYPES
. . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
AX. 1 Abstract Syntaxes Supported . .7
A.8.2 Transfer Syntaxes . 8 B BIBLIOGRAPHY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
38
0 IS0 1997
All rights reserved. Unless otherwise specified, no part of this publication may be reproduced
or utilized in any form or by any means, electronic or mechanical, including photocopying and
microfilm, without permission in writing from the publisher.
lnternational Organization for Standardization
Case postale 56 l CH-1211 Geneve 20 l Switzerland
Internet central @ iso.ch
x.400 c=ch; a=40Onet; p=iso; o=isocs; s=central
Printed in Switzerland
ii

---------------------- Page: 4 ----------------------

SIST ISO 10161-2:2013
@ IS0 IS0 10161-2:1997(E)
Foreword
IS0 (the International Organization for Standardization) is a worldwide federation
of national standards bodies (IS0 member bodies). The work of preparing Inter-
national Standards is normally carried out through IS0 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. IS0 collaborates closely with the International Electrotechnical
Commission (IEC) on all matters of electrotechnical standardization.
Draft International Standards adopted by the technical committees are circulated to
the member bodies for voting. Publication as an International Standard requires
approval by at least 75 % of the member bodies casting a vote.
International Standard IS0 10 16 l-2 was prepared by Technical Committee
ISOITC 46, Information and documentation Subcommittee SC 4, Computer
applications in information and documentation.
IS0 10 16 1 consists of the following parts, under the general title Information and
documentation - Open Systems Interconnection - Interlibrary Loan Application
Protocol SpeciJication:
- Part I: Protocol specification
Part 2: Protocol implementation conformance statement (PICS) proforma
Annex A forms an integral part of this part of IS0 10 16 1. Annex B is for
information only.
. . .
III

---------------------- Page: 5 ----------------------

SIST ISO 10161-2:2013
IS0 10161-2: 1997(E)
Introduction
To evaluate conformance of a particular implementation of an OS1 protocol, it is necessary to have a description
of the capabilities and options which have been implemented. Such a description is called a Protocol
Implementation Conformance Statement (PICS).
A PICS Proforma is developed as a companion standard to an OS1 protocol standard. It is developed in the form
of a questionnaire to be filled out by a supplier of a product claiming to implement the protocol. The filled-out
questionnaire becomes the PICS for the product. It indicates which capabilities and options have been
implemented and what limitations might prevent inter-working. It allows a customer of the product to evaluate its
conformance to the standard and to determine whether the product meets the customer’s requirements.
This part of IS0 10161 defines a Protocol Implementation Conformance Statement (PICS) proforma for
the detailed expression of the conformance requirements of IS0 10 16 I- 1: 1997 which incorporates Defect
Reports l-22 and Amendment 1: ILL Support for Electronic Document Delivery. Details of the use of this
proforma are provided in this part of IS0 10161.
The level of detail required in the proforma exceeds that of the protocol specification by requiring details of the
implementor in addition to details of the imp lementation.
iv

---------------------- Page: 6 ----------------------

SIST ISO 10161-2:2013
IS0 10161-2:1997(E)
INTERNATIONAL STANDARD 0 IS0
- Open Systems Interconnection -
Information and documentation
Interlibrary Loan Application Protocol Specification -
Part 2: Protocol implementation conformance statement (PICS) proforma
ISOIIEC 9646-2: 199 1, Information technology -
1 Scope
Open Systems Interconnection - Conformance
This part of IS0 10161 defines the PICS
testing methodology andfiamework - Part 2:
proforma for the ILL protocol as specified in
Abstract test suite specification.
IS0 10 161-1, in compliance with the relevant
requirements, and in accordance with the
IS0 9735: 1988, Electronic data interchange
relevant guidance for a PICS proforma, given
for administration, commerce and transport
in IS0 9646-2. Implementors claiming
(EDIFACT) - Application level syntax rules.
conformance to IS0 10 16 l-l shall complete
IS0 10 16 1- 1: 1997, Information and
the proforma as part of the conformance
documentation - Open Systems
requirements.
Interconnection - Interlibrary Loan
Application Protocol Specification - Part 1:
2 Normative References
Protocol specification.
The following standards contain provisions
which, through reference in this text, constitute
3 Definitions
provisions of this part of IS0 10161. At the
This part of IS0 10161 uses the following
time of publication, the editions indicated were
terms defined in IS0 9646- 1: 1990.
valid. All standards are subject to revision, and
parties to agreements based on this part of
3.1 PICS proforma: A document, in the
IS0 10 16 1 are encouraged to investigate the
form of a questionnaire, designed by the
possibility of applying the most recent editions
protocol specifier or conformance test suite
of the standards indicated below. Members of
specifier, which when completed for an OS1
IEC and IS0 maintain registers of currently
implementation or system becomes the PICS.
valid International Standards.
ISOIIEC 8825: 1990, Information technology -
3.2 protocol implementation conformance
Open Systems Interconnection - Spectfication
statement [PICS]: A statement made by the
of Basic Encoding Rules for Abstract Syntax
supplier of an OS1 implementation or system,
Notation One (ASN. 1).
stating which capabilities have been
implemented, for a given OS1 protocol.
ISOIIEC 9646- 1: 1994, Information technology -
Open Systems Interconnection - Conformance
4 Abbreviations
testing methodology and@amework - Part I:
General concepts.
This part of IS0 10161 uses the following
abbreviations:
NOTE - ISO/IEC 9646- 1: 1994 supersedes
IS0 9646-l : 199 1. However, when this part of
APDU - Application Protocol Data Unit
IS0 10 16 1 was under development, the previous
edition was valid and this part of IS0 10 161 is
ASN. 1 - Abstract Syntax Notation One
therefore based on this edition, which is given below.
EDIFACT - Electronic Data Interchange for
ISOIIEC 9646- 1: 199 1, Information technology -
Administration, Commerce and Transport
Open Systems Interconnection - Conformance
IEC - International Electrotechnical
testing methodology andfiamework - Part I:
Commission
General concepts.
ILL - Interlibrary Loan
ISOIIEC 9646-2: 1994, Information technology -
Open Systems Interconnection - Conformance
IS0 - International Organization for
testing methodology andfiamework - Part 2:
Standardization
Abstract Test Suite specification.
OSI - Open Systems Interconnection
NOTE - ISOLIEC 9646-2: 1994 supersedes
IS0 9646-2: 1991. However, when this part of
PIGS - Protocol Implementation Conformance
IS0 10 16 1 was under development, the previous
Statement
edition was valid and this part of IS0 1016 1 is
TC - Technical Committee
therefore based on this edition, which is given below.
1

---------------------- Page: 7 ----------------------

SIST ISO 10161-2:2013
IS0 10161=2:1997(E) 0 IS0
5 Layout
‘c’: conditional: support for this feature is
mandatory if certain conditions as
Annex A contains the actual proforma to be
specified in IS0 10 161-1 are met. The
filled in by an implementor claiming
conditions to be met are indicated by
conformance to IS0 1016 l-l. The PICS
an integer referencing a table of
proforma has been designed to be a self-
conditions at the end of each proforma
contained section of this part of IS0 10 16 1, for
section.
use in testing and procurement.
‘cc’: conditional on supporting
6 Conformance communication service: support for this
feature is mandatory if the supporting
A conforming PICS shall:
communication service is store-and-
a. be technically equivalent to the IS0
forward service; support is optional if
published PICS proforma and shall preserve
the supporting communication service
the numbering and ordering of the items in the
is connection-oriented.
IS0 PICS proforma.
6 7.
. not applicable.
b. include the information necessary to
72 . ‘I’ Column
uniquely identify both the supplier and the
implementation.
The ‘I’ column shall be completed by the
supplier or implementor to indicate the level of
A supplier shall complete this PICS proforma
implementation of each feature. The Proforma
in accordance with the instructions for
has been designed such that the only entries
completion given in clauses 7 and 9.
required in the ‘I’ column are:
7 Notations Defined in the Proforma 6 7.
Yes, the feature has been implemented
Y .
6 7.
In order to reduce the size of the tables in the
N . No. the feature has not been
proforma, a number of abbreviations have been
implemented
introduced. The definition of each of these
6 7.
. Not applicable to this implementation
follows:
73 ‘Reference, Usage or Range of
For column headings:
\;alues’ Column
6 7.
D . Defined in IS0 10 161 -I. This column
The ‘Reference, Usage or Range of Values’
indicates the level of support required
column requires the specification of
for conformance to IS0 IO 16 1 -I.
information pertaining to the usage or range of
6 3.
I . Implementation indicator. This column values implemented for a feature, where
shows which parameters or other relevant and/or where the implementation
details have or have not been has restrictions or limits not present in
implemented. IS0 10161-l.
If the proforma has insufficient room for a
71 . ‘D’ Column
complete description of the usage or range of
values for any particular feature, a reference to
‘m’: mandatory: support for this feature is
an attachment on a separate page may be given
required for conformance to IS0
here.
10161-l.
8 PICS Numbers
‘0’: optional: support for this feature is
permitted, but is not required for
Each line in the PICS proforma which requires
conformance to IS0 10 16 l- 1.
implementation detail to be supplied is
However, if this feature is
numbered at the left-hand edge of the line.
implemented, it must conform to the
This numbering is included as a means of
specifications and restrictions
uniquely identifiying all possible
contained in IS0 10161-l. These
implementation details within the proforma.
restrictions may affect the optionality
The need for such unique referencing has been
of other features.
identified by testing bodies.
2

---------------------- Page: 8 ----------------------

SIST ISO 10161-2:2013
IS0 10161-2: 1997(E)
0 IS0
The means of referencing individual responses and its scope is restricted to the clause in
which it appears.
shall be to specify the smallest subclause
enclosing the relevant item and the reference
Other specifically identified information shall
number of the row in which the response
be provided by the implementor where
appears.
requested.
No changes shall be made to the proforma
9 Completion of the PICS
except the addition of responses as required.
The implementor shall complete all
Recognizing that the level of detail required
66
1” entries in the proforma, in addition
may, in some instances, exceed the space
[
to other specifically identified sections. In
available for responses, the implementor may
certain clauses, further guidance for
continue the response on separate paper (so
completion is included. Such guidance
indicating this in the space provided) and
supplements the guidance given in this clause
provide a reference (see clause 8).

---------------------- Page: 9 ----------------------

SIST ISO 10161-2:2013
IS0 10161=2:1997(E)
Annex A
(normative)
Protocol Implementation Conformance Statement (PICS)
Proforma for the Interlibrary Loan Protocol’)
Section One - General Information
Al . Implementation Details
A.1.1 Date of Statement
1 Date of Statement(YYW-MM-DD):
6
Identification of the Implementation
A.l.2
1 Implementation Supplier:
I I I I
Implementation Name:
2
I I I I
Implementation Version Number:
13 I I I
4 Machine Name:
I I I I
r5-- 1 Machine Version Number:
I I
6 Operating System Name:
I I I I
7 Operating System Version Number:
I I I I
8 Other Operating Systems:
I I I I
Other Hardware:
19 I I I
10 System Name (if different):
I I I I
p-i- 1 Resources Required:
I I
12 Contact Name:
I I I I
pr1 Contact Address:
I I
14 Contact Telephone:
I I I I
A2 . Global Statement of Conformance
1 Are all mandatory features of IS0 10161-l implemented?
( I
1) Copyright release for PIGS proforma: Users of this part of IS0 10161 may freely reproduce this PIGS proforma so
that it can be used for its intended purpose and may further publish the completed PIGS.

---------------------- Page: 10 ----------------------

SIST ISO 10161-2:2013
IS0 10161-2:1997(E)
Section Two - General Details
A.3 IS0 10161-l Details
Protocol Version Number(s) that this PICS
describes:
Other Version Number(s) supported:
I I
Defect Report Number(s) implemented:
Amendment(s) implemented:
I
I
A.4 Application-Context Names
List the names and object identifiers of the application-contexts recognized or provided by this implementation.
Ref. Application-Context Name Object Identifier
i
A.5 Roles Supported
D
Ref. I
1 Requester 0 ( 1
2 Responder 0 ( 1
0 ( I
3 Intermediary
NOTE - At least one role must be supported by an implementation.
A.6 ILL Service Types Supported
Ref. Service Type Requester Responder Intermediary
D I D I D
I
1 Loan 0 ( 1 0 ( 1 0 ( I
2 Copy/Non-returnable 0 ( 1 0 ( 1 0 ( I
( >
3 Locations 0 ( > 0 ( 1 0
0 ( 1 0 ( 1 0 ( 1
4 Estimate
0 ( I 0 ( 1 0 ( I
5 Responder-specific
5

---------------------- Page: 11 ----------------------

SIST ISO 10161-2:2013
IS0 10161=2:1997(E)
A7 . Transaction Types Supported
Requester Responder
Ref. Transaction Type Intermediary
D I D
I D I
-
m m
1 Simple ( I
( I ( >
2 Chained 0 0 0
( 1 ( ( 1
I
3 Partitioned 0 0 0
( > ( > ( 1
NOTES
For chained transactions, requester support implies the ability to permit chained transactions; responder support
implies the ability to send the SHIPPED message; intermediary support implies the ability to initiate chained
subtransactions.
For partitioned transactions, requester support implies the ability to permit partitioned transactions and to
interact with different parties for the processing and tracking phases of a transaction; responder support implies
the ability to send the SHIPPED message and to interact directly with the requester during the tracking phase of
the transaction; intermediary support implies the ability to initiate partitioned sub-transactions.
Implementation of the intermediary role implies support for at least one of the chained or partitioned transaction
types.
6

---------------------- Page: 12 ----------------------

SIST ISO 10161-2:2013
0 IS0 IS0 10161-2: 1997(E)
Section Three - Syntaxes
A% . Syntaxes
This section identifies the requirements for support of the various possible syntaxes associated with the ILL protocol.
Support for a particular syntax implies that an implementation is capable of generation and reception of
information defined by that syntax.
A.& 1 Abstract Syntaxes Supported
Indicate below what abstract syntaxes are supported by the implementation, Registered syntaxes may be
identified by citing the assigned object identifier; other syntaxes should be fully defined using ASN.l notation, if
appropriate, in an attachment.
Ref. Parameter D I
Abstract-Syntax Name Object Identifier
1 ILL-APDU m ill-apdus
( I 10 10161 2 1
2 responder-specific-service 0
( I
national-bibliography-no
3 0
( 1
4 system-no
0
( I
5 responder-specific-results 0
( I
(for reason-unfilled)
6 responder-specific-results 0
( 1
(for reason-lots-provided)
7 responder-specific-results 0
( I
(for reason-not-available)
8 responder-specific-results 0
( I
(for conditions)
9 responder-specific-results 0
( I
(for reason-will-supply))
10 supplemental-item- 0
( I
description

---------------------- Page: 13 ----------------------

SIST ISO 10161-2:2013
IS0 10161=2:1997(E)
A.8.2 Transfer Syntaxes
For each abstract syntax identified in section A.8.1, multiple transfer syntaxes are possible. Two transfer syntaxes for
ILL APDUs have been identified in the base standard, one based on ASN. 1 encoding rules (IS0 8825, W basic-
encoding”), and the other based on the EDIFACT syntax (IS0 9735).
For each abstract syntax name shown as supported in section A-8.1, state below which transfer syntax(es) is/are
supported.
Ref. Abstract Syntax Object Identifier Transfer Syntax Object Identifier D I
1,l ill-apdus 10 10161 2 1
basic-encoding 211 m ( I
1.2 ill-apdus 10 10161 2 1 EDIFACT-encoding
10 10161 3 1 0 ( I

---------------------- Page: 14 ----------------------

SIST ISO 10161-2:2013
IS0 10161=2:1997(E)
Section Four - Interlibrary Loan Protocol
Interlibrary Loan Application Services
A9 .
Except for optional APDUs, addressed in section A.9.2, support for an ILL service implies support for sending and/or
receiving the corresponding APDUs as appropriate,
NOTE - This section is cast in terms of services rather than APDUs because some mandatory services do not
necessarily result in the transfer of an APDU, For instance, it is mandatory for a responder to support the SHIPPED
service, but sending a Shipped APDlJ is optional. The protocol allows the most recent service and the current
state to be determined at any time by means of the Status-Query and Status-Or-Error-Report APDUs.
A.9.1 Support for Services
Service Requester Responder Intermediary
Ref.
D I D I D I
r-- I
1 ILL-REQUEST m m m
I ’ I I ( ) I I ( ) I I ( ) I
- -
2 FORWARD 0 0
( (
I I I I I I ) I I ) I
-
-
3 FORWARD-NOTIFICATION cl cl
( (
I I I I ) I I I I ) I
m
4 SHIPPED m ( m
( (
I I I I ) I I ) I I ) I
ILL-ANSWER m m m
5 ( (
C
I I I I ) I I ) I I 1 I
6 CONDITIONAL-REPLY m c2 m
( ( (
I I I I ) I I ) I I ) I
7 CANCEL 0 m m
( ( (
I I I I 1 I I 1 I I ) I
m
8 CANCEL-REPLY c3 m
( ( (
I I I I ) I I ) I I ) I
m
9 RECEIVED m m
( ( (
I I I I 1 I I 1 I I 1 I
RECALL c4 c4
10 ( c4
( (
I I I I ) I I 1 I I ) I
11 RETURNED c4 c4 c4
( ( (
I I I I -1 I I I I I I I
12 CHECKED-IN c4 c4 c4
( ( (
I I I I ) I I ) I I
c4
13 OVERDUE c4 c4
( ( (
I I I I 1 I I 1 I I 1 I
c5
14 RENEW ( c4 c4
I I I I I I I ( I I I ( I I
RENEW-ANSWER c6 c4
15 ( c4
( (
I I I I ) I I ) I I ) I
16 LOST m m m
( 1
( 1 ( I
17 DAMAGED 0 0 m
( I (
I ( I
18 MESSAGE 0 0 m
( I ( I
( I
19 STATUS-QUERY 0 0 m
( I ( I ( I
m
20 STATUS-OR-ERROR-REPORT m m
( I ( I
( I
0
21 EXPIRY ( I 0 m
( I ( I
Conditions
cl Support for the FORWARD-NOTIFICATION service is mandatory for requesters and intermediaries that support
permission-to-forward with the value “TRUE”; otherwise it is not applicable. See section A. 10.1, ref. 21.1,
c2 Support for the CONDITIONAL-REPLY service is mandatory for responders that support transaction-results with the
value “CONDITIONAL”; otherwise it is not applicable.
9

---------------------- Page: 15 ----------------------

SIST ISO 10161-2:2013
IS0 10161=2:1997(E) 0 IS0
c3 Support for the CANCEL-REPLY indication service is mandatory for requesters that support the CANCEL service;
otherwise it is not applicable.
c4 Support for the RECALL, RETURNED, CHECKED-IN, OVERDUE and RENEW-ANSWER services is mandatory for
implementations that support the “loan” service type; otherwise they are not applicable. See section A.6.
c5 Support for the RENEW service is optional for requesters that support the “loan” service type; otherwise it is not
applicable. See section A,6.
c6 Support for the RENEW-ANSWER service is mandatory for requesters that support the RENEW service; otherwise it
is not applicable.
NOTES
1. Invocation of the FORWARD service by a responder results in the transmission to the new responder of an ILL-
Request APDU with the forward-flag set to true and the transmission of a Forward-Notification APDU to the
requester. The FORWARD-NOTIFICATION service is an indication service only and is only supported in the
requester role.
2. The Shipped, Received, Returned and Checked-In APDUs are optional; they need not be sent even though the
corresponding services are invoked. See section A.9,2
A.9.2 Optional APDUs
This section requests information about the extent to which optional APDUs can be transmitted, and about the
extent to which the implementation requires the receipt of optional APDUs.
Note that it is never an error to send an optional APDU and that implementations must always be capable of
receiving an optional APDU. The issues are the extent to which an implementation is capable of sending them, and
to which an implementation requires the receipt of them.
A.9.2.1 Requester Role
Capabilities on Transmission
A.9.2.1 .l
Indicate the value(s) transmitted for each of the parameters of the data type Requester-Optional-Messages-Type.
Ref. Parameter Value
1 can-send-RECEIVED TRUE/FALSE
2 can-send-RETURNED TRUE/FALSE
3 requester-SHIPPED
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .I.
3.1 - requires ( I
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .I.
3.2 - desires ( I
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . .1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.3 - neither
( I
4 requester-CHECKED-IN
. . .-.
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.1 - requires
( I
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .-.-.-. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.2 - desires ( I
. . .-.-.
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .-.-.-.--.------.
4.3 - neither ( 1
10

---------------------- Page: 16 ----------------------

SIST ISO 10161-2:2013
IS0 10161=2:1997(E)
0 IS0
A.9.2.1.2 Requirements on Receipt
indicate the value(s) supported on receipt for each parameter of the data type Responder-Optional-Messages-
Type*
Value
Ref. Parameter
TRUE/FALSE
1 can-send-SHIPPED
2 Can-send-CHECKED-IN TRUE/FALSE
3 responder-RECEIVED
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .---.--.----.-.-.
3.1 - requires
( I
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .-.-.---.---.--.--------.
3.2 - desires 1
(
. .
...