1. NISO Circulation Interchange Protocol A Standard in Development Pat Stevens, OCLC July 13, 2000

2. Topics zBackground zWork to date yApproach yProgress zChallenges

3. What Do Users Want? zSimple access zReliable, fast delivery zI.e., services like Amazon.com

4. More Specifically... zEasy, powerful, one-stop search and find z“Request” requiring minimal keying zAbility to track request (e.g. UPS) zGuaranteed, fast delivery zIntegrated management of their loans (from local collection and outside…)

5. Make it Easy! (example) zJohn Smith - items charged: zBritish Art in the 20th Century Due 8/15/00 [borrowed from local collection] zBradshaw, T. Bloomsbury Artists Due 7/30/00 [requested and borrowed directly from consortial partner] zHolroyd, M. The Art of Dora Carrington Due 7/15/00 [not in local collection or consortium; borrowed from unaffiliated library via traditional ILL] zGombrich, E. History of Art Due 7/10/00 10:00 pm [E-book, charged for use online]

6. New Supply Models Local Library Consortial Partners Unaffiliated institutions

7. Vendors & Systems - potential uses of protocol ILS/ Circ Sys ILS/ Circ Sys ILL ILS/ Circ Sys ILS/ Circ Sys ILS/ Circ Sys ILS/ Circ Sys Self Service Self Service ILS/ Circ Sys ILS/ Circ Sys

8. 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

9. Supports 3 application areas zDirect consortial borrowing zCirculation/Interlibrary Loan Interaction zSelf-service Circulation zThe standard’s test bed zIt must support these, may support others

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

11. 3M SIP 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

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

13. 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

14. Message Syntax, Transport Protocol and Encoding zMessage Syntax and Encoding ySyntax -- XML DTD yMessage encoding -- XML following DTD zTransport yTo be decided at August, 2000 meeting xDirectly on top of TCP/IP xWrapped in another protocol

15. 3 Service Types zLookup tell me something about zUpdate please take an action zNotification I have taken an action

16. Messages zabout 3 things (objects) yUsers yItems yAgencies (Libraries)

17. Lookup Services zLookup yLookup Agency yLookup Item yLookup User yAuthenticate User xNot Authorize User xAuthorization request implicit in an update zLookups require a Unique ID

18. Lookup Response zDid not Understand Message zUnderstood Message yCannot Supply Information and Reason yCan Supply and the Information

19. Unique ID’s zAgency ID’s yRegistration scheme yValue in Scheme yExample OCLC and OCLC Symbol zUser ID and Item ID are compound yInclude the Agency ID

20. Update Services zCheckOut Item and Undo Checkout Item zCheckIn Item zRecall Item and Cancel Recall Item zRenew Item and Cancel Renew Item zRequest Item and Request Item zSend User Notice zTypical Circulation Transactions

21. Update Services continued zCreate Agency and Update Agency zCreate Item and Update Item zCreate User and Update User zUpdate User Fiscal Account zCreate Services used for new objects zUpdate Services include modify and delete

22. Update Responses zDid Not Understand Message zUnderstood Message yCannot take Action Requested with Reason yDid Take Action xResponse includes information on action taken, xExamples: Due Date, Item or User ID

23. Notification Services zItem CheckedOut zItem Checked In zItem Recalled and Item Recalled Cancelled zItem Renewed and Item Renewed Cancelled zItem Requested zUser Fiscal Account Updated zUser Notice Sent

24. Notification Service... zAgency Created and Agency Updated zItem Created and Item Updated zUser Created and User Updated

25. Notification Service Response zDid not understand message zUnderstood message

26. Messages defined in a DTD zEach service has 2 messages yInitiation and Response zAll messages have yHeader and Body zHeader provides identifying information zBody provides details zExtensibility a goal

27. Checkout Message data data

28. Checkout Message continued data data data data

29. Checkout Message continued data data

30. Checkout Message continued data data

31. Approach zGOAL -- Draft Standard for Trial Use zAllow for implementations prior to ballot zIdentify early implementers yImplementers invited to August meeting zDevelop tests yMessage level testing yApplication level testing zDSFTU - August 2000

32. Structure of standard zProtocol: services, high-level objects, message state zCross Application profile: specifies encoding via XML schema for ymessages, data objects, transport z3 Application-specific profiles: ySelf-Service, Direct Consortial Borrowing, ILL to Circulation

33. Challenges zAllowing for local practice yWithin libraries and consortia yAllowing for international use zMoving target yTechnology yLibrary practice zAllowing for new applications

34. Questions? pat_stevens@oclc.org