1 / 36

Handle - Technical Update

Handle - Technical Update. Larry Lannom CNRI Sept 20, 2002. Technical Developments: 2001/02 Maturation. Increase in numbers - 5M+ DOIs New backend db New admin facilities Increased scope of application areas Learning objects Images Increased scope of research interest

jola
Download Presentation

Handle - Technical Update

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. Handle - Technical Update Larry Lannom CNRI Sept 20, 2002

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

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

  4. Other Efforts • OpenURL • ‘Fat URL’ coming out of Library community • Used to solve the Appropriate Copy problem • Being proposed as a general interface to DOI world • Interparty • Interop across rights clearinghouses, library authority files, etc • Internet Digital Rights Management (IDRM) Group

  5. Technical Developments: DOIEvolving Functionality • Parameter passing • Carrying information in the http://dx.doi.org URL • Crossref prototype • OpenURL • Debate on data models and service architecture • Great potential flexibility • Given an ID, what can you get • How do you understand what you get • Moving targets • Web services, semantic web, Grid computing • XML DTD, XML Schema, RELAX NG • Adobe focus • Move forward with prototype, get RA buy-in

  6. DOI as Enabling Framework for Managing Content • 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 • 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 • 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

  7. Acrobat Plug-in Project as Focus • 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 • Handle plug-in made aware of special DOI facilities • Resolve handle/DOI upon rendering • New functions/services driven by resolution result • User interface through customization of tool bar, menu items, dialog boxes

  8. Demo 1 – Version .

  9. XMP Demo 1 – Version Tool Bar

  10. Demo 1 – Version HandleRecord DOI TYPE DATA Tool Bar cnri.test.jsn/pdf url http://host-4-211/book-newversion.pdf http://host-4-211/book-newversion.pdf last_modified 2002-06-13T14:06:03-03:00 2002-06-13T14:06:03-03:00 Handle System Internet

  11. Demo 1 – Version Tool Bar

  12. Demo 2 – MultiRes

  13. XMP Demo 2 – MultiRes

  14. Internet Demo 2 – MultiRes doi.multires <?xml version=“1.0”?> <!DOCTYPE multires SYSTEM “multires.dtd”> <multires> <node label=“Publisher’s Catalog Page” href=“http://www.mcgrawhill.com”/> <node label=“Read a Free Excerpt” href=“http://www.mcgrawhill.com/excerpt”/> <node label=“Buy This Book”> <node label=“Microsoft Reader”> <node label=“Amazon.com” href=http://www.amazon.com/isbn=120319”/> <node label=“Barnes &amp; Noble href=http://www.amazon.com/isbn=120319/> <nod label=“Contentville” href=http://www.contentville.com/> url http:/www.penguinbooks.com/0-465-03032-7 doi.kmd <?xml version=“1.0”?> <!DOCTYPE Kernel SYSTEM “doikernel-1.0.dtd”> <Kernel xmlns:doi=http://www.doi.org/namespace/> <Identifier>cnri.rest.jsn/multires</Identifier> <Assertor> <Registrant id=“publishers:123321”>Penguin Books</Registrant> <Date>October 16, 2001</Date> </Assertor> <Entity> <Type>intangible manifestation</Type> <Mode>visual</Mode> <Title> <Language>en</Language> <TitleValue>A Tale of Two DOIs</TitleValue> <Agent id=“authors:223453”> <Person>Charles Dickens</Person> <Role>Author</Role> </Agent> </Entity> </Kernel> cnri.test.jsn/multires

  15. XMP Demo 2 – MultiRes

  16. Internet Demo 2 – MultiRes doi.multires <?xml version=“1.0”?> <!DOCTYPE multires SYSTEM “multires.dtd”> <multires> <node label=“Publisher’s Catalog Page” href=“http://www.mcgrawhill.com”/> <node label=“Read a Free Excerpt” href=“http://www.mcgrawhill.com/excerpt”/> <node label=“Buy This Book”> <node label=“Microsoft Reader”> <node label=“Amazon.com” href=http://www.amazon.com/isbn=120319”/> <node label=“Barnes &amp; Noble href=http://www.amazon.com/isbn=120319/> <nod label=“Contentville” href=http://www.contentville.com/> url http:/www.penguinbooks.com/0-465-03032-7 doi.kmd <?xml version=“1.0”?> <!DOCTYPE Kernel SYSTEM “doikernel-1.0.dtd”> <Kernel xmlns:doi=http://www.doi.org/namespace/> <Identifier>cnri.rest.jsn/multires</Identifier> <Assertor> <Registrant id=“publishers:123321”>Penguin Books</Registrant> <Date>October 16, 2001</Date> </Assertor> <Entity> <Type>intangible manifestation</Type> <Mode>visual</Mode> <Title> <Language>en</Language> <TitleValue>A Tale of Two DOIs</TitleValue> <Agent id=“authors:223453”> <Person>Charles Dickens</Person> <Role>Author</Role> </Agent> </Entity> </Kernel> cnri.test.jsn/multires

  17. Demo 2 – MultiRes

  18. Internet Demo 2 – MultiRes doi.multires <?xml version=“1.0”?> <!DOCTYPE multires SYSTEM “multires.dtd”> <multires> <node label=“Publisher’s Catalog Page” href=“http://www.mcgrawhill.com”/> <node label=“Read a Free Excerpt” href=“http://www.mcgrawhill.com/excerpt”/> <node label=“Buy This Book”> <node label=“Microsoft Reader”> <node label=“Amazon.com” href=http://www.amazon.com/isbn=120319”/> <node label=“Barnes &amp; Noble href=http://www.amazon.com/isbn=120319/> <nod label=“Contentville” href=http://www.contentville.com/> url http:/www.penguinbooks.com/0-465-03032-7 doi.kmd <?xml version=“1.0”?> <!DOCTYPE Kernel SYSTEM “doikernel-1.0.dtd”> <Kernel xmlns:doi=http://www.doi.org/namespace/> <Identifier>cnri.rest.jsn/multires</Identifier> <Assertor> <Registrant id=“publishers:123321”>Penguin Books</Registrant> <Date>October 16, 2001</Date> </Assertor> <Entity> <Type>intangible manifestation</Type> <Mode>visual</Mode> <Title> <Language>en</Language> <TitleValue>A Tale of Two DOIs</TitleValue> <Agent id=“authors:223453”> <Person>Charles Dickens</Person> <Role>Author</Role> </Agent> </Entity> </Kernel> cnri.test.jsn/multires

  19. Demo 2 – MultiRes

  20. Demo 3 – CrossRef

  21. XMP Demo 3 – CrossRef Tool Bar

  22. Demo 2 – CrossRef HandleRecord DOI TYPE DATA Tool Bar cnri.test.jsn/crossref doi.xref Handle System Internet

  23. XMP Demo 3 – CrossRef Tool Bar

  24. Demo 3 – CrossRef Tool Bar

  25. Demo 3 – CrossRef Tool Bar

  26. Demo 3 – CrossRef Tool Bar

  27. Demo 4 – Rights

  28. XMP Demo 4 – Rights Tool Bar

  29. Demo 4 – Rights HandleRecord DOI TYPE DATA cnri.test.jsn/doi.rights doi.rights http://kaluha/~jpetrone/doi_rights.html Handle System Internet

  30. XMP Demo 4 – Rights Tool Bar

  31. Demo 4 – Rights Tool Bar

  32. Demo 4 – Rights Tool Bar

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

  34. 0.TYPE/doi.kmd INDEX TYPE *DESCRIPTION* 1 url http://dx.doi.org/10.1000/182 2 mime text/plain | <Description of DOI kernel metadata> 3 mime text/xml | <XML Schema for kernel metadata> 0.TYPE/doi.multires INDEX TYPE *DESCRIPTION* 1 mime text/plain | <description of multires> 2 mime text/xml | <XML Schema for multires data format > 3 view_doi-uri_template http://host-4-211/doi/multires_proxy.py?doi=%DOI A Namespace for DOI Functions

  35. A Note on XMP • XMP access hooks in Acrobat but not Reader • Considered too much bloat for Reader • Presumably could change over time • Two choices • Put the DOI someplace else -- PDF metadata • Create our own hooks • We’ve tried both • Demos based on Acrobat • Also developed a version that reads non-XMP metadata

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

More Related