270 likes | 372 Vues
Explore the importance of standard names in web services at the Office of Research. Learn how to embed names in URLs, manage relationships, and foster community involvement for seamless service provision.
E N D
Open Name Servicesnames.oclc.orgKeith ShaferOffice of Research
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
“Old” Names • What about ISBN, ISSN, etc.? • Large number of existing names • Services: buy, borrow, cover image, … • Large investment in systems
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
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
Examples http://names.oclc.org /isbn /title-author /ISBN# http://names.oclc.org /isbn /title-author /0-517-01505-6
Service Request is Optional http://names.oclc.org /isbn/ISBN# http://names.oclc.org /isbn/0-13-603051-3
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
Managing Relationships • Most services will be provided by external partners • Fosters building and maintaining relationships in and among OCLC members and external providers
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