1. DOI and STM doi>

2. A consistent extensible system –full implementation –is interoperable with other standards Supported by the publishing industry –publishers, and intermediaries Strong support from technology community –Microsoft, Hewlett-Packard, and others Not a proprietary solution –owned by the community (anyone can join) –available at cost DOI: so what have we got? tomorrow

3. POLICIES Any form of identifier NUMBERING DESCRIPTION framework: DOI can describe any form of intellectual property, at any level of granularity ACTION Handle resolution allows a DOI to link to any and multiple pieces of current data doi> extensible

4. one issue: appropriate copy illustrates how description (metadata) works with action (resolution) more detail than tomorrows overview relevant for STM community (CrossRef) This talk

5. I have found what I want to link to, but: –I have a copy locally; or –I use an aggregator; or –The publisher provides alternative sources; or –I am linked to an authorised E-print archive; or –It is available in a public archive (etc) so I want to go to the appropriate copy –rights issues (access control) are implicit Getting the appropriate copy

6. appropriate full text appropriate abstract

7. Web Browser Local Client Local collection Global Resolution System DOI:10.123/456? DOI:10.123/456 10.123/456 = http://local/abc.html redirect - http://local/abc.html http://local/abc.html www.pub.com Local Network/Environment (Harvard) Cache/Proxy abc Initial thoughts on solution (1998)

8. Web Browser Local Client Local collection Global Resolution System DOI:10.789/abc ? DOI:10.789/abc http://www.pub.com/abc.html www.pub.com DOI:10.789/abc http://www.pub.com/abc.html abc.html Cache/Proxy ? Local Network/Environment (Harvard) abc Initial thoughts on solution (1998) magic box?

9. The magic box is impractical Is there a better way? Solving the appropriate copy problem

10. Is there a better way? –Use the Handle resolution capabilities 1. Context of DOIs –make a DOI click dependent on context 2. Parameters –rules about what to do with DOIs which can be passed on (to be dealt with outside DOI system) Shows how metadata and resolution interact Solving the appropriate copy problem

11. 3 Handle dataDOIData type Index 10.123/456 URL http://srv1.pub.com/..... 3 URL http://srv2.pub.com/..... 2 9 URL http://srv3.pub.com/..... 5 9 MD http://lu.cr.com/10.123.. 10 999 EM Accounts@pub.com 9 9 IP 10.456/789 4 Background: DOIs resolve to Typed Data DOIHandle data

12. 3 DOIData type Index 10.123/456 URL http://srv1.pub.com/..... 3 URL http://srv2.pub.com/..... 2 9 URL http://srv3.pub.com/..... 5 9 MD http://lu.cr.com/10.123.. 10 999 EM Accounts@pub.com 9 9 IP 10.456/789 4 DOIs resolve to Typed Data Multiple typed values per DOI

13. 3 Handle dataDOIData type Index 10.123/456 URL http://srv1.pub.com/..... 3 URL http://srv2.pub.com/..... 2 9 URL http://srv3.pub.com/..... 5 9 MD http://lu.cr.com/10.123.. 10 999 EM Accounts@pub.com 9 9 IP 10.456/789 4 DOIs resolve to Typed Data Extensible typing

14. 3 Handle dataDOIData type Index 10.123/456 URL http://srv1.pub.com/..... 3 URL http://srv2.pub.com/..... 2 9 URL http://srv3.pub.com/..... 5 9 MD http://lu.cr.com/10.123.. 10 999 EM Accounts@pub.com 9 9 IP 10.456/789 4 DOIs resolve to Typed Data Query by type

15. There are two types of Handle query 1. Request all data 2. Request all data of a given type

16. There are two types of Handle query 1. Request all data Handle System Give me all data associated with 10.1000/123 Handle Client 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

17. 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 10.1000/123 Handle Client 2. Request all data of a given type Handle System In both types of query, the client could then do something else with the data it gets back. So… There are two types of Handle query

18. Some Other Process (1) Handle System (2) 3 2 5 10 9 4 10.1000/39505468499584974URL1(Server in US) URL2 (Server in Asia) URL3 (Server in Europe) public key email address rights data URL PK EM IP Some other handle aware process uses a DOI to contact the Handle System and request all URLs associated with that DOI... doi:10.1000/39505468499584974 Internet Future resolution (1)

19. URL1 (Server in US) URL2 (Server in Asia) URL3 (Server in Europe) Handle System (3) 325325 10.1000/39505468499584974 URL... and then ranks those URLs based on performance or best location... Some Other Process Future resolution (1)

20. URL2 (Server in Asia)... chooses the best one, and resolves it. (4) URL2 (Server in Asia) Some Other Process Future resolution (1)

21. A process might use an email address, rights data, or any other current state data. Handle System (2) (3) 3 2 5 10 9 4 10.1000/46578 URL1(US) URL2 (Asia) URL3 (Europe) public key email address rights data URL PK EM IP doi:10.1000/46578 (1) (4) rights data Some Other Process Interoperable metadata! Future resolution (1)

22. (1) XML file with embedded DOI User clicks on a DOI embedded in an XML document. Future Application with native understanding of handles and XML doi:10.1000/5467 Future resolution (2)

23. The application connects to the Handle System... Future Application with native understanding of handles and XML Handle System (2) 32943294 10.1000/5467http://www.pub.org/ http://rights.explain/ help@acme.com http://crossref.org/... URL IP EM MD Future resolution (2)

24. ... and retrieves DOI data. Future Application with native understanding of handles and XML (3) 32943294 10.1000/5467http://www.pub.org/ http://rights.explain/ help@acme.com http://crossref.org/.. URL IP EM MD Future resolution (2) Handle System

25. Application analyzes the data associated with that DOI. Future Application with native understanding of handles and XML http://www.pub.org/ http://rights.explain/ help@acme.com http://crossref.org/.. URL IP EM MD Interoperable metadata! Future resolution (2)

26. and dynamically displays for the user a list of options based on the data in the DOI System. Future Application with native understanding of handles and XML (5) XML file with embedded DOI 1. Retrieve document 2. Explain rights 3. Email query 4. Show metadata Future resolution (2) mouseover

27. User clicks on which path to follow. Future Application with native understanding of handles and XML (6) XML file with embedded DOI metadata record 1. Retrieve document 2. Explain rights 3. Email query 4. Show metadata Future resolution (2)

28. Weve published some analysis: –One to many Were working on implementations (MD type) Weve been doing some experiments: –CNRI + IDEAL + CrossRef + DLF + SFX Framework www.sfxit.com From theory to practice

29. 10.1000/123 http://acme.com/pg1.html 10.1000/123 pg1.html Article with CrossRef Link Client XYZ University Local copy DOI as used by CrossRef Handle System dx.doi.org acme.pub proxy

30. 10.1000/123?cookie 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 First experiment (CrossRef) hardcoded

31. 10.1000/123?cookie Redirect to local SFX Server Metadata location? Meta1.com Handle System dx.doi.org Understands SFX Cookies Meta1.com Metadata Collection Service XYZ University Client Article with CrossRef Link Local SFX Server localCopy.html Metadata? Metadata Second experiment (CrossRef) Metadata indirection

32. instructions to client when it gets a DOI (so that it can then do something else…): on interacting with whole handle –e.g. type=PK; query=Authoritative on actions to take with a returned value –e.g. URL?source=JournalABC on actions to take with a returned object –loc=chap23 syntax under discussion (Open URL?) Parameters

33. extensible framework can cope with anything we want it to do –spreadsheet analogy requires logical framework for identification, metadata (indecs) requires prototypes, –DOI-X, DOI-EB, DOI-R, etc requires software developers to adopt –Microsoft E-Book reader, etc requires thinking (business requirements) ! So:

34. Wednesday, Europa (Hall 4) 9.15 Annual Review 2000 CD-ROM overview Handbook on web site –www.doi.org DOI: Review of progress doi> ANNUAL REVIEW September 2000 The International DOI Foundation

35. Where do I go? - Registration agencies, applications - Information pack for RAs, Letter of Intent - Handbook etc on web site What can it do? - analogy: spreadsheets - increased marketing - more efforts for outreach - workshops - both general and specific areas Next steps: Marketing

36. Easier use of the technology –documentation, tools Evolving functionality –More prototypes (DOI-X; DOI-EB, DOI-R) Other intellectual property activities: –W3C, WIPO, MPEG-21, cIDF, SMPTE, SFX, etc –Existing identifiers (ISBN, ISSN, etc) –New identifiers (e.g. ISTC; E-books) –common issues for identifiers Major theme: interoperability Continuing development will be necessary Next steps: other work to be done

37. STM Task Force on Information Identifiers and Metering Systems in the Electronic Environment –Arnoud de Kemp (chair): Dec 1994 Innovations meeting Information identification - Armati Report, 1995 DOI, indecs, ONIX…… CrossRef… Five years on….