CornellCNRI Repository Interoperability Project Interoperability Meeting February 24

Cornell/CNRI Repository Interoperability Project Interoperability Meeting February 24, 1999

Cornell/CNRI Repository Goals • • • Open architecture Interoperable digital objects and repositories Flexible notions of content while ensuring interoperability Extensible, community-driven content types Complex aggregations of distributed content Rights management - leverage existing/future schemes

CNRI/Cornell Interoperability Project • Developed Joint Interface Definition 8 agreement on all conceptual abstractions 8 merger of RAP and FEDORA IDL • Separate repository implementations 8 CNRI using Visigenics ORB 8 Cornell using Iona’s Orbix. Web ORB • Test collections of Digital Objects 8 CNRI - Library Congress materials (books, journals, photographs, speeches) 8 Cornell - NCSTRL research collections

Project History • • • Kahn/Wilensky Warwick Framework Distributed Active Relationships CNRI Repository (Arms, Blanchi, Overly) Cornell FEDORA (Lagoze, Payette) RAP/FEDORA - joint model and IDL RAP/FEDORA - Interoperability Testing RAP/FEDORA - Access Management DLI 2

Insert CNRI Repository Slides

Cornell: FEDORA Part of broader effort to develop a component-ware digital library architecture • Repository Service 8 core service to provide a reliable and secure means to store and disseminate digital content 8 interoperability with other CRADDL services • Digital Object Model 8 container for aggregating any digital material 8 disseminations of complex content types with rights management 8 global extensibility mechanisms

Cornell/CNRI Digital Object Model Get. Chapter Get. TOC Get. Page List. Content. Types Book Disseminator Dublin. Core Disseminator Book, Dublin. Core Get. Methods(Book) Get. Chapter(n), Get. TOC(), etc. Get. Dissemination (Book. Get. Page(1)) application/ MARC DS 1 application/ postscript DS 2 Primitive Disseminator

Digital Object Extensibility: Book Adding New Content Types Pho Coll to ect Book The same underlying data. . . Structure can be operated on in novel ways… Mechanism Photo Collection to create new disseminations not originally conceived of for the particular digital object. Interface

How Achieve Content-Type Extensibility? DC servlet URNDC 1 CTID = URNDC 1 DC DC Mechanism application/ postscript Digital Object attains its extended content-type behaviors through association and delegation URNDC Signature Disseminator DC Method. List Servlet Disseminator C si G gn G et et D at D C ur C Fi e R e ec ld or d Dublin. Core Record application/ MARC D Get. Dissemination( Get. DCRecord)

Registration and Proliferation of Content Types • A content type becomes registered when the URN of the Digital. Object that disseminates its signature is registered (in a DL name service) • A content type becomes usable when the URN of the Digital. Object that disseminates its servlet is registered • Other Digital. Objects can utilize content types by referencing these URNs.

CNRI/Cornell Interoperability Experiments • IT 0: Fundamental Communication 8 Inter-ORB communication 8 IDL recognition: request invocation; proper return types 8 STATUS: Success (October 1998) • IT 1: Functional Interoperability 8 create/access Digital. Objects in each repository 8 execution of all operations per specification 8 STATUS: Success (December 1998)

CNRI/Cornell Interoperability Experiments • IT 2: Content-Type Servlet Interoperability 8 implementation of new Servlet API 8 dynamic loading and running of remote servlets 8 integration of CNRI’s Handle System 8 STATUS: In Progress (Completion March 1, 1999) • IT 3: Scalability 8 logical interoperability tests 8 complex objects from Library of Congress, NCSTRL 8 STATUS: Planned (Completion April 1, 1999)

Planned Research • Scale up: demonstrate complex content types and servlets with CNRI and LC • Integration of new communitydeveloped content types (e. g. , MOA 2) • Access Management • Reliability, security, integrity (DLI 2 - CS/Cornell University Library)