Web 2.0 and repositories - have we got our repository architecture right?
For the record... this is the presentation I gave at the Talis Xiphos meeting last week, though to be honest, with around 1000 Slideshare views in the first couple of days (presumably thanks to a blog entry by Lorcan Dempsey and it being 'featured' by the Slideshare team) I guess that most people who want to see it will have done so already:
Some of my more recent presentations have followed the trend towards a more "picture-rich, text-poor" style of presentation slides. For this presentation, I went back towards a more text-centric approach - largely because that makes the presentation much more useful to those people who only get to 'see' it on Slideshare and it leads to a more useful slideshow transcript (as generated automatically by Slideshare).
As always, I had good intentions around turning it into a slidecast but it hasn't happened yet, and may never happen to be honest. If it does, you'll be the first to know ;-) ...
After I'd finished the talk on the day there was some time for Q&A. Carsten Ulrich (one of the other speakers) asked the opening question, saying something along the lines of, "Thanks for the presentation - I didn't understand a word you were saying until slide 11". Well, it got a good laugh :-). But the point was a serious one... Carsten admitted that he had never really understood the point of services like arXiv until I said it was about "making content available on the Web".
OK, it's a sample of one... but this endorses the point I was making in the early part of the talk - that the language we use around repositories simply does not make sense to ordinary people and that we need to try harder to speak their language.