Yahoo’s Tom Coats was of seven star speakers at Carson Workshops‘ Future of Web Apps Summit last month. As usual, Ryan Eby was pretty quick to point out his slides to me, mostly by way of pointing out Jeremy Zawodny’s translation of them.
If it’s not clear yet: I wasn’t there, though I very much wanted to be, especially given some of what can be found in the post-summit blog posts.
Still, there’s a lot to be learned from just this one slide:
- Look to add value to the Aggregate Web of data
Â
- Build for normal users, developers, and machines
Â
- Start designing with data, not pages
Â
- Identify your first order objects and make them addressable
Â
- Use readable, reliable, and hackable URLs
Â
- Correlate with external identifier schemes
Â
- Build list views and batch manipulation interfaces
Â
- Create parallel data services using standards
Â
- Make your data as discoverable as possible
I’ve been making a lot of noise about Coates’ point number five in my own presentations about how to build an OPAC for Web 2.0 (though the lesson should be applied to every library application), but there’s a lot to like in all nine. And it’s a bunch easier to understand his point when you read Zawodny’s take on it.
Here are my favorite bits:
Use readable, reliable, and hackable URLs
If the URL is hard to read over the phone or wraps in email, you’re not there yet. Simplicity and predictability rule here. Consider something like http://socialshopping.com/item/12345. You can guess what that URL does, can’t you?
You may not grasp how important this is, but don’t let that stop you from worry about it. This stuff really does matter. Look at how most URLs in del.icio.us are guessable and simple. Mimic that.
Correlate with external identifier schemes
Don’t go inventing complete new ways to represent and/or structure things if there’s already an established mechanism that’d work. Not only is such effort wasteful, it significantly lowers the chance that others will adopt it and help to strengthen the platform you’re building.
You are building a platform, whether you believe it or not.
Create parallel data services using standards
Developers (and the code they write) will want to consume your data. Do not make this an afterthought. Get your engineers thinking about how they might use the data, and make sure they design the product to support those fantasies. Again, always default to using an existing standard or extending one when necessary. Look at how flexible RSS and Atom are.
Don’t re-invent the wheel [link added --Casey].
Make your data as discoverable as possible
The names and attributes you use should be descriptive to users and developers, not merely a byproduct of the proprietary internal system upon which they’re built. This means thinking like an outsider and doing a bit of extra work.
application design, Carson Workshops, FoWA, future of web apps, future of web apps summit, lib20, library 2.0, native to web, native to web of data, summit, tom coates, web 2.0, web applications, web design, web platform
Posted March 16, 2006 by Casey Bisson
Categories: Libraries & Networked Information, Technology. Tags: application design, Carson Workshops, FoWA, future of web apps, future of web apps summit, lib20, library 2.0, native to web, native to web of data, summit, tom coates, web 2.0, web applications, web design, web platform.
4 Comments
Comments RSS
TrackBack Identifier URI
Leave a comment
User contributed tags for this post:
iPhone porno (34) - native porno (31) - سكس3 (21) - porn webapp (18) - 12345 sex com (16) - native porn (15) - porn Apps (12) - 12345 sex (11) - Porno for iPhone (10) - tom coats (9) - http://www google com/m/st/gp202/search html (8) - Porn webapps (7) - future (7) - Porno native (6) - about (5) - iphone porn webapp (5) - 12345sexcom (4) - iPhone porn webapps (3) - 12345 sex.com (3) - porno en iphone (3) - coolest web apps (3) - iPhone porn apps (3) - webapps future (2) - porno in iPhone (2) - porno na iphone (2) - porno sur iphone (2) - uplapps:8509/ (2) - iPhone native porn (2) - porn web apps iPhone (2) - iphoneporno (2) - native iphone porn (2) - webapps sex (2) - iphone pornomovies (2) - http://www google com/m/html/search2 html (2) - www.sex.com 12345 (2) - porn web apps (2) - Porno app (2) - iphone webapps porn (2) - porno für iphone (2) - native vs web apps (2) - native prno mivies (2) - pretty urls tom coates (2) - readable reliable and hackable (2) - opac (2) - native sex movies (2) - hate web apps (2) - cool web apps (2) - site:maisonbisson.com sexs. batsh (2) - what native web applications (2) - tom coats yahoo (2) - web app native look (2) - 1porno (2) - native to (2) - iphon porn (2) - plasticbag org (2) - porno on Iphone (2) - identify Web 2 0 (2) - tom coates fowa slides (2) - readable reliable hackable (1) - porno apps for iPod (1) - sex web apps iphone (1) - Porno iphon (1) - www.sex mivies.com (1) - iphone native versus web applications (1) - داستان سكس3 (1) - porno web (1) - iPhone sexual webapp (1) - porno web apps (1) - THEY COOL SEX.COM (1) - sex prno move and photo (1) - readable reliable hackable url (1) - Porno for iphon (1) - iPhone porn webaps (1) - webapps sex for iPhone (1) - داستان هاي سكس3 (1) - porn web app for iPod (1) - porn to iphon pod (1) - webapps porn (1) - ipod porn apps (1) - webcool porn (1) - nativ porn (1) - native iPhone porn app (1) - porn iphone webapp (1) - iPod porno app (1) - Iphone porn native app (1) - porno na iphon (1) - Webapps para iphone de porno (1) - native webapps (1) - xxl sex tv batsh (1) - amazon native porn (1) - www.theycool.com (1) - porno 12345 (1) - iPhone native porn apps (1) - native porn app for iphone (1) - future of webapps iphone (1) - native sex.com (1) - Porno movies for iphon (1) - Native porn apps on ipod (1) - 12345 XXL (1) - webapps porno (1) - native to web of data (1) - tom coates hackable (1) - readable reliable hackable urls (1) - native sexs (1) - Tom Coates Future of Web Apps 2006 presentation (1) - sex be far the girls com (1) - Tom Coates of Yahoo at fowa (1) - london weather (1) - sexs coates (1) - Tom Coats Future of Web Apps (1) - NATIVE INDIAN ART on eby (1) - iPhone porn (1) - tom coats future of web apps presentation (1) - tom coats future web (1) - hackable urls (1) - item sexs for man order (1) - cache GUYl6kA89owJ simon incutio com archive 2006 02 08 (1) - Future of web apps 2006 tom coats (1) - Native Web Apps (1) - t re cool (1) - socialshopping com (1) - everyone is irish with a quart of whiskey in them (1) - use readable reliable and hackable urls (1) - wpopac sru (1) - i hate web apps (1) - Porn webapps for iPhone (1) - sex apps iphone (1) - porn apps for iPhone (1) - Iphone porn web apps (1) - native porn apps iphone (1) - sex 12345 xxl (1) - web apps porno (1) - porno dans iphone (1) - porno web application for iPhone (1) - Iphone webapps sex (1) - iPhone porno free porno movies for iphone (1) - http://maisonbisson com/blog/post/11178 (1) - http://www google com/m/st/gp203/search html?gl=us (1) - Porn web apps for iPhone (1) - web apps sex (1) - webapps iphone porno (1) - native sex com (1) - iphone porno apps (1) - sex webapps (1) - web apps iphone porno (1) - ipod webapps porn (1) - iPhone porno app listing (1) - how to see my native in google earth com (1) - porno auf iphone (1) - web cool 69 com (1) -
Well, to be fair… MARC/MODS and SRU aren’t really reinventing the wheel. Amazon reinvented the wheel (regardless of whether or not they were more successful at it). All of those technologies existed before their AWS counterpart.
However, point #5 is much more difficult than just /item/isbn/1234567890x in most real world scenarios.
Take articles for instance. Yes, some may have standard identifiers (dois, pmids, etc.), but many, many do not. And the doi isn’t even that friendly, anyway.
As I struggle to make a link resolver that “works better”, I’m still finding it nigh-on-impossible to improve on the readability of the openurl (and still actually be able to resolve anything).
I’m not sure #5 is ultimately all that important (although, yes, containing all of the information in a hash or behind session identifiers is wrong — and maybe what you’re actually getting at).
[tags]standards, rebuttal[/tags]
Ross,
I’m not sure how I feel about being typecast as the anti-SRU guy, but your points are valid.
I’ll quickly agree that the challenge of making openurl readable is probably insoluble, but let’s at least make the URLs in our apps durable enough to be bookmarkable, blogable, IMable, emailable, and indexable (so it’s Googleable(?)).
Now back to “standards…” The’ slides are good, but they don’t speak to your first point about priority and reinvention. What Coates couldn’t say, because the decision was made far above his head, was that successful organizations know when to change their game. Yahoo!’s acquisition of so many internet properties (and Coates himself) in the past year shows they know this.
What would we think of Yahoo! if they’d stuck to their old game? Would we respect them for claiming they did internet portals first? Would we care?
We need to think critically about our standards. MARC and SRU and others we love (and love to hate) may have been first, but there are substantially similar standards in broader use outside libraries.
[...] Readable, reliable, and hackable URLs are among my favorite things ever, and not just because Tom Coates says they’re cool. I like them because they make the internet work. [...]
[...] reliable, and hackable URLs are among my favorite things ever, and not just because Tom Coates says they’re cool. I like them because they make the internet [...]