1. Open Name Services names.oclc.org Keith Shafer Office of Research

2. Introduction  Every object has a name  A URL is a pointer, not a name  Many naming efforts on the Web –URNs, PURLs, Handles, DOIs –Introduced new protocols –Did not separate names from services

3. “Old” Names  What about ISBN, ISSN, etc.? –Large number of existing names –Services: buy, borrow, cover image, … –Large investment in systems

4. Our Research  Bring standard names to the Web –provide services on those names –not a new name authority –not a large database of names  Trusted third party –service registering and profiling –user customization –authentication

5. How?  Embed name in a URL  URL has four parts: –Standard http:// portion –Name type –Optional service request –Actual name http://… / NAME-TYPE / SERVICE / NAME

6. Examples http://names.oclc.org / isbn / title-author / ISBN# http://names.oclc.org / isbn / title-author / 0-517-01505-6

8. Service Request is Optional http://names.oclc.org / isbn / ISBN# http://names.oclc.org / isbn / 0-13-603051-3

19. Complex Requests  Service requests may be long or require parameters  Supporting OpenURL, a proposal that came out of the SFX research  SFX is now owned by Ex Libris –provides a customizable “what’s related” service

24. Managing Relationships  Most services will be provided by external partners  Fosters building and maintaining relationships in and among OCLC members and external providers

27. Wrap-Up  Separate names and services  Requests simple enough to hand enter, complete enough for services like SFX  Hope that some OCLC services will soon be offered this way  Need community involvement