NISO Circulation Interchange Protocol A Standard in Development ZIG Tutorial January 19, 2000

Topics zThe Committee - Charge & Composition zWork to date yApproach yProgress zFuture Challenges

Committee Charge - What zDefine transactions yneeded for circulation activities yamong independent library systems. zFacilitate ydirect patron borrowing, yremote patron authentication, yon-line payment, and ycontrolled access to electronic documents.

Step 1- Understand & Plan zUnderstand today’s environment yActivities in and among libraries yExisting standards environment yExisting solutions zDetermine yWhat a standard protocol can do yHow best to achieve it

Step 2- Check the plan zPublished a Guidelines document yProposed Standard, Purpose and Scope yRelated Standards yTechnical Assumptions and Plans yWork-to-date xActivities Supported xMessage State

The Standard and Scope zA repertoire of messages & associated rules of syntax and semantics zBetween and among computer-based applications yto effect circulation yto support controlled access to certain electronic resources or other library services z Not to define circulation functions

Supports 4 application areas zDirect consortial borrowing zCirculation/Interlibrary Loan Interaction zSelf-service Circulation zAccess to Electronic Resources zThe standard’s test bed zIt must support these, may support others

Standards environment z3M Standard Interchange Protocol zISO :1997 Bibliographic Data Element Directory: Part 4: Circulation Application zISO 10160/61 Interlibrary Loan Application Service Definition & Protocol Specification zANSI/NISO Z Information Retrieval: Application Service Definition and Protocol (ISO 23950)

3M Standard Interchange Protocol zDe facto standard for self checkout zExtended to support other functions zAllows the committee to build from a base of practical applications z3M and other vendors experienced with the SIP are active participants

A Goal -- as possible zUse existing definitions and terminology zPermit developers to meld standards into a single application

Technical Assumptions and Design Principles zKeep it simple and within purpose zConfirmed Service -- Pairs of messages yInitiation -- response pairs yEach message carries full context necessary for processing yRequires connection-oriented transport zSimple State Table ygoverns messaging not circulation

Message Syntax, Transport Protocol and Encoding zBody of library standards specified in ASN.1 zBody of library standards/applications using BER for encoding zWeb world appears to be adopting XML for both specification and encoding zCommittee will get expert help to make this decision

Step 3 -- Draft a standard zDevelop Services and Messages z3 Services yQuery tell me something about yRequest please take an action yNotification I have taken an action

Messages zabout 5 things (objects) yUsers yItems yTransactions yAgencies (Libraries) ySystems (Applications)

Where are we now? zService Definitions: Query, Request, Notify 2nd draft zMessage list for each service 2nd draft zMessage Definitions 2nd draft z4 groups charged with defining data structures and elements yUser, Item, Transaction, Agency and System

Next Steps zGOAL -- Draft Standard for Trial Use zAllow for implementations prior to ballot zSteps yComplete and refine message definitions ySeek expert advice on transfer encoding yDevelop structure for profile documents that describe use in a particular application zDSFTU - August 2000

Challenges/Questions zWhen does this committee stop? yAfter defining messages yAfter defining a sample profile with encoding mechanism zHow to promote and support initial implementations

URL’s zhttp:// zhttp://

Questions?