1 / 31

Resolution issues and DOI

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

bryant
Download Presentation

Resolution issues and DOI

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Resolution issues and DOI doi>

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

  3. Web Browser DOI? Local Client URL abc.doc Handle resolution Global Handle System abc www.pub.com

  4. Handle query GHS LHS LHS LHS Client LHS Handle system: a collection of Handle services each of which consists of one or more Handle servers HS1 HS4 loc.ndlp/amrlp.123456 HS2 HS3 each of which may be replicated URL URL http://www.loc.gov/..... http://www.loc2.gov/..... Handle record Handle resolution

  5. Handle • CNRI (www.handle.net); open standard • Proven • Scalable: # steps to get to any one Handle is independent of number of Handles in existence • A layer: DOI Other HDL apps Handle http, other protocols TCP/IP TCP/IP Physical net Physical net

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

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

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

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

  10. There are two types of Handle query 1. Request all data 2. Request all data of a given type (Because Handle is a lightweight efficient protocol)

  11. Handle Client Handle System 10.1000/123 URL URL URL PK EM IP URL1(Server in US) URL2 (Server in Asia) URL3 (Server in Europe) public key email address rights data 3 2 5 10 9 4 Handle Index Type Data There are two types of Handle query 1. Request all data “Give me all data associated with 10.1000/123”

  12. There are two types of Handle query 2. Request all data of a given type “Give me all data of type URL associated with 10.1000/123” Handle Client Handle Index Type Data 10.1000/123 URL1(Server in US) URL2 (Server in Asia) URL3 (Server in Europe) 3 2 5 URL URL URL Handle System In each type of query, the client could then do something else with the data it gets back.

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

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

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

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

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

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

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

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

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

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

  23. From theory to practice • We’ve published some analysis: • “One to many” • We’re working on implementations (MD type) • We’ve been doing some experiments: • CNRI + IDEAL + CrossRef + DLF + SFX Framework www.sfxit.com

  24. Example issue: getting the appropriate copy • 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; (etc.) • so I want to go to the “appropriate copy” • rights issues (access control) are implicit • wider issue is context (“contextualisation”) • other reasons (paper copies, other services, etc.)

  25. appropriate full text appropriateabstract

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

  27. XYZ University 10.1000/123?cookie dx.doi.org Understands SFX Cookies Redirect to local SFX Server Client Handle System Local SFX Server Metadata? Article with CrossRef Link Metadata localCopy.html CrossRef First experiment (CrossRef) “hardcoded”

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

  29. Parameters 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

  30. So: • 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) !

More Related