Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Web 2.0: Behind The Hype Panel

Slides from a talk by Brian Kelly,UKOLN in the "Web 2.0: Behind The Hype" panel session given at the Institutional Web Management Workshop 2006 on 15 June 2006.


  • Login to see the comments

Web 2.0: Behind The Hype Panel

  1. 1. Web 2.0: Behind The Hype Panel Being Web 2.0 – In 30 Minute Steps Brian Kelly UKOLN University of Bath Bath Email [email_address] UKOLN is supported by: Acceptable Use Policy Recording/broadcasting of this talk, taking photographs, discussing the content using email, instant messaging, Blogs, SMS, etc. is permitted providing distractions to others is minimised. This work is licensed under a Attribution-NonCommercial-ShareAlike 2.0 licence (but note caveat)
  2. 2. Contents <ul><li>This brief talk will cover: </li></ul><ul><li>No Web 2.0 … </li></ul><ul><ul><li>The Concerns </li></ul></ul><ul><li>Web 2.0 and IWMW 2006 </li></ul><ul><ul><li>RSS  Mashups </li></ul></ul><ul><ul><li>Blogs  Wikis </li></ul></ul><ul><ul><li>Microformats  Comms tools </li></ul></ul><ul><ul><li>Social bookmarking  … </li></ul></ul><ul><li>Deployment Strategies </li></ul><ul><ul><li>User Focus </li></ul></ul><ul><ul><li>Risk assessment </li></ul></ul>
  3. 3. No Web 2.0 … <ul><li>No Web 2.0 … without responsibility </li></ul><ul><ul><li>Title of talk by Andy Clarke, Stuff & Nonsense at WWW 2006 , May 206 </li></ul></ul><ul><ul><li>Web 2.0 can be useful but need to: </li></ul></ul><ul><ul><ul><li>Learn from mistakes from Web 2.0 </li></ul></ul></ul><ul><ul><ul><li>It will be used by marketers (just like Web 1.0) </li></ul></ul></ul><ul><ul><ul><li>Need to remember accessibility </li></ul></ul></ul><ul><ul><ul><li>Need to be user-focussed </li></ul></ul></ul><ul><ul><ul><li>… </li></ul></ul></ul><ul><li>This talk: </li></ul><ul><ul><li>Describes use of Web 2.0 at IWMW 2006 </li></ul></ul><ul><ul><li>Outlines user-focussed approach </li></ul></ul><ul><ul><li>Recommends use of a risk management approach </li></ul></ul>Web 2.0 and IWMW 2006 Just like the Web in the 1990s!
  4. 4. Don’t Like The Term? <ul><li>Don’t like the Web 2.0 term? Simply use the following XSLT script with the digital audio channel to convert all occurrences of Web 2.0 in talk to your preferred alternative </li></ul><xsl:template match=&quot;text()&quot;>  <xsl:choose>    <xsl:when test=&quot;contains(.,'Web 2.0')&quot;>      <xsl:value-of select=&quot;substring-before(.,'Web 2.0')&quot;/>      <xsl:text>Blogs, Wikis and other Social networking software with a user focus, always beta and a long tail</xsl:text>      <xsl:value-of select=&quot;substring-after(.,'Web 2.0')&quot;/>    </xsl:when>    <xsl:otherwise>      <xsl:value-of select=&quot;.&quot;/>    </xsl:otherwise>  </xsl:choose> </xsl:template> NOTE Due to increased time in saying alternative version, anyone using this will find the talk concludes when everyone else is in the bar XSLT script by Sebastian Rahtz, OSS Watch. OSS licence available.
  5. 5. Latest News <ul><li>Interested in marketing: </li></ul><ul><ul><li>Google for IWMW 2006 or IWMW2006. Where are the top links from? </li></ul></ul><ul><ul><li>And reflect on importance of Wikipedia </li></ul></ul><ul><li>Interested in user-created content: </li></ul><ul><ul><li>Look at Flickr with IWMW2006 tag </li></ul></ul><ul><ul><li>Upload last night’s photos & video clip </li></ul></ul>
  6. 6. RSS & OPML <ul><li>RSS: </li></ul><ul><ul><li>Used at IWMW 2005 for news </li></ul></ul><ul><ul><li>Used at IWMW 2006 for news and syndication of content (talks, parallel sessions) </li></ul></ul><ul><li>OPML (Outline Processor Markup Language): </li></ul><ul><ul><li>Used to group RSS files </li></ul></ul><ul><ul><li>OPML viewers (e.g. Grazr) allows our RSS files to be embedded in others’ Web sites </li></ul></ul>Web 2.0 and IWMW 2006 Why RSS? Widely acknowledged as key news & syndication format. Why OPML? Experimentation in maximising benefits of RSS. Effort : Simple (and trivial if appropriate tools/scripts used). Additional effort may be needed if RSS/OPML become obsolete Syndication
  7. 7. Mashups <ul><li>Mashup - aggregating content from various sources </li></ul><ul><li>IWMW 2006: </li></ul><ul><ul><li>Set up IWMW 2006 Suprgru page </li></ul></ul><ul><ul><li>Content mashup from: </li></ul></ul><ul><ul><ul><li>IWMW 2006 Web site </li></ul></ul></ul><ul><ul><ul><li>Third party services such as Blogs, Wikis, search engines, … </li></ul></ul></ul>Web 2.0 and IWMW 2006 Syndication <ul><li>Risk Assessment </li></ul><ul><li>The Web site is not currently available (Sun 4 Jun) </li></ul><ul><li>Does this mean Web 2.0 concept is flawed? </li></ul><ul><li>Thoughts: </li></ul><ul><ul><li>Little content stored (addresses of RSS feeds and a title) </li></ul></ul><ul><ul><li>Alternatives are available (lots of RSS aggregators, such as Netvibes, PLEX, …) </li></ul></ul><ul><ul><li>Experimentation and learning is a fundamental aspect of what we do! </li></ul></ul>Why? Simple demonstration to encourage debate about the issues. Effort : Simple (fill in a Web form) Experiences : Superglu service not always available (so what, use, PLEX, …)
  8. 8. Blogs <ul><li>Blogs: </li></ul><ul><ul><li>We link to Blogs provided by IWMW 2006 delegates </li></ul></ul><ul><ul><li>We recommend a tag (IWMW2006) to make it easier to find other Blogs, photos, bookmarks, etc. related to the event (e.g. using Technorati ) </li></ul></ul>Web 2.0 and IWMW 2006 Why? Facilitates sharing of thoughts about event. Effort : None – the Bloggers are doing the work! Risks : They say nasty things; upset people; … Blogs Users Syndication
  9. 9. Wikis <ul><li>Wikis: </li></ul><ul><ul><li>Used successfully at IWMW 2005 and UKOLN / UCISA events for note-taking in breakout groups, social use, … </li></ul></ul><ul><ul><li>Available at IWMW 2006: </li></ul></ul><ul><ul><ul><li>UKOLN Wiki (MediaWiki) </li></ul></ul></ul><ul><ul><ul><li>Other Wikis (for various parallel sessions) </li></ul></ul></ul>Web 2.0 and IWMW 2006 workshops/webmaster-2005/wiki-test/ Why? Wikis have proved popular at other UKOLN events Why diversity : To allow us to gain a feel of different Wikis and their strength & weaknesses. Wikis Users Syndication
  10. 10. Podcasts <ul><li>Podcasts: </li></ul><ul><ul><li>Used at IWMW 2005 (prior to general public interest) </li></ul></ul><ul><ul><li>Podcasting session at IWMW 2006 </li></ul></ul> workshops/webmaster-2005/podcasts/podcast.xml Why? Gain experiences at popular technology; explore difference usages and technical and non-technical issues Effort : Non – work being led by workshop facilitator. RSS Users Syndication
  11. 11. Communications: Chat <ul><li>IRC chat facility used successfully at IWMW 2005. </li></ul><ul><li>Gabbly being evaluated: </li></ul><ul><ul><li>If no systems effort available </li></ul></ul><ul><ul><li>On-the-fly chatting </li></ul></ul><ul><li>How long to set up: </li></ul><ul><ul><li>Go to < > </li></ul></ul><ul><ul><li>Create chat on your institution’s home page </li></ul></ul><ul><ul><li>How long? </li></ul></ul><ul><li>This provides on-the-fly creation of chat facilities  </li></ul>Web 2.0 and IWMW 2006 Too good to be true? Suspicious of anything this simple? See risk assessment page Users Collaboration AJAX Syndication
  12. 12. Communications: Sound & Video <ul><li>VoIP, Access Grid technologies, streaming video, … have rich potential in supporting events: </li></ul><ul><ul><li>Speakers who can't travel </li></ul></ul><ul><ul><li>Delegates who can't travel </li></ul></ul><ul><ul><li>Maximising impact </li></ul></ul><ul><ul><li>Reaching potential delegates </li></ul></ul><ul><ul><li>Reaching sceptics </li></ul></ul><ul><ul><li>Just-in-time speakers (cf Blended Learning 2006 conf.) </li></ul></ul><ul><ul><li>Accessibility (slept in/ hungover?!) </li></ul></ul>Issues : Technical difficulties; privacy; trust; business models; … Plans : Evaluate; reflect on issues & act accordingly; …
  13. 13. <ul><li> social bookmarking service available for use to: </li></ul><ul><ul><li>Provide access to resources mentioned in talks & workshops </li></ul></ul><ul><ul><li>Allow others to bookmark related resources </li></ul></ul><ul><ul><li>Allow users to view others’ bookmarks </li></ul></ul><ul><ul><li>Monitor who’s bookmarked your resources </li></ul></ul>Web 2.0 and IWMW 2006 Tags AJAX Collaboration Tag misuse? Not needed in some areas (e.g. citation analysis, other people interests) So if misspelt still gain benefits.
  14. 14. Microformats (1) <ul><li>Microformats: </li></ul><ul><ul><li>Highlight of WWW 2006 </li></ul></ul><ul><ul><li>Semantic markup on the cheap – builds on existing XHTML pages </li></ul></ul><ul><ul><li>No need for complex software </li></ul></ul><ul><ul><li>See <> </li></ul></ul><ul><li>Using microformats: </li></ul><ul><ul><li>Add some simple semantics using <span>, <div>, etc. classes: </li></ul></ul><ul><ul><ul><li><span class=&quot;fn&quot;>Brian Kelly</span> </li></ul></ul></ul><ul><ul><li>Firefox plugins, harvesters, etc can process the semantic markup e.g. add names to your Outlook contacts, events to your Google calendar, etc </li></ul></ul><ul><ul><li>Bath Univ created thousands of pages with microformats using simple tweak to Perl scripts  </li></ul></ul>Web 2.0 and IWMW 2006 Tags Collaboration
  15. 15. Microformats (2) <ul><li>Pages on IWMW 2006 Web site have microformats </li></ul><ul><li>Plugins such as Tails display contact and event details & allow them to be uploaded to Outlook, Google Calendar, etc </li></ul>Web 2.0 workshops/webmaster-2006/sessions/kelly World Cup Web site also has microformats. This avoids the cumbersome downloading dates, entering calendar, selecting import, finding file, … Tags Collaboration
  16. 16. Web As A Platform <ul><li> has delivered visitors to IWMW 2006 Web site </li></ul><ul><li>They provide </li></ul><ul><ul><li>Event details </li></ul></ul><ul><ul><li>Microformats (event, location) </li></ul></ul>Web 2.0 and IWMW 2006 <ul><ul><li>Exporting functionality </li></ul></ul><ul><ul><li>Community space </li></ul></ul>Other people can take my data and use it to provide my event. They also provide additional functionality for me  Network Users Tags Collaboration
  17. 17. Creative Commons <ul><li>Hasn’t Upcoming contributor infringed my copyright (even though it’s to my benefit?) </li></ul><ul><ul><li>Creative Commons licence assigned to publicity details </li></ul></ul><ul><ul><li>Also described in microformat to allow software to find </li></ul></ul>Web 2.0 and IWMW 2006 workshops/webmaster-2006/publicity/ Openness Tags Collaboration
  18. 18. Wikipedia <ul><li>Summary of IWMW series available in Wikipedia: </li></ul><ul><ul><li>High profile location </li></ul></ul><ul><ul><li>Google friendly </li></ul></ul><ul><ul><li>Maximise impact </li></ul></ul><ul><ul><li>Community can update </li></ul></ul><ul><ul><li>Good guys seem to win (and I’ve now a Wikipedia track record) </li></ul></ul><ul><ul><li>CC rights assigned </li></ul></ul><ul><ul><li>Clean URI </li></ul></ul><ul><ul><li>May provide stable URI </li></ul></ul> Clean, stable URIs? Mashups, integration, annotation, etc. helped by use of clean (e.g. application independent) and stable URIs URIs Wikis Collaboration
  19. 19. Maps <ul><li>Google Map of University of Bath embedded on Web site </li></ul><ul><li>Provides: </li></ul><ul><ul><li>Usability (rescalable and repositioning through use of AJAX) </li></ul></ul><ul><ul><li>Can be personalised (map from my home) </li></ul></ul><ul><ul><li>Effective use of scarce resources (avoids techies duplicating existing services) </li></ul></ul>Web 2.0 and IWMW 2006 workshops/webmaster-2006/maps/ Risk : What if Google go out-of-business? Response : What if local staff leave? What if other development work they should do fails to get done? Note : Northumbria have better example APIs AJAX Mashups Syndication
  20. 20. User Focus <ul><li>Why are we doing this? </li></ul><ul><li>For Our Users: </li></ul><ul><ul><li>Making our users aware of emerging new stuff </li></ul></ul><ul><ul><li>Demonstrating how they can be used </li></ul></ul><ul><ul><li>Describing possible problems and solutions </li></ul></ul><ul><ul><li>To provide richer services </li></ul></ul><ul><li>Engaging With Users </li></ul><ul><ul><li>Getting our users involved in using the applications, listening to their feedback </li></ul></ul><ul><li>Risk If We Don’t </li></ul><ul><ul><li>We’re aware of the risks of not doing this: </li></ul></ul><ul><ul><ul><li>Shouldn’t UKOLN be able to advise us? </li></ul></ul></ul><ul><ul><ul><li>What do we pay them for? </li></ul></ul></ul>Deployment Strategy
  21. 21. It’s Scary <ul><li>Remember Web in early 1990s: </li></ul><ul><ul><li>It’s a toy </li></ul></ul><ul><ul><li>Gopher is the future </li></ul></ul><ul><ul><li>We’ve a home-grown CWIS </li></ul></ul><ul><li>And the word and other wars: </li></ul><ul><ul><li>World Wide Web, worldwideweb, WWW, W 3 </li></ul></ul><ul><ul><li>You can’t use the Web for Intranets – content must be open </li></ul></ul><ul><li>Nothing’s changed (Web 2.0 is scary) </li></ul><ul><ul><li>We’ve just bought a CMS </li></ul></ul><ul><ul><li>Legal issues </li></ul></ul><ul><ul><li>Don’t understand the technologies </li></ul></ul><ul><ul><li>We’re losing control </li></ul></ul><ul><ul><li>… </li></ul></ul>Deployment Strategy Northgate Rapper and their double asymmetric somersault debuted at international DERT 2006 competition Addressing fears: Experimentation, practice, working with enthusiasts & youngsters, getting support of friends & colleagues, having a plan B, alcohol?, … We Sometimes Do Scary Things
  22. 22. IWMW 2006 & Risk Management <ul><li>IWMW 2006 has taken a risk management approach to its evaluation of Web 2.0 technologies: </li></ul><ul><ul><li>Agreements : e.g. in the case of the Chatbot. </li></ul></ul><ul><ul><li>Use of well-established services : Google & are well-established and have financial security. </li></ul></ul><ul><ul><li>Notification : warnings that services could be lost. </li></ul></ul><ul><ul><li>Engagement : with the user community: users actively engage in the evaluation of the services. </li></ul></ul><ul><ul><li>Provision of alternative services: multiple OMPL tools. </li></ul></ul><ul><ul><li>Use in non-mission critical areas: not for bookings! </li></ul></ul><ul><ul><li>Long term experiences of services: usage stats </li></ul></ul><ul><ul><li>Availability of alternative sources of data : e.g. standard Web server log files. </li></ul></ul><ul><ul><li>Data export and aggregation: RSS feeds, aggregated in Suprglu, OPML viewers, etc. </li></ul></ul>Deployment Strategy
  23. 23. Risks (2) <ul><li>File Formats </li></ul><ul><ul><li>Microformats are a bottom-up approach </li></ul></ul><ul><ul><li>OPML is simple but ambiguous </li></ul></ul><ul><ul><li>How scalable? </li></ul></ul><ul><ul><li>Will formats change in light of experience? </li></ul></ul><ul><li>Approaches: </li></ul><ul><ul><li>Use to provide services today </li></ul></ul><ul><ul><li>Look for tools which will allow for changes </li></ul></ul><ul><li>Applications </li></ul><ul><ul><li>No longer critical in many areas! </li></ul></ul><ul><ul><li>If application is flawed, no longer available through it away and use an alterative </li></ul></ul>Deployment Strategy
  24. 24. Web 2.0 With Responsibility <ul><li>Web 2.0 software and services: </li></ul><ul><ul><li>Will be poor, over-hyped, inaccessible, … </li></ul></ul><ul><li>Web 1.0 software an Web sites was the same </li></ul><ul><li>Still need to: </li></ul><ul><ul><li>Make use of standards & best practices </li></ul></ul><ul><ul><li>Address usability & accessibility issues </li></ul></ul><ul><ul><li>Have migration plans (e.g. create microformats with scripts, use for events in near future, …) </li></ul></ul>Deployment Strategy AJAX And Accessibility Argument : AJAX use JavaScript and WAI guidelines implies JavaScript is bad. Counter-Argument : But WCAG 2.0 removes this, and JavaScript can provide accessibility & usability benefits. Advice : Right decent JavaScript and test it! (or provide alternatives).
  25. 25. Conclusions <ul><li>To conclude: </li></ul><ul><ul><li>Web 2.0 is here and ready for use </li></ul></ul><ul><ul><li>It can provide valuable user services </li></ul></ul><ul><ul><li>It’s particularly appropriate for use in education & research, which seeks to make use of innovation </li></ul></ul><ul><ul><li>There will be poor applications, mistakes, etc. </li></ul></ul><ul><ul><li>Planning, flexibility & sharing can help </li></ul></ul>Conclusions Note resources cited in the talk are bookmarked in using tag '' iwmw2006-web2.0-panel &quot;