ISO 10161-1:1997
(Main)Information and documentation - Open Systems Interconnection - Interlibrary Loan Application Protocol Specification - Part 1: Protocol specification
Information and documentation - Open Systems Interconnection - Interlibrary Loan Application Protocol Specification - Part 1: Protocol specification
Information et documentation — Interconnexion de systèmes ouverts (OSI) — Spécification du protocole d'application pour les prêts entre bibliothèques — Partie 1: Spécification du protocole
Informatika in dokumentacija – Skupina za povezovanje odprtih sistemov – Specifikacija aplikacijskega protokola za medknjižnično izposojo – 1. del: Specifikacija protokola
General Information
Relations
Frequently Asked Questions
ISO 10161-1:1997 is a standard published by the International Organization for Standardization (ISO). Its full title is "Information and documentation - Open Systems Interconnection - Interlibrary Loan Application Protocol Specification - Part 1: Protocol specification". This standard covers: Information and documentation - Open Systems Interconnection - Interlibrary Loan Application Protocol Specification - Part 1: Protocol specification
Information and documentation - Open Systems Interconnection - Interlibrary Loan Application Protocol Specification - Part 1: Protocol specification
ISO 10161-1:1997 is classified under the following ICS (International Classification for Standards) categories: 35.240.30 - IT applications in information, documentation and publishing. The ICS classification helps identify the subject area and facilitates finding related standards.
ISO 10161-1:1997 has the following relationships with other standards: It is inter standard links to ISO 10161-1:1997/Amd 1:2002, ISO 10161-1:1997/Amd 2:2002, ISO 10161-1:2014, ISO 10161-1:1993; is excused to ISO 10161-1:1997/Amd 1:2002, ISO 10161-1:1997/Amd 2:2002. Understanding these relationships helps ensure you are using the most current and applicable version of the standard.
You can purchase ISO 10161-1:1997 directly from iTeh Standards. The document is available in PDF format and is delivered instantly after payment. Add the standard to your cart and complete the secure checkout process. iTeh Standards is an authorized distributor of ISO standards.
Standards Content (Sample)
INTERNATIONAL Is0
STANDARD 10161-1
Second edition
1997-06-I 5
Information and documentation - Open
Systems Interconnection - Interlibrary
Loan Application Protocol Specification -
Part 1:
Protocol specification
Information et documentation - lnterconnexion de syst&mes ouvefls
(OH) - Spkification du protocole d’application pour les pr6ts entre
biblioth&ques -
Partie 1: Spkification du protocole
Reference number
IS0 10161-1:1997(E)
ISO10161-1:1997(E)
Contents
1 SCOPE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
2 NORMATIVE REFERENCES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3 DEFINITIONS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . .*. 2
3.1 REFERENCE MODEL DEFINITIONS
3.2 ABSTRACT SYNTAX NOTATION ONE DEFINITIONS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . .~.“. 3
3.3 PRESENTATION SERVICE DEFINITION
3.4 APPLICATION LAYER STRUCTURE DEFINITIONS . . . . . . . . . . . . . . . . . . . . . . .*.
3.5 SERVICE CONVENTION DEFINITIONS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
3.6 ILL DEFINITIONS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4 ABBREVIATIONS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5 OVERVIEW OF THE PROTOCOL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .*.***.**. 10
5.1 SERVICE PROVISION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .~.
5.2 SUPPORTING SERVICES ASSUMED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.3 MODEL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .~.
6 ILL APDUS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7 TRANSACTION INFORMATION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
7.1 TRANSACTION IDENTIFICATION . . . . . . . . . . . . . . .*.
7.2 PROTOCOL STATES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
7.2.1 Requester States
7.2.2 Responder States . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
7.2.3 Terminal States
7.2.4 Intermediary States . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7.3 PROTOCOL VARIABLES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
7.4 EXPIRY TIMER . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7.5 REQUEST INFORMATION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
7.5.1 System-id . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7.6 HISTORY INFORMATION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .~.~. 15
............................................................................................................................................ 16
8 ELEMENTS OF PROCEDURE
8.1 EVENTS AND ACTIONS . 16
............................................................................................................................................................. 16
8.1.1 Requester Events
8.1.2 Requester Actions . 17
8.1.3 Responder Events . 18
.......................................................................................................................................................... 19
8.1.4 Responder Actions
8.1.5 Intermediary Events and Actions . 20
8.2 PROCEDURAL RULES FOR ALL PARTIES .
8.2.1 Sending and Receiving APDUs . 20
8.2.2 Transaction Phases .
8.2.3 Optional Messages . 20
8.2.4 Send-to-list .
8.2.5 Already-tried-list . 21
........................................................................................................................................................
8.2.6 Control of Renewals 22
8.2.7 APDU Sequence Validation . 22
8.2.8 Repeated APDUs . 22
8.2.9 Retries . 23
8.2.10 Transaction Expiry . 23
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.
International Organization for Standardization
Case postale 56 l Cl-I-1 211 Geneve 20 l Switzerland
Internet central @ iso.ch
c=ch; a=40Onet; p=iso; o=isocs; s=central
x.400
Printed in Switzerland
@ IS0 IS0 10161=1:1997(E)
8.2.11 Transaction Cancellation .
8.2.12 Lifetime of ILL-Transaction Information . 24
................................................................................................................................................................. 24
8.2.13 Protocol Errors
8.2.14 Rules for Extensibility .
8.2.15 Responder-specific Information . 24
........................................................................................................................................... 25
8.2.16 Account-number Information
8.2.17 Supplemental-item-description . 25
8.2.18 Send Message . 25
8.3 PROCEDURAL RULES FOR INTERMEDIARIES . 25
................................................................................................................................................... 25
8.3.1 Transaction Forwarding
8.3.2 Transaction Chaining .
8.3.3 Transaction Partitioning . 26
8.3.4 Mixed Forwarding, Chaining and Partitioning . 27
9 ABSTRACT SYNTAX .
9.1 ASN. 1 SPECIFICATION OF ILL APDUs . 28
...................................................................................................................................................................... 29
9.1.1 ILL APDUs
9.1.2 Types . 36
10 CONFORMANCE . 48
10.1 STATIC CONFORMANCE . 48
10.2 DYNAMIC CONFORMANCE . 48
10.3 PROTOCOLIMPLEMENTATIONCONFORMANCESTATEMENTREQUIREMENTS . 49
Annexes
A ILL STATE TABLES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
. . . . . .“.=. 79
B TRANSFER SYNTAX
C OBJECT IDENTIFIERS ASSIGNED IN THIS PART OF IS0 10161 AND REGISTRATION REQUIREMENTS . . . . . . . . 102
D REGISTRATION PROCEDURES FOR ILL EXTERNAL DATA TYPE DEFINITIONS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103
E EXAMPLE OF ILL EXTERNAL DATA TYPE DEFINITION REGISTER ENTRY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
F USE OF SUPPORTING SERVICES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106
G INVOCATION OF EXTERNAL DOCUMENT DELIVERY SERVICES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108
H BIBLIOGRAPHY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109
. . .
III
@IS0
IS0 10161=1:1997(E)
Foreword
IS0 (the International Organization for Standardization) is a worldwide federation of national standards bodies (IS0 member
bodies). The work of preparing International 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 1- 1 was prepared by Technical Committee ISO/TC 46, Information and Documentation,
Subcommittee SC 4, Computer applications in information and documentation.
This second edition cancels and replaces the first edition (IS0 10 16 l-l : 1993), which has been technically revised. It includes
amendments specified in IS0 10161, DAM 1 and the corrections specified in Defect Reports l-23.
IS0 10 16 1 consists of the following parts, under the general title Information and documentation - open Systems
Interconnection - Interlibrary Loan Application Protocol Specification:
Part I: Protocol specification
Part 2: Protocol implementation conformance statement (PICS) proforma
Annexes A to D form an integral part of this part of IS0 1016 1. Annexes E to H are for information only.
iv
@ IS0 IS0 10161-1:1997(E)
Introduction
This part of IS0 10 16 1 is one of a set of International Standards produced to facilitate the interconnection of computer systems.
It is related to other International Standards in the set as defined by the Reference Model for Open Systems Interconnection
(IS0 7498). The Reference Model subdivides the area of standardization for interconnection into a series of layers of
specification, each of manageable size.
The aim of Open Systems Interconnection is to allow, with a minimum of technical agreement outside the interconnection
standards, the interconnection of computer systems:
a. from different manufacturers,
b. under different managements,
c. of different levels of complexity,
d. of different ages.
This part of IS0 10 16 1 provides a protocol specification for Interlibrary Loan (ILL) communication. The ILL protocol operates
in the Application Layer and allows the parties involved in an ILL-transaction to progress through the ILL-transaction in an
orderly and defined way.
The ILL protocol has been designed to support the ILL services defined in IS0 10 160, the ILL Application Service Definition,
which generally requires invocation of external delivery services to fulfill an ILL request. The ILL protocol carries information
that permits both automatic and operator-mediated invocation of external delivery services.
This part of IS0 10 16 1 is one of a number of related standards supporting the interconnection of library systems. These
standards can be used by themselves or in a cooperative manner to support library applications requiring a mixture of
communications services. For example, IS0 23950, which supports remote access to bibliographic databases, could be used in
conjunction with the ILL protocol to obtain item identification information. The control and management of interactions among
such bibliographic applications are local matters that are outside the scope of this International Standard.
Security and accounting issues as they relate to ILL operations are for further study.
The specification technique used in this part of IS0 1016 1 is consistent with techniques used in defining other OS1 protocols.
Within most of this document, the technique is self-explanatory. The Abstract Syntax of the ILL Application Protocol Data
Units (APDUs) is defined by means of the ASN.l specification technique specified in ISO/IEC 8824.
This part of IS0 1016 1 contains eight annexes. Annexes A to D are normative. Annex A specifies the the state tables for the
ILL protocol. Annex B specifies the encoding rules for generating a transfer syntax compatible with EDIFACT as defined in
IS0 9735. Annex C specifies the object identifiers assigned in this part of IS0 10 16 1 and registration requirements. Annex D
defines the registration procedures for ILL EXTERNAL data type definitions. Annex E is an example of an ILL EXTERNAL
data type registry entry. Annex F describes the possible mappings of this protocol onto supporting services. Annex G describes
possible methods of using a document delivery protocol in conjunction with the ILL protocol. Annex H is a bibliography.
This page intentionally left blank
~~~~~~
IS0 10161-1:1997(E)
INTERNATIONAL STANDARD @ IS0
Information and documentation - Open Systems
Interconnection - Interlibrary Loan Application
- Part 1: Protocol specification
Protocol Specification
1 Scope
This part of IS0 10 16 1 defines the protocol for an ILL application-service-element (ASE). It specifies the behaviour which
must be exhibited by a system in order to take part in the provision of the IS0 interlibrary loan service.
It provides a formal statement of the rules of behaviour of each of the two or more entities participating in an ILL transaction. It
specifies:
a. the actions to be taken on receiving request service primitives issued by an ILL service-user;
b. the actions to be taken on receiving application-protocol-data-units (APDUs);
c. the actions to be taken as a result of events within the local system.
It provides a specification (in clause 9) of the abstract syntax required to convey the ILL protocol APDUs.
It states the conformance requirements to be met by implementors of this protocol (in clause 10).
The scope of the ILL protocol is restricted to the interconnection of systems; it does not specify or restrict the possible
implementation of interfaces within a computer system. Computer systems may range from stand-alone workstations to
mainframes.
This part of IS0 10 16 1 is intended for use by libraries, information utilities such as union catalogue centres, and any other
system which processes bibliographic information. These systems may participate in an interlibrary loan transaction in the role
of requester (i.e. an initiator of ILL requests), responder (i.e. a provider of bibliographic material or information) and/or
intermediary (i.e. an agent that acts on behalf of a requester to find suitable responders).
Various interworking topologies are supported, ranging from simple two-party interactions, to multi-party interactions.
2 Normative references
The following standards contain provisions which, through reference in this text, constitute provisions of this part of
IS0 1016 1. At the time of publication, the editions indicated were valid. All standards are subject to revision, and parties to
agreeements based on this part of IS0 10 16 1 are encouraged to investigate the possibility of applying the most recent editions
of the standards indicated below. Members of IEC and IS0 maintain registers of currently valid International Standards.
Information technology - IS0 7-bit coded character set for information interchange.
ISO/IEC 646: 199 1,
NOTE - ISO/IEC 646: 199 1 supersedes IS0 646: 1983. However, when this part of IS0 10 16 1 was under development, the previous
edition was valid and this part of IS0 10161 is therefore based on this edition, which is given below.
646: 1983, Information Processing Systems - IS0 7-bit coded character set for information interchange.
IS0
Information and documentation - International standard book numbering (ISBN).
IS0 2108: 1992,
NOTE - IS0 2 108: 1992 supersedes IS0 2 108: 1978. However, when this part of IS0 10 16 1 was under development, the previous
edition was valid and this part of IS0 10161 is therefore based on this edition, which is given below.
IS0 2108: 1978, Documentation - International standard book numbering (ISBN).
IS0 2709: 1996, Information and documentation - Format for Information Ekhnge.
NOTE - IS0 2709: 1996 supersedes IS0 2709: 198 1. However, when this part of IS0 10 16 1 was under development, the previous
edition was valid and this part of IS0 10 161 is therefore based on this edition, which is given below.
IS0 Documentation - Format for bibliographic information interchange on magnetic tape.
2709: 1981,
IS0 3297: 1986, Documentation - International standard serial numbering (ISSN).
@ IS0
IS0 10161=1:1997(E)
IS0 421711995, Codes for the representation of currencies and funds.
NOTE - IS0 42 17: 1995 supersedes IS0 42 17: 198 1. However, when this part of IS0 10 16 1 was under development, the previous
edition was valid and this part of IS0 10161 is therefore based on this edition, which is given below.
IS0 4217:1981, Codes for the representation of currencies and funds.
ISO/IEC 7498-l : 1994, Information technology - Open Systems Interconnection - Basic Reference Model: The Basic Model.
IS0 7498-2: 1989, Information processing systems - Open Systems Interconnection - Basic Reference Model - Part 2: Security Architecture.
IS0 Information processing systems - Open Systems Interconnection - Basic Reference Model - Part 3: Naming and addressing.
7498-3 : 1989,
Open Systems Interconnection - Basic Reference Model - Part 4: Managementframework.
ISO/IEC 74984: 1989, Information processing systems -
NOTE - ISO/IEC 7498-l) IS0 7498-2, IS0 7498-3 and ISO/IEC 7498-4 supersede IS0 7498: 1984. However, when this part of
IS0 10161 was under development, the previous edition was valid and this part of IS0 10 16 1 is therefore based on this edition,
which is given below.
IS0 7498: 1984, Information processing systems - Open Systems Interconnection - Basic Reference Model.
IS0 8601: 1988, Data elements and interchange formats - Information interchange - Representation of dates and times.
ISO/IEC Information technology - Open Systems Interconnection - Presentation service definition.
8822: 1994,
NOTE - ISO/IEC 8822: 1994 supersedes IS0 8822: 1988.’ However, when this part of IS0 10 16 1 was under development, the
previous edition was valid and this part of IS0 10161 is therefore based on this edition, which is given below.
Open Systems Interconnection - Connection Oriented Presentation Service Definition.
IS0 8822: 1988, Information processing systems -
- Specification of Abstract Syntax Notation One (ASN. I).
ISO/IEC 8824: 1990, Information technology - Open Systems Interconnection
ISO/IEC 8825: 1990, Information technology - Open Systems Interconnection - Specification of Basic Encoding Rules for Abstract Syntax Notation One
(ASN. I).
IS0 9735: 1988, Electronic data interchange for administration, commerce and transport (EDIFACT) - Application Level Syntax Rules.
ISO/IEC Information technology - Open Systems Interconnection - Procedures for the operation of OSI Registration Authorities - Part I:
9834-l: 1993,
General procedures.
Procedures for the operation of OSI Registration Authorities - Part 2:
ISO/IEC 9834-2: 1993, Information technology - Open Systems Interconnection -
Registration procedures for OSI document types.
Text Interchange Systems (MOTIS) - Part 4: Message Transfer
ISO/IEC 10021-4:1990, Information Technology - Text Communication - Message-Oriented
System: Abstract Service Definition and Procedures.
IS0 10 160: 1997, Information and documentation - Open Systems Interconnection - Interlibrary Loan Application Service Definition.
3 Definitions
For the purposes of this part of IS0 10 16 1, the following definitions apply.
3.1 Reference Model Definitions
This part of IS0 10 16 1 is based on the concepts developed in IS0 7498: 1984 and makes use of the following terms found in it.
These terms are replicated here as a convenience to the reader.
Application Layer: The seventh and highest layer in the Reference Model for Open Systems Interconnection (ON); it
3.1.1
serves as the window between correspondent application-processes which are using the OS1 to exchange meaningfkl
information.
3.1.2 application-entity: The aspects of an application-process pertinent to OSI.
application-process: An element within a real open system which performs the information processing for a particular
3.1.3
application.
3.1.4 application-protocol-data-unit: A unit of data specified in an application-protocol and consisting of application-
protocol-information and possibly application-user-data.
application-service-element: That part of an application-entity which provides an OS1 environment capability, using
3.1.5
underlying services when appropriate.
@ IS0 IS0 10161=1:1997(E)
3.1.6 (N)-service: A capability of the (N)-layer and the layers beneath it, which is provided to (N+l)-entities at the
boundary between the @Q-layer and the (N+l)-layer.
NOTE - An application-service does not provide a capability to higher layer entities, but rather to application-processes.
presentation-service: A capability of the Presentation Layer and the layers beneath it, which is provided to
3.1.7
application-entities at the boundary between the Presentation and the Application Layer.
3.1.8 transfer syntax: The concrete syntax used in the transfer of data between open systems.
3.2 Abstract Syntax Notation One Definitions
This part of IS0 10 16 1 makes use of the following terms defined in ISO/IEC 8824: 1990.
3.2.1 data type; type: A named set of values.
3.2.2 simple type: A type defined by directly specifying the set of its values.
3.2.3 structured type: A type defined by reference to one or more other types.
3.2.4 component type: One of the types referenced when defining a structured type.
3.2.5 value: A distinguished member of a set of values.
3.3 Presentation Service Definition
This part of IS0 1016 1 makes use of the following term defined in IS0 8822: 1988.
3.3.1 abstract syntax: Those aspects of the rules used in the formal specification of data which are independent of the
encoding technique to represent the data.
3.4 Application Layer Structure Definitions
This part of IS0 10 16 1 makes use of the following terms defined in ISO/IEC 9545: 1989.
3.4.1 application-association: A cooperative relationship between two application-entity-invocations for the purpose of
communication of information and coordination of their joint operation. This relationship is formed by the exchange
of application-protocol-control-information using the Presentation Service.
3.4.2 application-context: A set of rules shared in common by two application-entity-invocations governing their behavior
in order to enable their cooperative operation.
NOTE - An application-context is a shared conceptual schema for the universe of discourse for communication.
3.4.3 application-context-definition: The description of an application-context.
application-entity-invocation: A specific utilization of part or all of the capabilities of a given application-entity in
3.4.4
support of the communications requirements of an application-process-invocation.
application-process-invocation: A specific utilization of part or all of the capabilities of a given application-process
3.4.5
in support of a specific occasion of information processing.
3.5 Service Convention Definitions
This part of IS0 10161 makes use of the following terms defined in ISO/TR 8509: 1987.
3.5.1 indication primitive: A representation of an interaction in which a service-provider either:
indicates that it has, on its own initiative, invoked some procedure; or
a.
b. indicates that a procedure has been invoked by the service-user at the peer service-access-point.
3.5.2 non-confirmed service: A distinct part of the total (N)-service which does not result in an explicit confirmation from
the service-provider to the initiating service-user.
3.5.3 provider-initiated service: A distinct part of the total @)-service which is initiated by the service-provider rather
than the service-user.
3.5.4 request primitive: A representation of an interaction in which a service-user invokes some procedure.
3.5.5 service primitive: An abstract, implementation-independent representation of an interaction between service-user and
the service-provider.
3.5.6 service-provider: An abstract of the totality of those entities which provide a service to peer service-users.
3.5.7 service-user: An entity in a single open system that makes use of a service.
@ IS0
IS0 10161-l :1997(E)
3.6 ILL Definitions
For the purposes of this part of IS0 10 16 1, the following definitions apply to the ASN. 1 value reference names and values
which are associated with simple data types, as specified in clause 9. Of these definitions, the following are repetitions of those
found in IS0 8459-l : 1988:
author
call number
client identifier
client-status
country
edition
place-of-publication
post-office-box
postal-code
publisher
sponsoring body
street-and-number
title
transportation-mode
volume-issue
-
NOTE - volume-issue is defined here, but volume and issue are defined separately in IS0 8459-l : 1988.
3.6.1 account-number: The number of an account to which a credit or debit is made. A requester typically has been
assigned a separate account for each responder. (Variation of IS0 8459-l)
additional-no-letters: (additional-numbers-letters) A number or code identifying an item.
3.6.2
3.6.3 already-forwarded: Responder indication that an ILL request has already been forwarded.
already-tried-list: List of institutions which have been approached but were unable to supply requested item.
3.6.4
3.6.5 answer: A code representing a yes or no response.
3.6.6 at-bindery: Title is owned but the requested item is at the bindery.
3.6.7 author: Name of the person or corporate body responsible for the intellectual or artistic content of an item, including
composers, creators or originators of an item.
3.6.8 author-of-article: Author of an item which is a component part of another item.
3.6.9 badly-structured-APDU: The structure of a received APDU does not conform to the standard notation and encoding
defmed in IS0 8824 and 8825, or to the EDIFACT encoding defined in IS0 9735 and Annex B of this International
Standard. For example, a received APDU does not match its stated length.
being-processed-for-supply: Item is being retrieved, copied, and/or packaged for delivery.
3.6.10
3.6.11 call-number: Notation assigned to an item indicating its physical location in the owner institution.
can-send-CHECKED-IN: An indication by the responder that it is capable of supplying the CHECKED-IN APDU.
3.6.12
3.6.13 can-send-RECEIVED: An indication by the requester that it is capable of supplying the RECEIVED APDU.
3.6.14 can-send-RETURNED: An indication by the requester that it is capable of supplying the RETURNED APDU.
can-send-SHIPPED: An indication by the responder that it is capable of supplying the SHIPPED APDU.
3.6.15
3.6.16 cannot-send-onward: An intermediary is unable to send on a request due to communication problems.
chargeable-units: The number of units supplied for which there is a charge.
3.6.17
3.6.18 charges: The responder’s charges for the provision of the requested service.
3.6.19 city: A phrase used to identify a city, town or village. (Variation of IS0 8459-l)
client-identifier: Number or code used to identify the client uniquely.
3.6.20
3.6.21 client-name: Name of the person or institution for which the item has been requested. (Variation of ISO 8459-l)
3.6.22 client-signature-required: Responder’s stipulation that the client must sign the signature sheet enclosed with the item.
3.6.23 client-status: Professional level or position of the client.
conditions: A code used to indicate the conditions under which an item may be borrowed.
3.6.24
3.6.25 copyright-compliance: Requester notation indicating the applkable copyright regulations or laws to which the
requester is adhering.
correlation-information: Information that is used to correlate an error report with the service request to which the
3.6.26
report relates.
cost: The amount asked, taken or billed by the responder for the service supplied.
3.6.27
cost-estimate: Estimate of the cost to provide the service requested.
3.6.28
@ IS0 IS0 10161=1:1997(E)
cost-exceeds-limit: Responder indication that the minimum cost to supply the request is greater than the amount authorized.
3.6.29
3.6.30 country: A phrase used to identify a country.
3.6.31 currency-code: A code identifying the currency of an amount, according to IS0 42 17: 198 1.
3.6.32 current-state: A code identifying the state of the ILL-transaction.
3.6.33 date-checked-in: The date on which a loaned item is received back by the responder.
date-due: The date by which the loaned item should be returned to the responder. Note that this should reflect the
3.6.34
latest date-due.
date-for-reply: The date by which a reply should be returned to the responder.
3.6.35
date-of-last-transition: The date on which the last state transition occurred.
3.6.36
3.6.37 date-of-most-recent-service: The date when the most recent service event occurred at the system providing the status
report. This is either a service invoked by the system providing the status report or a service reflected in a received APDU.
3.6.38 date-of-service: The date on which a service concerning an ILL-transaction is invoked.
3.6.39 date-received: The date when the item is received by the requester.
3.6.40 date-requested: The date the ILL request was initiated by the requester.
date-returned: The date when the item was returned to the responder.
3.6.41
3.6.42 date-shipped: The date when the item was shipped to the requester.
3.6.43 delivery-service: The delivery service or method used in transporting a requested item. Either physical or electronic
delivery may be used.
desired-due-date: The proposed due date for the renewed loan.
3.6.44
3.6.45 duplicate-transaction-id: The transaction-id value of an ILL-REQUEST APDU is an illegal duplicate, i.e. the value
is identical to one for an existing ILL-REQUEST received from the same requester.
3.6.46 edition: All the copies of an item produced from one master copy or substantially the same type image, having the same
contents, and, in the case of non-book materials, issued by a particular publishing agency or group of such agencies.
3.6.47 electronic-delivery: Delivery of an electronic representation of a document via a telecommunications-based data
transfer mechanism. Delivery via transfer of a tangible magnetic or optical medium is excluded.
3.6.48 estimated-date-available: Date when an item placed on hold is expected to become available.
expiry-date: The date on which an ILL-transaction expires automatically.
3.6.49
3.6.50 expiry-flag: An indication of whether an expiry date has been set for an ILL-transaction, and if so, whether that date is
the “need-before-date”, or some other date.
extended-postal-delivery-address: Additional information in the postal address necessary to identify the exact point
3.6.51
of delivery, e.g. room and floor number in a large building.
final-responder: Institution which supplies a requested item. This term is used when it is necessary to distinguish
3.6.52
between the responder of an ILL-transaction and the responder of an ILL-sub-transaction.
3.6.53 forward-flag: An indication whether a received ILL-REQUEST has been forwarded from an intermediary.
forward-note: Note added to the ILL-REQUEST by the responder when it is forwarded to a new responder.
3.6.54
3.6.55 general-problem: Code indicating a general problem with a received APDU detected by the ILL service-provider that
is not related to either the transaction-id or permissible state transitions.
ILL-APDU-type: Code identifying the type of APDU received.
3.6.56
3.6.57 ILL-service-type: A code for the type of ILL service requested. These can be listed in a preferred order.
3.6.58 ILL-transaction: A single complete instance of the whole ILL cycle, including all of the actions, service primitives, and
messages involved from the initial ILL-Request until the cycle is concluded, as with the return of the requested material.
3.6.59 in-process: Item has been received but is not yet ready for use.
in-use/on-loan: Item is owned but is currently being used by a client or is on loan to another institution.
3.6.60
3.6.61 initial-requester: Person or institution which initiates an ILL-transaction; this term is used when it is necessary to
distinguish between the requester of an ILL-transaction and the requester of an ILL sub-transaction.
initial-requester-address: Information identifying the telecommunications service and address by which the initial-
3.6.62
requester can be reached.
initiator-of-most-recent service: Identification information of the requester or responder who initiated the most
3.6.63
recent service.
institution-symbol: Number(s), letter(s) or a code serving to ident@ unambiguously and in an abbreviated format a library,
3.6.64
institution or corporation that is participating in an ILL-transaction, e.g. institutions national union catalogue symbol.
3.6.65 insured-for: Notation of the amount of insurance purchased against loss or damage of items.
@ is0
IS0 10161-1:1997(E)
3.6.66 intermediary-id: Identification information of an ILL-transaction intermediary.
3.6.67 intermediary-problem: Code indicating that the intermediary has a problem in processing the request.
invalid-transaction-id: The transaction-id value of an ILL-REQUEST is invalid, e.g. the value violates the assignment
3.6.68
rules of this part of IS0 10 16 1, or an unknown person-or-institution symbol or person-or-institution-name is encountered.
3.6.69 ISBN: The International Standard Book Number assigned to a monograph as prescribed by IS0 3297: 1986.
3.6.70 ISSN: The International Standard Serial Number assigned to a serial title as prescribed by IS0 2108: 1978.
3.6.71 item-type: A code identifying the bibliographic form in which the item has been produced.
3.6.72 lacking: The title is owned but not the component part or pages requested.
3.6.73 lacks-copyright-compliance: Compliance with applicable copyright regulations or laws must be indicated before
copying can be done.
level-of-service: A code that indicates the level of search detail required or the duration of time within which a
3.6.74
response is required. Note that this code reflects regional or national conventions.
3.6.75 library-use-only: Responder indication that the item may not be removed from the requesting institution.
location-address: Information identifying the telecommunication service and address or the postal address by which
3.6.76
the institution that owns the item can be reached.
3.6.77 location-id: The symbol or name of the institution that owns the requested item.
3.6.78
...
INTERNATIONAL Is0
STANDARD 10161-1
Second edition
1997-06-I 5
Information and documentation - Open
Systems Interconnection - Interlibrary
Loan Application Protocol Specification -
Part 1:
Protocol specification
Information et documentation - lnterconnexion de syst&mes ouvefls
(OH) - Spkification du protocole d’application pour les pr6ts entre
biblioth&ques -
Partie 1: Spkification du protocole
Reference number
IS0 10161-1:1997(E)
ISO10161-1:1997(E)
Contents
1 SCOPE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
2 NORMATIVE REFERENCES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3 DEFINITIONS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . .*. 2
3.1 REFERENCE MODEL DEFINITIONS
3.2 ABSTRACT SYNTAX NOTATION ONE DEFINITIONS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . .~.“. 3
3.3 PRESENTATION SERVICE DEFINITION
3.4 APPLICATION LAYER STRUCTURE DEFINITIONS . . . . . . . . . . . . . . . . . . . . . . .*.
3.5 SERVICE CONVENTION DEFINITIONS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
3.6 ILL DEFINITIONS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4 ABBREVIATIONS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5 OVERVIEW OF THE PROTOCOL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .*.***.**. 10
5.1 SERVICE PROVISION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .~.
5.2 SUPPORTING SERVICES ASSUMED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.3 MODEL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .~.
6 ILL APDUS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7 TRANSACTION INFORMATION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
7.1 TRANSACTION IDENTIFICATION . . . . . . . . . . . . . . .*.
7.2 PROTOCOL STATES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
7.2.1 Requester States
7.2.2 Responder States . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
7.2.3 Terminal States
7.2.4 Intermediary States . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7.3 PROTOCOL VARIABLES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
7.4 EXPIRY TIMER . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7.5 REQUEST INFORMATION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
7.5.1 System-id . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7.6 HISTORY INFORMATION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .~.~. 15
............................................................................................................................................ 16
8 ELEMENTS OF PROCEDURE
8.1 EVENTS AND ACTIONS . 16
............................................................................................................................................................. 16
8.1.1 Requester Events
8.1.2 Requester Actions . 17
8.1.3 Responder Events . 18
.......................................................................................................................................................... 19
8.1.4 Responder Actions
8.1.5 Intermediary Events and Actions . 20
8.2 PROCEDURAL RULES FOR ALL PARTIES .
8.2.1 Sending and Receiving APDUs . 20
8.2.2 Transaction Phases .
8.2.3 Optional Messages . 20
8.2.4 Send-to-list .
8.2.5 Already-tried-list . 21
........................................................................................................................................................
8.2.6 Control of Renewals 22
8.2.7 APDU Sequence Validation . 22
8.2.8 Repeated APDUs . 22
8.2.9 Retries . 23
8.2.10 Transaction Expiry . 23
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.
International Organization for Standardization
Case postale 56 l Cl-I-1 211 Geneve 20 l Switzerland
Internet central @ iso.ch
c=ch; a=40Onet; p=iso; o=isocs; s=central
x.400
Printed in Switzerland
@ IS0 IS0 10161=1:1997(E)
8.2.11 Transaction Cancellation .
8.2.12 Lifetime of ILL-Transaction Information . 24
................................................................................................................................................................. 24
8.2.13 Protocol Errors
8.2.14 Rules for Extensibility .
8.2.15 Responder-specific Information . 24
........................................................................................................................................... 25
8.2.16 Account-number Information
8.2.17 Supplemental-item-description . 25
8.2.18 Send Message . 25
8.3 PROCEDURAL RULES FOR INTERMEDIARIES . 25
................................................................................................................................................... 25
8.3.1 Transaction Forwarding
8.3.2 Transaction Chaining .
8.3.3 Transaction Partitioning . 26
8.3.4 Mixed Forwarding, Chaining and Partitioning . 27
9 ABSTRACT SYNTAX .
9.1 ASN. 1 SPECIFICATION OF ILL APDUs . 28
...................................................................................................................................................................... 29
9.1.1 ILL APDUs
9.1.2 Types . 36
10 CONFORMANCE . 48
10.1 STATIC CONFORMANCE . 48
10.2 DYNAMIC CONFORMANCE . 48
10.3 PROTOCOLIMPLEMENTATIONCONFORMANCESTATEMENTREQUIREMENTS . 49
Annexes
A ILL STATE TABLES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
. . . . . .“.=. 79
B TRANSFER SYNTAX
C OBJECT IDENTIFIERS ASSIGNED IN THIS PART OF IS0 10161 AND REGISTRATION REQUIREMENTS . . . . . . . . 102
D REGISTRATION PROCEDURES FOR ILL EXTERNAL DATA TYPE DEFINITIONS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103
E EXAMPLE OF ILL EXTERNAL DATA TYPE DEFINITION REGISTER ENTRY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
F USE OF SUPPORTING SERVICES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106
G INVOCATION OF EXTERNAL DOCUMENT DELIVERY SERVICES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108
H BIBLIOGRAPHY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109
. . .
III
@IS0
IS0 10161=1:1997(E)
Foreword
IS0 (the International Organization for Standardization) is a worldwide federation of national standards bodies (IS0 member
bodies). The work of preparing International 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 1- 1 was prepared by Technical Committee ISO/TC 46, Information and Documentation,
Subcommittee SC 4, Computer applications in information and documentation.
This second edition cancels and replaces the first edition (IS0 10 16 l-l : 1993), which has been technically revised. It includes
amendments specified in IS0 10161, DAM 1 and the corrections specified in Defect Reports l-23.
IS0 10 16 1 consists of the following parts, under the general title Information and documentation - open Systems
Interconnection - Interlibrary Loan Application Protocol Specification:
Part I: Protocol specification
Part 2: Protocol implementation conformance statement (PICS) proforma
Annexes A to D form an integral part of this part of IS0 1016 1. Annexes E to H are for information only.
iv
@ IS0 IS0 10161-1:1997(E)
Introduction
This part of IS0 10 16 1 is one of a set of International Standards produced to facilitate the interconnection of computer systems.
It is related to other International Standards in the set as defined by the Reference Model for Open Systems Interconnection
(IS0 7498). The Reference Model subdivides the area of standardization for interconnection into a series of layers of
specification, each of manageable size.
The aim of Open Systems Interconnection is to allow, with a minimum of technical agreement outside the interconnection
standards, the interconnection of computer systems:
a. from different manufacturers,
b. under different managements,
c. of different levels of complexity,
d. of different ages.
This part of IS0 10 16 1 provides a protocol specification for Interlibrary Loan (ILL) communication. The ILL protocol operates
in the Application Layer and allows the parties involved in an ILL-transaction to progress through the ILL-transaction in an
orderly and defined way.
The ILL protocol has been designed to support the ILL services defined in IS0 10 160, the ILL Application Service Definition,
which generally requires invocation of external delivery services to fulfill an ILL request. The ILL protocol carries information
that permits both automatic and operator-mediated invocation of external delivery services.
This part of IS0 10 16 1 is one of a number of related standards supporting the interconnection of library systems. These
standards can be used by themselves or in a cooperative manner to support library applications requiring a mixture of
communications services. For example, IS0 23950, which supports remote access to bibliographic databases, could be used in
conjunction with the ILL protocol to obtain item identification information. The control and management of interactions among
such bibliographic applications are local matters that are outside the scope of this International Standard.
Security and accounting issues as they relate to ILL operations are for further study.
The specification technique used in this part of IS0 1016 1 is consistent with techniques used in defining other OS1 protocols.
Within most of this document, the technique is self-explanatory. The Abstract Syntax of the ILL Application Protocol Data
Units (APDUs) is defined by means of the ASN.l specification technique specified in ISO/IEC 8824.
This part of IS0 1016 1 contains eight annexes. Annexes A to D are normative. Annex A specifies the the state tables for the
ILL protocol. Annex B specifies the encoding rules for generating a transfer syntax compatible with EDIFACT as defined in
IS0 9735. Annex C specifies the object identifiers assigned in this part of IS0 10 16 1 and registration requirements. Annex D
defines the registration procedures for ILL EXTERNAL data type definitions. Annex E is an example of an ILL EXTERNAL
data type registry entry. Annex F describes the possible mappings of this protocol onto supporting services. Annex G describes
possible methods of using a document delivery protocol in conjunction with the ILL protocol. Annex H is a bibliography.
This page intentionally left blank
~~~~~~
IS0 10161-1:1997(E)
INTERNATIONAL STANDARD @ IS0
Information and documentation - Open Systems
Interconnection - Interlibrary Loan Application
- Part 1: Protocol specification
Protocol Specification
1 Scope
This part of IS0 10 16 1 defines the protocol for an ILL application-service-element (ASE). It specifies the behaviour which
must be exhibited by a system in order to take part in the provision of the IS0 interlibrary loan service.
It provides a formal statement of the rules of behaviour of each of the two or more entities participating in an ILL transaction. It
specifies:
a. the actions to be taken on receiving request service primitives issued by an ILL service-user;
b. the actions to be taken on receiving application-protocol-data-units (APDUs);
c. the actions to be taken as a result of events within the local system.
It provides a specification (in clause 9) of the abstract syntax required to convey the ILL protocol APDUs.
It states the conformance requirements to be met by implementors of this protocol (in clause 10).
The scope of the ILL protocol is restricted to the interconnection of systems; it does not specify or restrict the possible
implementation of interfaces within a computer system. Computer systems may range from stand-alone workstations to
mainframes.
This part of IS0 10 16 1 is intended for use by libraries, information utilities such as union catalogue centres, and any other
system which processes bibliographic information. These systems may participate in an interlibrary loan transaction in the role
of requester (i.e. an initiator of ILL requests), responder (i.e. a provider of bibliographic material or information) and/or
intermediary (i.e. an agent that acts on behalf of a requester to find suitable responders).
Various interworking topologies are supported, ranging from simple two-party interactions, to multi-party interactions.
2 Normative references
The following standards contain provisions which, through reference in this text, constitute provisions of this part of
IS0 1016 1. At the time of publication, the editions indicated were valid. All standards are subject to revision, and parties to
agreeements based on this part of IS0 10 16 1 are encouraged to investigate the possibility of applying the most recent editions
of the standards indicated below. Members of IEC and IS0 maintain registers of currently valid International Standards.
Information technology - IS0 7-bit coded character set for information interchange.
ISO/IEC 646: 199 1,
NOTE - ISO/IEC 646: 199 1 supersedes IS0 646: 1983. However, when this part of IS0 10 16 1 was under development, the previous
edition was valid and this part of IS0 10161 is therefore based on this edition, which is given below.
646: 1983, Information Processing Systems - IS0 7-bit coded character set for information interchange.
IS0
Information and documentation - International standard book numbering (ISBN).
IS0 2108: 1992,
NOTE - IS0 2 108: 1992 supersedes IS0 2 108: 1978. However, when this part of IS0 10 16 1 was under development, the previous
edition was valid and this part of IS0 10161 is therefore based on this edition, which is given below.
IS0 2108: 1978, Documentation - International standard book numbering (ISBN).
IS0 2709: 1996, Information and documentation - Format for Information Ekhnge.
NOTE - IS0 2709: 1996 supersedes IS0 2709: 198 1. However, when this part of IS0 10 16 1 was under development, the previous
edition was valid and this part of IS0 10 161 is therefore based on this edition, which is given below.
IS0 Documentation - Format for bibliographic information interchange on magnetic tape.
2709: 1981,
IS0 3297: 1986, Documentation - International standard serial numbering (ISSN).
@ IS0
IS0 10161=1:1997(E)
IS0 421711995, Codes for the representation of currencies and funds.
NOTE - IS0 42 17: 1995 supersedes IS0 42 17: 198 1. However, when this part of IS0 10 16 1 was under development, the previous
edition was valid and this part of IS0 10161 is therefore based on this edition, which is given below.
IS0 4217:1981, Codes for the representation of currencies and funds.
ISO/IEC 7498-l : 1994, Information technology - Open Systems Interconnection - Basic Reference Model: The Basic Model.
IS0 7498-2: 1989, Information processing systems - Open Systems Interconnection - Basic Reference Model - Part 2: Security Architecture.
IS0 Information processing systems - Open Systems Interconnection - Basic Reference Model - Part 3: Naming and addressing.
7498-3 : 1989,
Open Systems Interconnection - Basic Reference Model - Part 4: Managementframework.
ISO/IEC 74984: 1989, Information processing systems -
NOTE - ISO/IEC 7498-l) IS0 7498-2, IS0 7498-3 and ISO/IEC 7498-4 supersede IS0 7498: 1984. However, when this part of
IS0 10161 was under development, the previous edition was valid and this part of IS0 10 16 1 is therefore based on this edition,
which is given below.
IS0 7498: 1984, Information processing systems - Open Systems Interconnection - Basic Reference Model.
IS0 8601: 1988, Data elements and interchange formats - Information interchange - Representation of dates and times.
ISO/IEC Information technology - Open Systems Interconnection - Presentation service definition.
8822: 1994,
NOTE - ISO/IEC 8822: 1994 supersedes IS0 8822: 1988.’ However, when this part of IS0 10 16 1 was under development, the
previous edition was valid and this part of IS0 10161 is therefore based on this edition, which is given below.
Open Systems Interconnection - Connection Oriented Presentation Service Definition.
IS0 8822: 1988, Information processing systems -
- Specification of Abstract Syntax Notation One (ASN. I).
ISO/IEC 8824: 1990, Information technology - Open Systems Interconnection
ISO/IEC 8825: 1990, Information technology - Open Systems Interconnection - Specification of Basic Encoding Rules for Abstract Syntax Notation One
(ASN. I).
IS0 9735: 1988, Electronic data interchange for administration, commerce and transport (EDIFACT) - Application Level Syntax Rules.
ISO/IEC Information technology - Open Systems Interconnection - Procedures for the operation of OSI Registration Authorities - Part I:
9834-l: 1993,
General procedures.
Procedures for the operation of OSI Registration Authorities - Part 2:
ISO/IEC 9834-2: 1993, Information technology - Open Systems Interconnection -
Registration procedures for OSI document types.
Text Interchange Systems (MOTIS) - Part 4: Message Transfer
ISO/IEC 10021-4:1990, Information Technology - Text Communication - Message-Oriented
System: Abstract Service Definition and Procedures.
IS0 10 160: 1997, Information and documentation - Open Systems Interconnection - Interlibrary Loan Application Service Definition.
3 Definitions
For the purposes of this part of IS0 10 16 1, the following definitions apply.
3.1 Reference Model Definitions
This part of IS0 10 16 1 is based on the concepts developed in IS0 7498: 1984 and makes use of the following terms found in it.
These terms are replicated here as a convenience to the reader.
Application Layer: The seventh and highest layer in the Reference Model for Open Systems Interconnection (ON); it
3.1.1
serves as the window between correspondent application-processes which are using the OS1 to exchange meaningfkl
information.
3.1.2 application-entity: The aspects of an application-process pertinent to OSI.
application-process: An element within a real open system which performs the information processing for a particular
3.1.3
application.
3.1.4 application-protocol-data-unit: A unit of data specified in an application-protocol and consisting of application-
protocol-information and possibly application-user-data.
application-service-element: That part of an application-entity which provides an OS1 environment capability, using
3.1.5
underlying services when appropriate.
@ IS0 IS0 10161=1:1997(E)
3.1.6 (N)-service: A capability of the (N)-layer and the layers beneath it, which is provided to (N+l)-entities at the
boundary between the @Q-layer and the (N+l)-layer.
NOTE - An application-service does not provide a capability to higher layer entities, but rather to application-processes.
presentation-service: A capability of the Presentation Layer and the layers beneath it, which is provided to
3.1.7
application-entities at the boundary between the Presentation and the Application Layer.
3.1.8 transfer syntax: The concrete syntax used in the transfer of data between open systems.
3.2 Abstract Syntax Notation One Definitions
This part of IS0 10 16 1 makes use of the following terms defined in ISO/IEC 8824: 1990.
3.2.1 data type; type: A named set of values.
3.2.2 simple type: A type defined by directly specifying the set of its values.
3.2.3 structured type: A type defined by reference to one or more other types.
3.2.4 component type: One of the types referenced when defining a structured type.
3.2.5 value: A distinguished member of a set of values.
3.3 Presentation Service Definition
This part of IS0 1016 1 makes use of the following term defined in IS0 8822: 1988.
3.3.1 abstract syntax: Those aspects of the rules used in the formal specification of data which are independent of the
encoding technique to represent the data.
3.4 Application Layer Structure Definitions
This part of IS0 10 16 1 makes use of the following terms defined in ISO/IEC 9545: 1989.
3.4.1 application-association: A cooperative relationship between two application-entity-invocations for the purpose of
communication of information and coordination of their joint operation. This relationship is formed by the exchange
of application-protocol-control-information using the Presentation Service.
3.4.2 application-context: A set of rules shared in common by two application-entity-invocations governing their behavior
in order to enable their cooperative operation.
NOTE - An application-context is a shared conceptual schema for the universe of discourse for communication.
3.4.3 application-context-definition: The description of an application-context.
application-entity-invocation: A specific utilization of part or all of the capabilities of a given application-entity in
3.4.4
support of the communications requirements of an application-process-invocation.
application-process-invocation: A specific utilization of part or all of the capabilities of a given application-process
3.4.5
in support of a specific occasion of information processing.
3.5 Service Convention Definitions
This part of IS0 10161 makes use of the following terms defined in ISO/TR 8509: 1987.
3.5.1 indication primitive: A representation of an interaction in which a service-provider either:
indicates that it has, on its own initiative, invoked some procedure; or
a.
b. indicates that a procedure has been invoked by the service-user at the peer service-access-point.
3.5.2 non-confirmed service: A distinct part of the total (N)-service which does not result in an explicit confirmation from
the service-provider to the initiating service-user.
3.5.3 provider-initiated service: A distinct part of the total @)-service which is initiated by the service-provider rather
than the service-user.
3.5.4 request primitive: A representation of an interaction in which a service-user invokes some procedure.
3.5.5 service primitive: An abstract, implementation-independent representation of an interaction between service-user and
the service-provider.
3.5.6 service-provider: An abstract of the totality of those entities which provide a service to peer service-users.
3.5.7 service-user: An entity in a single open system that makes use of a service.
@ IS0
IS0 10161-l :1997(E)
3.6 ILL Definitions
For the purposes of this part of IS0 10 16 1, the following definitions apply to the ASN. 1 value reference names and values
which are associated with simple data types, as specified in clause 9. Of these definitions, the following are repetitions of those
found in IS0 8459-l : 1988:
author
call number
client identifier
client-status
country
edition
place-of-publication
post-office-box
postal-code
publisher
sponsoring body
street-and-number
title
transportation-mode
volume-issue
-
NOTE - volume-issue is defined here, but volume and issue are defined separately in IS0 8459-l : 1988.
3.6.1 account-number: The number of an account to which a credit or debit is made. A requester typically has been
assigned a separate account for each responder. (Variation of IS0 8459-l)
additional-no-letters: (additional-numbers-letters) A number or code identifying an item.
3.6.2
3.6.3 already-forwarded: Responder indication that an ILL request has already been forwarded.
already-tried-list: List of institutions which have been approached but were unable to supply requested item.
3.6.4
3.6.5 answer: A code representing a yes or no response.
3.6.6 at-bindery: Title is owned but the requested item is at the bindery.
3.6.7 author: Name of the person or corporate body responsible for the intellectual or artistic content of an item, including
composers, creators or originators of an item.
3.6.8 author-of-article: Author of an item which is a component part of another item.
3.6.9 badly-structured-APDU: The structure of a received APDU does not conform to the standard notation and encoding
defmed in IS0 8824 and 8825, or to the EDIFACT encoding defined in IS0 9735 and Annex B of this International
Standard. For example, a received APDU does not match its stated length.
being-processed-for-supply: Item is being retrieved, copied, and/or packaged for delivery.
3.6.10
3.6.11 call-number: Notation assigned to an item indicating its physical location in the owner institution.
can-send-CHECKED-IN: An indication by the responder that it is capable of supplying the CHECKED-IN APDU.
3.6.12
3.6.13 can-send-RECEIVED: An indication by the requester that it is capable of supplying the RECEIVED APDU.
3.6.14 can-send-RETURNED: An indication by the requester that it is capable of supplying the RETURNED APDU.
can-send-SHIPPED: An indication by the responder that it is capable of supplying the SHIPPED APDU.
3.6.15
3.6.16 cannot-send-onward: An intermediary is unable to send on a request due to communication problems.
chargeable-units: The number of units supplied for which there is a charge.
3.6.17
3.6.18 charges: The responder’s charges for the provision of the requested service.
3.6.19 city: A phrase used to identify a city, town or village. (Variation of IS0 8459-l)
client-identifier: Number or code used to identify the client uniquely.
3.6.20
3.6.21 client-name: Name of the person or institution for which the item has been requested. (Variation of ISO 8459-l)
3.6.22 client-signature-required: Responder’s stipulation that the client must sign the signature sheet enclosed with the item.
3.6.23 client-status: Professional level or position of the client.
conditions: A code used to indicate the conditions under which an item may be borrowed.
3.6.24
3.6.25 copyright-compliance: Requester notation indicating the applkable copyright regulations or laws to which the
requester is adhering.
correlation-information: Information that is used to correlate an error report with the service request to which the
3.6.26
report relates.
cost: The amount asked, taken or billed by the responder for the service supplied.
3.6.27
cost-estimate: Estimate of the cost to provide the service requested.
3.6.28
@ IS0 IS0 10161=1:1997(E)
cost-exceeds-limit: Responder indication that the minimum cost to supply the request is greater than the amount authorized.
3.6.29
3.6.30 country: A phrase used to identify a country.
3.6.31 currency-code: A code identifying the currency of an amount, according to IS0 42 17: 198 1.
3.6.32 current-state: A code identifying the state of the ILL-transaction.
3.6.33 date-checked-in: The date on which a loaned item is received back by the responder.
date-due: The date by which the loaned item should be returned to the responder. Note that this should reflect the
3.6.34
latest date-due.
date-for-reply: The date by which a reply should be returned to the responder.
3.6.35
date-of-last-transition: The date on which the last state transition occurred.
3.6.36
3.6.37 date-of-most-recent-service: The date when the most recent service event occurred at the system providing the status
report. This is either a service invoked by the system providing the status report or a service reflected in a received APDU.
3.6.38 date-of-service: The date on which a service concerning an ILL-transaction is invoked.
3.6.39 date-received: The date when the item is received by the requester.
3.6.40 date-requested: The date the ILL request was initiated by the requester.
date-returned: The date when the item was returned to the responder.
3.6.41
3.6.42 date-shipped: The date when the item was shipped to the requester.
3.6.43 delivery-service: The delivery service or method used in transporting a requested item. Either physical or electronic
delivery may be used.
desired-due-date: The proposed due date for the renewed loan.
3.6.44
3.6.45 duplicate-transaction-id: The transaction-id value of an ILL-REQUEST APDU is an illegal duplicate, i.e. the value
is identical to one for an existing ILL-REQUEST received from the same requester.
3.6.46 edition: All the copies of an item produced from one master copy or substantially the same type image, having the same
contents, and, in the case of non-book materials, issued by a particular publishing agency or group of such agencies.
3.6.47 electronic-delivery: Delivery of an electronic representation of a document via a telecommunications-based data
transfer mechanism. Delivery via transfer of a tangible magnetic or optical medium is excluded.
3.6.48 estimated-date-available: Date when an item placed on hold is expected to become available.
expiry-date: The date on which an ILL-transaction expires automatically.
3.6.49
3.6.50 expiry-flag: An indication of whether an expiry date has been set for an ILL-transaction, and if so, whether that date is
the “need-before-date”, or some other date.
extended-postal-delivery-address: Additional information in the postal address necessary to identify the exact point
3.6.51
of delivery, e.g. room and floor number in a large building.
final-responder: Institution which supplies a requested item. This term is used when it is necessary to distinguish
3.6.52
between the responder of an ILL-transaction and the responder of an ILL-sub-transaction.
3.6.53 forward-flag: An indication whether a received ILL-REQUEST has been forwarded from an intermediary.
forward-note: Note added to the ILL-REQUEST by the responder when it is forwarded to a new responder.
3.6.54
3.6.55 general-problem: Code indicating a general problem with a received APDU detected by the ILL service-provider that
is not related to either the transaction-id or permissible state transitions.
ILL-APDU-type: Code identifying the type of APDU received.
3.6.56
3.6.57 ILL-service-type: A code for the type of ILL service requested. These can be listed in a preferred order.
3.6.58 ILL-transaction: A single complete instance of the whole ILL cycle, including all of the actions, service primitives, and
messages involved from the initial ILL-Request until the cycle is concluded, as with the return of the requested material.
3.6.59 in-process: Item has been received but is not yet ready for use.
in-use/on-loan: Item is owned but is currently being used by a client or is on loan to another institution.
3.6.60
3.6.61 initial-requester: Person or institution which initiates an ILL-transaction; this term is used when it is necessary to
distinguish between the requester of an ILL-transaction and the requester of an ILL sub-transaction.
initial-requester-address: Information identifying the telecommunications service and address by which the initial-
3.6.62
requester can be reached.
initiator-of-most-recent service: Identification information of the requester or responder who initiated the most
3.6.63
recent service.
institution-symbol: Number(s), letter(s) or a code serving to ident@ unambiguously and in an abbreviated format a library,
3.6.64
institution or corporation that is participating in an ILL-transaction, e.g. institutions national union catalogue symbol.
3.6.65 insured-for: Notation of the amount of insurance purchased against loss or damage of items.
@ is0
IS0 10161-1:1997(E)
3.6.66 intermediary-id: Identification information of an ILL-transaction intermediary.
3.6.67 intermediary-problem: Code indicating that the intermediary has a problem in processing the request.
invalid-transaction-id: The transaction-id value of an ILL-REQUEST is invalid, e.g. the value violates the assignment
3.6.68
rules of this part of IS0 10 16 1, or an unknown person-or-institution symbol or person-or-institution-name is encountered.
3.6.69 ISBN: The International Standard Book Number assigned to a monograph as prescribed by IS0 3297: 1986.
3.6.70 ISSN: The International Standard Serial Number assigned to a serial title as prescribed by IS0 2108: 1978.
3.6.71 item-type: A code identifying the bibliographic form in which the item has been produced.
3.6.72 lacking: The title is owned but not the component part or pages requested.
3.6.73 lacks-copyright-compliance: Compliance with applicable copyright regulations or laws must be indicated before
copying can be done.
level-of-service: A code that indicates the level of search detail required or the duration of time within which a
3.6.74
response is required. Note that this code reflects regional or national conventions.
3.6.75 library-use-only: Responder indication that the item may not be removed from the requesting institution.
location-address: Information identifying the telecommunication service and address or the postal address by which
3.6.76
the institution that owns the item can be reached.
3.6.77 location-id: The symbol or name of the institution that owns the r
...
SLOVENSKI STANDARD
01-november-2005
,QIRUPDWLNDLQGRNXPHQWDFLMD±6NXSLQD]DSRYH]RYDQMHRGSUWLKVLVWHPRY±
6SHFLILNDFLMDDSOLNDFLMVNHJDSURWRNROD]DPHGNQMLåQLþQRL]SRVRMR±GHO
6SHFLILNDFLMDSURWRNROD
Information and documentation -- Open Systems Interconnection -- Interlibrary Loan
Application Protocol Specification -- Part 1: Protocol specification
Information et documentation -- Interconnexion de systèmes ouverts (OSI) --
Spécification du protocole d'application pour les prêts entre bibliothèques -- Partie 1:
Spécification du protocole
Ta slovenski standard je istoveten z: ISO 10161-1:1997
ICS:
01.140.20 Informacijske vede Information sciences
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 Is0
STANDARD 10161-1
Second edition
1997-06-I 5
Information and documentation - Open
Systems Interconnection - Interlibrary
Loan Application Protocol Specification -
Part 1:
Protocol specification
Information et documentation - lnterconnexion de syst&mes ouvefls
(OH) - Spkification du protocole d’application pour les pr6ts entre
biblioth&ques -
Partie 1: Spkification du protocole
Reference number
IS0 10161-1:1997(E)
ISO10161-1:1997(E)
Contents
1 SCOPE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
2 NORMATIVE REFERENCES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3 DEFINITIONS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . .*. 2
3.1 REFERENCE MODEL DEFINITIONS
3.2 ABSTRACT SYNTAX NOTATION ONE DEFINITIONS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . .~.“. 3
3.3 PRESENTATION SERVICE DEFINITION
3.4 APPLICATION LAYER STRUCTURE DEFINITIONS . . . . . . . . . . . . . . . . . . . . . . .*.
3.5 SERVICE CONVENTION DEFINITIONS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
3.6 ILL DEFINITIONS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4 ABBREVIATIONS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5 OVERVIEW OF THE PROTOCOL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .*.***.**. 10
5.1 SERVICE PROVISION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .~.
5.2 SUPPORTING SERVICES ASSUMED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.3 MODEL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .~.
6 ILL APDUS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7 TRANSACTION INFORMATION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
7.1 TRANSACTION IDENTIFICATION . . . . . . . . . . . . . . .*.
7.2 PROTOCOL STATES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
7.2.1 Requester States
7.2.2 Responder States . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
7.2.3 Terminal States
7.2.4 Intermediary States . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7.3 PROTOCOL VARIABLES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
7.4 EXPIRY TIMER . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7.5 REQUEST INFORMATION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
7.5.1 System-id . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7.6 HISTORY INFORMATION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .~.~. 15
............................................................................................................................................ 16
8 ELEMENTS OF PROCEDURE
8.1 EVENTS AND ACTIONS . 16
............................................................................................................................................................. 16
8.1.1 Requester Events
8.1.2 Requester Actions . 17
8.1.3 Responder Events . 18
.......................................................................................................................................................... 19
8.1.4 Responder Actions
8.1.5 Intermediary Events and Actions . 20
8.2 PROCEDURAL RULES FOR ALL PARTIES .
8.2.1 Sending and Receiving APDUs . 20
8.2.2 Transaction Phases .
8.2.3 Optional Messages . 20
8.2.4 Send-to-list .
8.2.5 Already-tried-list . 21
........................................................................................................................................................
8.2.6 Control of Renewals 22
8.2.7 APDU Sequence Validation . 22
8.2.8 Repeated APDUs . 22
8.2.9 Retries . 23
8.2.10 Transaction Expiry . 23
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.
International Organization for Standardization
Case postale 56 l Cl-I-1 211 Geneve 20 l Switzerland
Internet central @ iso.ch
c=ch; a=40Onet; p=iso; o=isocs; s=central
x.400
Printed in Switzerland
@ IS0 IS0 10161=1:1997(E)
8.2.11 Transaction Cancellation .
8.2.12 Lifetime of ILL-Transaction Information . 24
................................................................................................................................................................. 24
8.2.13 Protocol Errors
8.2.14 Rules for Extensibility .
8.2.15 Responder-specific Information . 24
........................................................................................................................................... 25
8.2.16 Account-number Information
8.2.17 Supplemental-item-description . 25
8.2.18 Send Message . 25
8.3 PROCEDURAL RULES FOR INTERMEDIARIES . 25
................................................................................................................................................... 25
8.3.1 Transaction Forwarding
8.3.2 Transaction Chaining .
8.3.3 Transaction Partitioning . 26
8.3.4 Mixed Forwarding, Chaining and Partitioning . 27
9 ABSTRACT SYNTAX .
9.1 ASN. 1 SPECIFICATION OF ILL APDUs . 28
...................................................................................................................................................................... 29
9.1.1 ILL APDUs
9.1.2 Types . 36
10 CONFORMANCE . 48
10.1 STATIC CONFORMANCE . 48
10.2 DYNAMIC CONFORMANCE . 48
10.3 PROTOCOLIMPLEMENTATIONCONFORMANCESTATEMENTREQUIREMENTS . 49
Annexes
A ILL STATE TABLES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
. . . . . .“.=. 79
B TRANSFER SYNTAX
C OBJECT IDENTIFIERS ASSIGNED IN THIS PART OF IS0 10161 AND REGISTRATION REQUIREMENTS . . . . . . . . 102
D REGISTRATION PROCEDURES FOR ILL EXTERNAL DATA TYPE DEFINITIONS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103
E EXAMPLE OF ILL EXTERNAL DATA TYPE DEFINITION REGISTER ENTRY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
F USE OF SUPPORTING SERVICES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106
G INVOCATION OF EXTERNAL DOCUMENT DELIVERY SERVICES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108
H BIBLIOGRAPHY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109
. . .
III
@IS0
IS0 10161=1:1997(E)
Foreword
IS0 (the International Organization for Standardization) is a worldwide federation of national standards bodies (IS0 member
bodies). The work of preparing International 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 1- 1 was prepared by Technical Committee ISO/TC 46, Information and Documentation,
Subcommittee SC 4, Computer applications in information and documentation.
This second edition cancels and replaces the first edition (IS0 10 16 l-l : 1993), which has been technically revised. It includes
amendments specified in IS0 10161, DAM 1 and the corrections specified in Defect Reports l-23.
IS0 10 16 1 consists of the following parts, under the general title Information and documentation - open Systems
Interconnection - Interlibrary Loan Application Protocol Specification:
Part I: Protocol specification
Part 2: Protocol implementation conformance statement (PICS) proforma
Annexes A to D form an integral part of this part of IS0 1016 1. Annexes E to H are for information only.
iv
@ IS0 IS0 10161-1:1997(E)
Introduction
This part of IS0 10 16 1 is one of a set of International Standards produced to facilitate the interconnection of computer systems.
It is related to other International Standards in the set as defined by the Reference Model for Open Systems Interconnection
(IS0 7498). The Reference Model subdivides the area of standardization for interconnection into a series of layers of
specification, each of manageable size.
The aim of Open Systems Interconnection is to allow, with a minimum of technical agreement outside the interconnection
standards, the interconnection of computer systems:
a. from different manufacturers,
b. under different managements,
c. of different levels of complexity,
d. of different ages.
This part of IS0 10 16 1 provides a protocol specification for Interlibrary Loan (ILL) communication. The ILL protocol operates
in the Application Layer and allows the parties involved in an ILL-transaction to progress through the ILL-transaction in an
orderly and defined way.
The ILL protocol has been designed to support the ILL services defined in IS0 10 160, the ILL Application Service Definition,
which generally requires invocation of external delivery services to fulfill an ILL request. The ILL protocol carries information
that permits both automatic and operator-mediated invocation of external delivery services.
This part of IS0 10 16 1 is one of a number of related standards supporting the interconnection of library systems. These
standards can be used by themselves or in a cooperative manner to support library applications requiring a mixture of
communications services. For example, IS0 23950, which supports remote access to bibliographic databases, could be used in
conjunction with the ILL protocol to obtain item identification information. The control and management of interactions among
such bibliographic applications are local matters that are outside the scope of this International Standard.
Security and accounting issues as they relate to ILL operations are for further study.
The specification technique used in this part of IS0 1016 1 is consistent with techniques used in defining other OS1 protocols.
Within most of this document, the technique is self-explanatory. The Abstract Syntax of the ILL Application Protocol Data
Units (APDUs) is defined by means of the ASN.l specification technique specified in ISO/IEC 8824.
This part of IS0 1016 1 contains eight annexes. Annexes A to D are normative. Annex A specifies the the state tables for the
ILL protocol. Annex B specifies the encoding rules for generating a transfer syntax compatible with EDIFACT as defined in
IS0 9735. Annex C specifies the object identifiers assigned in this part of IS0 10 16 1 and registration requirements. Annex D
defines the registration procedures for ILL EXTERNAL data type definitions. Annex E is an example of an ILL EXTERNAL
data type registry entry. Annex F describes the possible mappings of this protocol onto supporting services. Annex G describes
possible methods of using a document delivery protocol in conjunction with the ILL protocol. Annex H is a bibliography.
This page intentionally left blank
~~~~~~
IS0 10161-1:1997(E)
INTERNATIONAL STANDARD @ IS0
Information and documentation - Open Systems
Interconnection - Interlibrary Loan Application
- Part 1: Protocol specification
Protocol Specification
1 Scope
This part of IS0 10 16 1 defines the protocol for an ILL application-service-element (ASE). It specifies the behaviour which
must be exhibited by a system in order to take part in the provision of the IS0 interlibrary loan service.
It provides a formal statement of the rules of behaviour of each of the two or more entities participating in an ILL transaction. It
specifies:
a. the actions to be taken on receiving request service primitives issued by an ILL service-user;
b. the actions to be taken on receiving application-protocol-data-units (APDUs);
c. the actions to be taken as a result of events within the local system.
It provides a specification (in clause 9) of the abstract syntax required to convey the ILL protocol APDUs.
It states the conformance requirements to be met by implementors of this protocol (in clause 10).
The scope of the ILL protocol is restricted to the interconnection of systems; it does not specify or restrict the possible
implementation of interfaces within a computer system. Computer systems may range from stand-alone workstations to
mainframes.
This part of IS0 10 16 1 is intended for use by libraries, information utilities such as union catalogue centres, and any other
system which processes bibliographic information. These systems may participate in an interlibrary loan transaction in the role
of requester (i.e. an initiator of ILL requests), responder (i.e. a provider of bibliographic material or information) and/or
intermediary (i.e. an agent that acts on behalf of a requester to find suitable responders).
Various interworking topologies are supported, ranging from simple two-party interactions, to multi-party interactions.
2 Normative references
The following standards contain provisions which, through reference in this text, constitute provisions of this part of
IS0 1016 1. At the time of publication, the editions indicated were valid. All standards are subject to revision, and parties to
agreeements based on this part of IS0 10 16 1 are encouraged to investigate the possibility of applying the most recent editions
of the standards indicated below. Members of IEC and IS0 maintain registers of currently valid International Standards.
Information technology - IS0 7-bit coded character set for information interchange.
ISO/IEC 646: 199 1,
NOTE - ISO/IEC 646: 199 1 supersedes IS0 646: 1983. However, when this part of IS0 10 16 1 was under development, the previous
edition was valid and this part of IS0 10161 is therefore based on this edition, which is given below.
646: 1983, Information Processing Systems - IS0 7-bit coded character set for information interchange.
IS0
Information and documentation - International standard book numbering (ISBN).
IS0 2108: 1992,
NOTE - IS0 2 108: 1992 supersedes IS0 2 108: 1978. However, when this part of IS0 10 16 1 was under development, the previous
edition was valid and this part of IS0 10161 is therefore based on this edition, which is given below.
IS0 2108: 1978, Documentation - International standard book numbering (ISBN).
IS0 2709: 1996, Information and documentation - Format for Information Ekhnge.
NOTE - IS0 2709: 1996 supersedes IS0 2709: 198 1. However, when this part of IS0 10 16 1 was under development, the previous
edition was valid and this part of IS0 10 161 is therefore based on this edition, which is given below.
IS0 Documentation - Format for bibliographic information interchange on magnetic tape.
2709: 1981,
IS0 3297: 1986, Documentation - International standard serial numbering (ISSN).
@ IS0
IS0 10161=1:1997(E)
IS0 421711995, Codes for the representation of currencies and funds.
NOTE - IS0 42 17: 1995 supersedes IS0 42 17: 198 1. However, when this part of IS0 10 16 1 was under development, the previous
edition was valid and this part of IS0 10161 is therefore based on this edition, which is given below.
IS0 4217:1981, Codes for the representation of currencies and funds.
ISO/IEC 7498-l : 1994, Information technology - Open Systems Interconnection - Basic Reference Model: The Basic Model.
IS0 7498-2: 1989, Information processing systems - Open Systems Interconnection - Basic Reference Model - Part 2: Security Architecture.
IS0 Information processing systems - Open Systems Interconnection - Basic Reference Model - Part 3: Naming and addressing.
7498-3 : 1989,
Open Systems Interconnection - Basic Reference Model - Part 4: Managementframework.
ISO/IEC 74984: 1989, Information processing systems -
NOTE - ISO/IEC 7498-l) IS0 7498-2, IS0 7498-3 and ISO/IEC 7498-4 supersede IS0 7498: 1984. However, when this part of
IS0 10161 was under development, the previous edition was valid and this part of IS0 10 16 1 is therefore based on this edition,
which is given below.
IS0 7498: 1984, Information processing systems - Open Systems Interconnection - Basic Reference Model.
IS0 8601: 1988, Data elements and interchange formats - Information interchange - Representation of dates and times.
ISO/IEC Information technology - Open Systems Interconnection - Presentation service definition.
8822: 1994,
NOTE - ISO/IEC 8822: 1994 supersedes IS0 8822: 1988.’ However, when this part of IS0 10 16 1 was under development, the
previous edition was valid and this part of IS0 10161 is therefore based on this edition, which is given below.
Open Systems Interconnection - Connection Oriented Presentation Service Definition.
IS0 8822: 1988, Information processing systems -
- Specification of Abstract Syntax Notation One (ASN. I).
ISO/IEC 8824: 1990, Information technology - Open Systems Interconnection
ISO/IEC 8825: 1990, Information technology - Open Systems Interconnection - Specification of Basic Encoding Rules for Abstract Syntax Notation One
(ASN. I).
IS0 9735: 1988, Electronic data interchange for administration, commerce and transport (EDIFACT) - Application Level Syntax Rules.
ISO/IEC Information technology - Open Systems Interconnection - Procedures for the operation of OSI Registration Authorities - Part I:
9834-l: 1993,
General procedures.
Procedures for the operation of OSI Registration Authorities - Part 2:
ISO/IEC 9834-2: 1993, Information technology - Open Systems Interconnection -
Registration procedures for OSI document types.
Text Interchange Systems (MOTIS) - Part 4: Message Transfer
ISO/IEC 10021-4:1990, Information Technology - Text Communication - Message-Oriented
System: Abstract Service Definition and Procedures.
IS0 10 160: 1997, Information and documentation - Open Systems Interconnection - Interlibrary Loan Application Service Definition.
3 Definitions
For the purposes of this part of IS0 10 16 1, the following definitions apply.
3.1 Reference Model Definitions
This part of IS0 10 16 1 is based on the concepts developed in IS0 7498: 1984 and makes use of the following terms found in it.
These terms are replicated here as a convenience to the reader.
Application Layer: The seventh and highest layer in the Reference Model for Open Systems Interconnection (ON); it
3.1.1
serves as the window between correspondent application-processes which are using the OS1 to exchange meaningfkl
information.
3.1.2 application-entity: The aspects of an application-process pertinent to OSI.
application-process: An element within a real open system which performs the information processing for a particular
3.1.3
application.
3.1.4 application-protocol-data-unit: A unit of data specified in an application-protocol and consisting of application-
protocol-information and possibly application-user-data.
application-service-element: That part of an application-entity which provides an OS1 environment capability, using
3.1.5
underlying services when appropriate.
@ IS0 IS0 10161=1:1997(E)
3.1.6 (N)-service: A capability of the (N)-layer and the layers beneath it, which is provided to (N+l)-entities at the
boundary between the @Q-layer and the (N+l)-layer.
NOTE - An application-service does not provide a capability to higher layer entities, but rather to application-processes.
presentation-service: A capability of the Presentation Layer and the layers beneath it, which is provided to
3.1.7
application-entities at the boundary between the Presentation and the Application Layer.
3.1.8 transfer syntax: The concrete syntax used in the transfer of data between open systems.
3.2 Abstract Syntax Notation One Definitions
This part of IS0 10 16 1 makes use of the following terms defined in ISO/IEC 8824: 1990.
3.2.1 data type; type: A named set of values.
3.2.2 simple type: A type defined by directly specifying the set of its values.
3.2.3 structured type: A type defined by reference to one or more other types.
3.2.4 component type: One of the types referenced when defining a structured type.
3.2.5 value: A distinguished member of a set of values.
3.3 Presentation Service Definition
This part of IS0 1016 1 makes use of the following term defined in IS0 8822: 1988.
3.3.1 abstract syntax: Those aspects of the rules used in the formal specification of data which are independent of the
encoding technique to represent the data.
3.4 Application Layer Structure Definitions
This part of IS0 10 16 1 makes use of the following terms defined in ISO/IEC 9545: 1989.
3.4.1 application-association: A cooperative relationship between two application-entity-invocations for the purpose of
communication of information and coordination of their joint operation. This relationship is formed by the exchange
of application-protocol-control-information using the Presentation Service.
3.4.2 application-context: A set of rules shared in common by two application-entity-invocations governing their behavior
in order to enable their cooperative operation.
NOTE - An application-context is a shared conceptual schema for the universe of discourse for communication.
3.4.3 application-context-definition: The description of an application-context.
application-entity-invocation: A specific utilization of part or all of the capabilities of a given application-entity in
3.4.4
support of the communications requirements of an application-process-invocation.
application-process-invocation: A specific utilization of part or all of the capabilities of a given application-process
3.4.5
in support of a specific occasion of information processing.
3.5 Service Convention Definitions
This part of IS0 10161 makes use of the following terms defined in ISO/TR 8509: 1987.
3.5.1 indication primitive: A representation of an interaction in which a service-provider either:
indicates that it has, on its own initiative, invoked some procedure; or
a.
b. indicates that a procedure has been invoked by the service-user at the peer service-access-point.
3.5.2 non-confirmed service: A distinct part of the total (N)-service which does not result in an explicit confirmation from
the service-provider to the initiating service-user.
3.5.3 provider-initiated service: A distinct part of the total @)-service which is initiated by the service-provider rather
than the service-user.
3.5.4 request primitive: A representation of an interaction in which a service-user invokes some procedure.
3.5.5 service primitive: An abstract, implementation-independent representation of an interaction between service-user and
the service-provider.
3.5.6 service-provider: An abstract of the totality of those entities which provide a service to peer service-users.
3.5.7 service-user: An entity in a single open system that makes use of a service.
@ IS0
IS0 10161-l :1997(E)
3.6 ILL Definitions
For the purposes of this part of IS0 10 16 1, the following definitions apply to the ASN. 1 value reference names and values
which are associated with simple data types, as specified in clause 9. Of these definitions, the following are repetitions of those
found in IS0 8459-l : 1988:
author
call number
client identifier
client-status
country
edition
place-of-publication
post-office-box
postal-code
publisher
sponsoring body
street-and-number
title
transportation-mode
volume-issue
-
NOTE - volume-issue is defined here, but volume and issue are defined separately in IS0 8459-l : 1988.
3.6.1 account-number: The number of an account to which a credit or debit is made. A requester typically has been
assigned a separate account for each responder. (Variation of IS0 8459-l)
additional-no-letters: (additional-numbers-letters) A number or code identifying an item.
3.6.2
3.6.3 already-forwarded: Responder indication that an ILL request has already been forwarded.
already-tried-list: List of institutions which have been approached but were unable to supply requested item.
3.6.4
3.6.5 answer: A code representing a yes or no response.
3.6.6 at-bindery: Title is owned but the requested item is at the bindery.
3.6.7 author: Name of the person or corporate body responsible for the intellectual or artistic content of an item, including
composers, creators or originators of an item.
3.6.8 author-of-article: Author of an item which is a component part of another item.
3.6.9 badly-structured-APDU: The structure of a received APDU does not conform to the standard notation and encoding
defmed in IS0 8824 and 8825, or to the EDIFACT encoding defined in IS0 9735 and Annex B of this International
Standard. For example, a received APDU does not match its stated length.
being-processed-for-supply: Item is being retrieved, copied, and/or packaged for delivery.
3.6.10
3.6.11 call-number: Notation assigned to an item indicating its physical location in the owner institution.
can-send-CHECKED-IN: An indication by the responder that it is capable of supplying the CHECKED-IN APDU.
3.6.12
3.6.13 can-send-RECEIVED: An indication by the requester that it is capable of supplying the RECEIVED APDU.
3.6.14 can-send-RETURNED: An indication by the requester that it is capable of supplying the RETURNED APDU.
can-send-SHIPPED: An indication by the responder that it is capable of supplying the SHIPPED APDU.
3.6.15
3.6.16 cannot-send-onward: An intermediary is unable to send on a request due to communication problems.
chargeable-units: The number of units supplied for which there is a charge.
3.6.17
3.6.18 charges: The responder’s charges for the provision of the requested service.
3.6.19 city: A phrase used to identify a city, town or village. (Variation of IS0 8459-l)
client-identifier: Number or code used to identify the client uniquely.
3.6.20
3.6.21 client-name: Name of the person or institution for which the item has been requested. (Variation of ISO 8459-l)
3.6.22 client-signature-required: Responder’s stipulation that the client must sign the signature sheet enclosed with the item.
3.6.23 client-status: Professional level or position of the client.
conditions: A code used to indicate the conditions under which an item may be borrowed.
3.6.24
3.6.25 copyright-compliance: Requester notation indicating the applkable copyright regulations or laws to which the
requester is adhering.
correlation-information: Information that is used to correlate an error report with the service request to which the
3.6.26
report relates.
cost: The amount asked, taken or billed by the responder for the service supplied.
3.6.27
cost-estimate: Estimate of the cost to provide the service requested.
3.6.28
@ IS0 IS0 10161=1:1997(E)
cost-exceeds-limit: Responder indication that the minimum cost to supply the request is greater than the amount authorized.
3.6.29
3.6.30 country: A phrase used to identify a country.
3.6.31 currency-code: A code identifying the currency of an amount, according to IS0 42 17: 198 1.
3.6.32 current-state: A code identifying the state of the ILL-transaction.
3.6.33 date-checked-in: The date on which a loaned item is received back by the responder.
date-due: The date by which the loaned item should be returned to the responder. Note that this should reflect the
3.6.34
latest date-due.
date-for-reply: The date by which a reply should be returned to the responder.
3.6.35
date-of-last-transition: The date on which the last state transition occurred.
3.6.36
3.6.37 date-of-most-recent-service: The date when the most recent service event occurred at the system providing the status
report. This is either a service invoked by the system providing the status report or a service reflected in a received APDU.
3.6.38 date-of-service: The date on which a service concerning an ILL-transaction is invoked.
3.6.39 date-received: The date when the item is received by the requester.
3.6.40 date-requested: The date the ILL request was initiated by the requester.
date-returned: The date when the item was returned to the responder.
3.6.41
3.6.42 date-shipped: The date when the item was shipped to the requester.
3.6.43 delivery-service: The delivery service or method used in transporting a requested item. Either physical or electronic
delivery may be used.
desired-due-date: The proposed due date for the renewed loan.
3.6.44
3.6.45 duplicate-transaction-id: The transaction-id value of an ILL-REQUEST APDU is an illegal duplicate, i.e. the value
is identical to one for an existing ILL-REQUEST received from the same requester.
3.6.46 edition: All the copies of an item produced from one master copy or substantially the same type image, having the same
contents, and, in the case of non-book materials, issued by a particular publishing agency or group of such agencies.
3.6.47 electronic-delivery: Delivery of an electronic representation of a document via a telecommunications-based data
transfer mechanism. Delivery via transfer of a tangible magnetic or optical medium is excluded.
3.6.48 estimated-date-available: Date when an item placed on hold is expected to become available.
expiry-date: The date on which an ILL-transaction expires automatically.
3.6.49
3.6.50 expiry-flag: An indication of whether an expiry date has been set for an ILL-transaction, and if so, whether that date is
the “need-before-date”, or some other date.
extended-postal-delivery-address: Additional information in the postal address necessary to identify the exact point
3.6.51
of delivery, e.g. room and floor number in a large building.
final-responder: Institution which supplies a requested item. This term is used when it is necessary to distinguish
3.6.52
between the responder of an ILL-transaction and the responder of an ILL-sub-transaction.
3.6.53 forward-flag: An indication whether a received ILL-REQUEST has been forwarded from an intermediary.
forward-note: Note added to the ILL-REQUEST by the responder when it is forwarded to a new responder.
3.6.54
3.6.55 general-problem: Code indicating a general problem with a received APDU detected by the ILL service-provider that
is not related to either the transaction-id or permissible state transitions.
ILL-APDU-type: Code identifying the type of APDU received.
3.6.56
3.6.57 ILL-service-type: A code for the type of ILL service requested. These can be listed in a preferred order.
3.6.58 ILL-transaction: A single complete instance of the whole ILL cycle, including all of the actions, service primitives, and
messages involved from the initial ILL-Request until the cycle is concluded, as with the return of the requested material.
3.6.59 in-process: Item has been received but is not yet ready for use.
in-use/on-loan: Item is owned but is currently being used by a client or is on loan to another institution.
3.6.60
3.6.61 initial-requester: Person or institution which initiates an ILL-transaction; this term is used when it is necessary to
distinguish between the requester of an ILL-transaction and the requester of an ILL sub-transaction.
initial-requester-address: Information identifying the telecommunications service and address by which the initial-
3.6.62
requester can be reached.
initiator-of-most-recent service: Identification information of the requester or responder who initiated the most
3.6.63
recent service.
institution-symbol: Number(s), letter(s) or a code serving to ident@ unambiguously and in an abbreviated format a library,
3.6.64
institution or corporation that is participating in an ILL-transaction, e.g. institutions national union catalogue symbol.
3.6.65 insured-for: Notation of the amount of insurance purchased against loss or damage of items.
@ is0
IS0 10161-1:1997(E)
3.6.66 intermediary-id: Identification information of an ILL-transaction intermediary.
3.6.67 intermediary-problem: Code indicating that the intermediary has a problem in processing the request.
invalid-transaction-id: The transaction-id value of an ILL-REQUEST is invalid, e.g.
...
Questions, Comments and Discussion
Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.
Loading comments...