1. Corporation For National Research Initiatives 1 DOI Evolution Larry Lannom CNRI May 17, 2001

2. Corporation For National Research Initiatives DOI History u AAP: 1996 - 1997 –content identifier necessary for IP management –location-based id (URL) not sufficient –CNRI Handle System u IDF: 1998 - present –non-profit, member based –develop policy layer on top of technology –metadata requirement added in 1999 (indecs) –Crossref for journal linking - 2000 –extending to e-books, other media

3. Corporation For National Research Initiatives Technical Evolution u One to one –one DOI (fixed) resolves to one URL (can change) –that URL = unconstrained publisher ‘response page’ u One to many –one DOI resolves to mulitple typed values, aka, multiple resolution t more than location - metadata pointers, owenership, etc. t value types fixed by application profile t multiple application profiles t beginning of Service Layer - given a DOI what can I get? –one DOI resolvable in multiple contexts t appropriate copy t contextualized by person, location, source, etc.

4. Corporation For National Research Initiatives DOIs Resolve to Typed Data URL2http://www2.pub.com/…. MD9 http://md.com/lookup?10.. PKI100z2ss3323dlkjtddmdssl…. XYZ 1001110011110 12 Handle data Handle Data type Index 10.123/456URL1http://www.pub.com/….

5. Corporation For National Research Initiatives Two Types of DOI Resolution Handle System Give me all data associated with DOI 10.1000/123. 325325 10.1000/123URL1(Server in US) URL2 (Server in Asia) URL3 (Server in Europe) URL IndexTypeDataHandle Give me all data of type URL associated with DOI 10.1000/123. Handle Client Handle Client 1. Request all data 2. Request all data of a given type 3 2 5 10 9 4 10.1000/123URL1(Server in US) URL2 (Server in Asia) URL3 (Server in Europe) public key email address rights data URL PK EM IP IndexTypeDataHandle Handle System

6. Corporation For National Research Initiatives Services Layer u Application Profile –define standard set of data elements associated with each DOI in a given application profile –each application profile will be registered –each DOI will explicitly be part of one application profile u Services can be built on top of Application Profiles, e.g., –each e-book DOI yields pointer to defined metadata –and each metadata instance contains a synopsis –so a service can be built that takes an ebook DOI and returns a synopsis

7. Corporation For National Research Initiatives Contextualization: Current 10.1000/123 http://acme.com/pg1.html 10.1000/123 Handle System dx.doi.org acme.pub pg1.html Article with CrossRef Link Client XYZ University localCopy.html

8. Corporation For National Research Initiatives Contextualization: First Experiment (Hardcoded CrossRef) Redirect to local SFX Server Handle System dx.doi.org Understands SFX Cookies CrossRef Metadata? Metadata localCopy.html Article with CrossRef Link Client Local SFX Server XYZ University 10.1000/123?cookie

9. Corporation For National Research Initiatives Contextualization: Second Experiment (MD Indirection) Redirect to local SFX Server Metadata location? Meta1.com XYZ University Client Article with CrossRef Link Local SFX Server localCopy.html Metadata? Metadata Handle System dx.doi.org Understands SFX Cookies Meta1.com Metadata Collection Service Meta2.com Metadata Collection Service Meta3.com Metadata Collection Service 10.1000/123?cookie

10. Corporation For National Research Initiatives Contextualization: Second Experiment (MD Indirection/No Local Copy) Redirect to local SFX Server Metadata location? Meta1.com XYZ University Client Article with CrossRef Link Local SFX Server localCopy.html Metadata? Metadata Handle System dx.doi.org Understands SFX Cookies Meta1.com Metadata Collection Service Meta2.com Metadata Collection Service Meta3.com Metadata Collection Service 10.1000/123?cookie X