ISO ILL Protocol Standards

What's New
Standards
Register
Implementations
Testing ILL Protocol Implementations
Reading
ASN.1 Index

Home
Site Index

In this Document:

  • Intro to ILL Application
    Standards
  • ISO 10160
    Service Definition
  • ISO 10161-1
    Protocol Specs
  • ISO 10161-2
    PICS Proforma
  • Where to Purchase
  • ISO TC46/SC4/WG4
  • Maintenance
    Agency Procedures
  • Profiles
  • Clarifications
  • Review
    For More Information,
    contact
    the ILL Application Standards
    Maintenance Agency,
    Library and Archives Canada

    ill_asma
    @lac-bac.gc.ca

    Last Update:
    2002/01/08



  • ISO ILL Protocol Standards
    Interlibrary Loan Application Standards Maintenance Agency


    Clarification E13.3

    External OID for Extension (13)

    APDU-Delivery-Info (3)


    The APDU-Delivery-Info object can be deeply nested in order to solve complex agency identification and APDU delivery problems. The outer object, APDU-Delivery-Info, contains three identical lists of identification/delivery elements called APDU-Delivery-Parameters. Unlike the ILL Protocol, which describes roles in terms of the ILL transaction, each list describes identification and delivery information relative to the agencies that emitted or received the APDU itself.

    Thus, any ILL implementation capable of supporting all three transport/encoding methods could identify that ability by including multiple APDU-Delivery-Parameters for itself. For instance, the CISTI Transponder is capable of sending and receiving EDIFACT store-and-forward and BER connection-oriented APDUs. Thus, CISTI could encode its address twice: once for the connection-oriented BER path, the other for the EDIFACT store-and-forward path. An implementation has the responsibility of examining each element stored under each role to determine which is appropriate for its delivery capabilities.

    Likewise, the user of this object may encode as many namespace resolution identifiers as deemed necessary by filling the alias list with the appropriate System-Ids. An organization could identify itself as TLC: SITE1, OCLC: UWV, and RLIN: WILDANDWONDERFUL simultaneously.

    Usage in IPIG Profile:

    This object is mandatory in all APDUs conforming to the IPIG Profile. The IPIG Profile restricts individual lists to a maximum of twenty-five elements.

    Use of EDIFACT encoding

    Because this object may be used by libraries using the Canadian Standardized Profile and other implementations using the supplementary transfer syntax, EDIFACT, coding for this external object has been provided in EDIFACT as well as in ASN.1 BER.

    Example of encoding for an EDIFACT interchange:
     EXT+'
       EID+1'
       EXS+1 0 10161 13 3'
         SIN+1:2:3+SendersId+SendersAddress'
           SYI+NUC?:MaSU
         RIN+2:1+Recipient1Id+Recipient1Address'
         RIN+1+Recipient2Id+Recipient2Address'
         TIN+1:3+TransponderId+TransponderAddress'
           SYI+NUC?:CaOON
           SYI+OCLC?:CAI
       EXF+'
     
    --Based on IPIG Mailing List posting "IPIG use of the APDUDeliveryInfo Object" from Mark Wilson, TLC, dated 24 February 1998.

    --EDIFACT coding example provided by Johann C. Zeeman, CGI.


    Entry from Register of Public Object Identifers for ILL for APDU-Delivery-Info


    See the Maintenance Agency Procedures for details on preparing Clarifications.

          Top of page


    copyright © 1998
    Interlibrary Loan Application Standards Maintenance Agency