70 likes | 81 Views
Learn about reducing costs and barriers through interoperability efforts, explore RSS vs. Atom usage, understand web architecture principles, and discover addressing aggregation and URL strategies.
E N D
If you don’t remember anything else, remember these… Peter Cliff, Research Officer, UKOLN, University of Bath, UK SUETr Interoperability Workshop, The LSE Library, December 2008 UKOLN is supported by: This work is licensed under a Creative Commons LicenseAttribution-ShareAlike 2.0
Over to you… • Write on a piece of paper the one thing you learnt today that you do not want to forget
Some things • Interoperability is about improving your chances of reducing costs/barriers • Interoperability takes effort • RSS is on its way out, use Atom • Web architecture
More things… • Addressable resources • How else will you describe an aggregation? • Cool URIs • http://www.w3.org/Provider/Style/URI • Announce your interfaces • SWORD/OAI-PMH base URLs • Use standards • But consider the motivations behind them & are they adopted?
More things • Check if anyone is doing what you want to do and steal from/help them • Good APIs project • DRIVER report • Ensure you are meeting user needs • Don’t get hung up on “doing it the Web 2.0” || “Semantic Web” way – just do something • Remember the simple things: robots.txt, open HTTP access to resources, etc. • Compromise
Summary • Demonstrated ways of getting content in • Demonstrated ways of getting content out and facilitating novel uses of that content • Seen some ways to describe that content • Not just technologies, but it’s a start