Corporation For National Research Initiatives Handle - Technical Update Larry Lannom CNRI Sept 20, 2002

Corporation For National Research Initiatives Technical Developments: 2001/02 Maturation u Increase in numbers - 5M+ DOIs –New backend db –New admin facilities u Increased scope of application areas –Learning objects –Images u Increased scope of research interest –Identity management –Grid - handles for events –Laws & Regs (DTIC/TSO) –Network storage

Corporation For National Research Initiatives Technical Developments: 2001/02 Maturation u Admin Tools –GUI installer, server splitter –SQL backend –Servlets for web based admin –Administration Manual u Development Tools –Python library (not yet licensed) –New hdllib example programs (net.handle.apps.simple) u Responding to dot com jitters –Exodus bankruptcy - added additional GHS, DOI LHS and proxy at CNRI u Support for encrypted communication between clients and servers u Support for Java 1.4 u Lots more….

Corporation For National Research Initiatives Other Efforts u OpenURL –Fat URL coming out of Library community –Used to solve the Appropriate Copy problem –Being proposed as a general interface to DOI world u Interparty –Interop across rights clearinghouses, library authority files, etc u Internet Digital Rights Management (IDRM) Group

Corporation For National Research Initiatives Technical Developments: DOI Evolving Functionality u Parameter passing –Carrying information in the URLhttp://dx.doi.org –Crossref prototype –OpenURL u Debate on data models and service architecture –Great potential flexibility t Given an ID, what can you get t How do you understand what you get –Moving targets t Web services, semantic web, Grid computing t XML DTD, XML Schema, RELAX NG u Adobe focus –Move forward with prototype, get RA buy-in

Corporation For National Research Initiatives DOI as Enabling Framework for Managing Content u Simple Goal: Build a framework for coherent management of content in an evolving digital realm –Make sure your intended audience can find it –Associate related information and services both now and later –Maintain integrity of original content u Complicated World: Years and even centuries of practice disrupted by technology –Content no longer physically fixed, but in motion and highly mutable –Digital entities have value, in the creation, but can be duplicated and disseminated at no cost –Digital convergence pushing content out of its familiar boundaries –Technology is accelerating u Persistent, manageable, and actionable identifier is a foundation of the needed framework –Basic mechanisms in place: id assignment, management, resolution plus associated metadata creation framework –Need common data models and architectures for extended use of what we have

Corporation For National Research Initiatives Acrobat Plug-in Project as Focus u Use DOI embedded in PDF to extend functionality –Show DOI as useful for item in hand as well as for links –Provide user with new functions/services as they evolve u Handle plug-in made aware of special DOI facilities u Resolve handle/DOI upon rendering u New functions/services driven by resolution result u User interface through customization of tool bar, menu items, dialog boxes

. Demo 1 – Version

Tool Bar Demo 1 – Version XMP

Tool Bar Demo 1 – Version cnri.test.jsn/pdf TYPEDATA last_modified T14:06:03-03:00 DOI Handle Record T14:06:03-03:00 Internet Handle System

Tool Bar Demo 1 – Version

Demo 2 – MultiRes

XMP

Demo 2 – MultiRes urlhttp:/ doi.multires doi.kmd cnri.rest.jsn/multires Penguin Books October 16, 2001 intangible manifestation visual en A Tale of Two DOIs Charles Dickens Author cnri.test.jsn/multires Internet

Demo 2 – MultiRes XMP

Demo 2 – MultiRes urlhttp:/ doi.multires doi.kmd cnri.rest.jsn/multires Penguin Books October 16, 2001 intangible manifestation visual en A Tale of Two DOIs Charles Dickens Author cnri.test.jsn/multires Internet

Demo 2 – MultiRes

urlhttp:/ doi.multires doi.kmd cnri.rest.jsn/multires Penguin Books October 16, 2001 intangible manifestation visual en A Tale of Two DOIs Charles Dickens Author cnri.test.jsn/multires Internet

Demo 2 – MultiRes

Demo 3 – CrossRef

Tool Bar Demo 3 – CrossRef XMP

Tool Bar Demo 2 – CrossRef Handle System cnri.test.jsn/crossref TYPEDATA doi.xref DOI Handle Record Internet

Tool Bar Demo 3 – CrossRef XMP

Tool Bar Demo 3 – CrossRef

Tool Bar Demo 3 – CrossRef

Tool Bar Demo 3 – CrossRef

Demo 4 – Rights

Tool Bar Demo 4 – Rights XMP

Demo 4 – Rights Handle System cnri.test.jsn/doi.rights TYPEDATA DOI Handle Record Internet

Tool Bar Demo 4 – Rights XMP

Tool Bar Demo 4 – Rights

Tool Bar Demo 4 – Rights

Corporation For National Research Initiatives What Have We Done u Put the DOI data in functional units in the handle record and the knowledge of what to do with them in the client u Demonstrated with an end-user client (Acrobat) but equally applicable to middleware u No constraints on adding additional functional units to a given DOI –Added flexibility and simplicity –Reduced ability to verify integrity across functional units u No attempts at on-the-fly bootstrapping for introducing new functionality to existing clients –Will require an updating process for clients

Corporation For National Research Initiatives A Namespace for DOI Functions 0.TYPE/doi.multiresINDEXTYPE*DESCRIPTION* view_doi-uri_templatehttp://host-4-211/doi/multires_proxy.py?doi=%DOI mime text/plain | text/xml | TYPE/doi.kmd url mime INDEXTYPE*DESCRIPTION* text/plain | text/xml | 1 2 3

Corporation For National Research Initiatives A Note on XMP u XMP access hooks in Acrobat but not Reader –Considered too much bloat for Reader –Presumably could change over time u Two choices –Put the DOI someplace else -- PDF metadata –Create our own hooks u Weve tried both –Demos based on Acrobat –Also developed a version that reads non-XMP metadata

Corporation For National Research Initiatives What Next u Bring together the RA tech reps to roll out significant prototype –Need experience with additional data, real users –Decision on XMP –Go beyond PDF u Package it up and roll it out –License –Management of new functions: some sort of vetting process