<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Web 2.0 and Archival Institutions</title>
	<atom:link href="http://archivemati.ca/2006/05/08/web-20-and-archival-institutions/feed/" rel="self" type="application/rss+xml" />
	<link>http://archivemati.ca/2006/05/08/web-20-and-archival-institutions/</link>
	<description>digital archives consulting and research</description>
	<lastBuildDate>Sun, 18 Jan 2009 06:37:31 -0600</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Stevie K</title>
		<link>http://archivemati.ca/2006/05/08/web-20-and-archival-institutions/comment-page-1/#comment-80</link>
		<dc:creator>Stevie K</dc:creator>
		<pubDate>Sun, 09 Jul 2006 07:34:53 +0000</pubDate>
		<guid isPermaLink="false">http://archivemati.ca/?p=41#comment-80</guid>
		<description>But IE 7.0 is on the horizon.  Beware!</description>
		<content:encoded><![CDATA[<p>But IE 7.0 is on the horizon.  Beware!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Peter Van Garderen</title>
		<link>http://archivemati.ca/2006/05/08/web-20-and-archival-institutions/comment-page-1/#comment-79</link>
		<dc:creator>Peter Van Garderen</dc:creator>
		<pubDate>Sat, 08 Jul 2006 12:55:28 +0000</pubDate>
		<guid isPermaLink="false">http://archivemati.ca/?p=41#comment-79</guid>
		<description>Good points Steve. For those reasons I think any web application that employs AJAX should have a non-AJAX alternative for each of its interfaces. Or you can simply force them to use only Internet Explorer 6.0 - with a specific options configuration, like some applications we know :-)</description>
		<content:encoded><![CDATA[<p>Good points Steve. For those reasons I think any web application that employs AJAX should have a non-AJAX alternative for each of its interfaces. Or you can simply force them to use only Internet Explorer 6.0 &#8211; with a specific options configuration, like some applications we know <img src='http://archivemati.ca/wp-includes/images/smilies/icon_smile.gif' alt=':-)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Steve Kwan</title>
		<link>http://archivemati.ca/2006/05/08/web-20-and-archival-institutions/comment-page-1/#comment-78</link>
		<dc:creator>Steve Kwan</dc:creator>
		<pubDate>Fri, 07 Jul 2006 18:32:22 +0000</pubDate>
		<guid isPermaLink="false">http://archivemati.ca/?p=41#comment-78</guid>
		<description>Something to think about:  Sometimes technologies such as Ajax can actually impair usability, not improve.

By providing &quot;thick client&quot; functionality to websites, Ajax can make them behave drastically different than people might expect.  After all, if people expect something to behave like a website and it behaves like Microsoft Word, you might have problems.

Also, Ajax is completely dependent upon JavaScript.  If the user doesn&#039;t have JavaScript enabled, or is using a browser that quirks up with your particular JavaScript, then they may be prevented from using your website.  This would actually decrease usability.

Ajax can break standard Web conventions.  It typically breaks the browser&#039;s Back button.  This can be worked around, but in its immature stages this problem is still very common in Ajax websites.

It&#039;s also worth keeping in mind that a large portion of your users may have some sort of impairment.  This could be particularly common in archives, where the average age of your users could be 50-60.  Take a blind user, for example.  Blind users use speech readers to surf the Internet, and if most of your content is dynamically loaded via Ajax, this content may unaccessible to these users.  Features such as drag-and-drop will be completely unusable to them.

Ajax is a promising methodology, but sticking to good old Web standards like XHTML and CSS is often preferable.</description>
		<content:encoded><![CDATA[<p>Something to think about:  Sometimes technologies such as Ajax can actually impair usability, not improve.</p>
<p>By providing &#8220;thick client&#8221; functionality to websites, Ajax can make them behave drastically different than people might expect.  After all, if people expect something to behave like a website and it behaves like Microsoft Word, you might have problems.</p>
<p>Also, Ajax is completely dependent upon JavaScript.  If the user doesn&#8217;t have JavaScript enabled, or is using a browser that quirks up with your particular JavaScript, then they may be prevented from using your website.  This would actually decrease usability.</p>
<p>Ajax can break standard Web conventions.  It typically breaks the browser&#8217;s Back button.  This can be worked around, but in its immature stages this problem is still very common in Ajax websites.</p>
<p>It&#8217;s also worth keeping in mind that a large portion of your users may have some sort of impairment.  This could be particularly common in archives, where the average age of your users could be 50-60.  Take a blind user, for example.  Blind users use speech readers to surf the Internet, and if most of your content is dynamically loaded via Ajax, this content may unaccessible to these users.  Features such as drag-and-drop will be completely unusable to them.</p>
<p>Ajax is a promising methodology, but sticking to good old Web standards like XHTML and CSS is often preferable.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Peter Van Garderen</title>
		<link>http://archivemati.ca/2006/05/08/web-20-and-archival-institutions/comment-page-1/#comment-77</link>
		<dc:creator>Peter Van Garderen</dc:creator>
		<pubDate>Mon, 15 May 2006 18:56:32 +0000</pubDate>
		<guid isPermaLink="false">http://archivemati.ca/?p=41#comment-77</guid>
		<description>Thanks Jason,

I hadn&#039;t checked out the Pepys diary website for a couple of years. They have since managed to build a Web 2.0-style community around this archival resource using RSS webfeeds, annotations (blog comments) and related discussion forums.

I&#039;ve added it to my list of examples above. Thanks for pointing it out. Very interesting.

Thanks also for posting the &lt;a href=&quot;http://neoarch.wordpress.com/2006/03/10/library-20-a-patrons-summary/&quot;&gt;Library 2.0 summary&lt;/a&gt; on your own blog. This article provides more insight into the noteworthy aspects of Web 2.0 and, in this case, how that applies to Library services.</description>
		<content:encoded><![CDATA[<p>Thanks Jason,</p>
<p>I hadn&#8217;t checked out the Pepys diary website for a couple of years. They have since managed to build a Web 2.0-style community around this archival resource using RSS webfeeds, annotations (blog comments) and related discussion forums.</p>
<p>I&#8217;ve added it to my list of examples above. Thanks for pointing it out. Very interesting.</p>
<p>Thanks also for posting the <a href="http://neoarch.wordpress.com/2006/03/10/library-20-a-patrons-summary/">Library 2.0 summary</a> on your own blog. This article provides more insight into the noteworthy aspects of Web 2.0 and, in this case, how that applies to Library services.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jason</title>
		<link>http://archivemati.ca/2006/05/08/web-20-and-archival-institutions/comment-page-1/#comment-76</link>
		<dc:creator>Jason</dc:creator>
		<pubDate>Mon, 15 May 2006 17:07:42 +0000</pubDate>
		<guid isPermaLink="false">http://archivemati.ca/?p=41#comment-76</guid>
		<description>&lt;blockquote&gt;I therefore see the introduction of community-managed collections, descriptions, exhibits and discussions as something that happens in parallel to the authoritative archives access systems that are managed by archival institutions and their professional staff. I see these parallel systems as taking the form of virtual collections or virtual research rooms that are loosely-coupled to the institutional systems using open architectures and standards.&lt;/blockquote&gt;
I have often thought that the &lt;a href=&quot;http://www.pepysdiary.com/&quot; rel=&quot;nofollow&quot;&gt;online Pepys diary&lt;/a&gt; represents a picture of the type of colaboration that would be beneficial to archivists. How many enlightening annotations could other archivists and patrons provide to our digital collections and finding aids, if we would only give them a format for doing so.

Thanks for writing on this topic!</description>
		<content:encoded><![CDATA[<blockquote><p>I therefore see the introduction of community-managed collections, descriptions, exhibits and discussions as something that happens in parallel to the authoritative archives access systems that are managed by archival institutions and their professional staff. I see these parallel systems as taking the form of virtual collections or virtual research rooms that are loosely-coupled to the institutional systems using open architectures and standards.</p></blockquote>
<p>I have often thought that the <a href="http://www.pepysdiary.com/" rel="nofollow">online Pepys diary</a> represents a picture of the type of colaboration that would be beneficial to archivists. How many enlightening annotations could other archivists and patrons provide to our digital collections and finding aids, if we would only give them a format for doing so.</p>
<p>Thanks for writing on this topic!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Klaus Graf</title>
		<link>http://archivemati.ca/2006/05/08/web-20-and-archival-institutions/comment-page-1/#comment-75</link>
		<dc:creator>Klaus Graf</dc:creator>
		<pubDate>Tue, 09 May 2006 16:40:57 +0000</pubDate>
		<guid isPermaLink="false">http://archivemati.ca/?p=41#comment-75</guid>
		<description>See
http://archiv.twoday.net/stories/1939655/
and the category &quot;Open Access&quot; of ARCHIVALIA (in German)</description>
		<content:encoded><![CDATA[<p>See<br />
<a href="http://archiv.twoday.net/stories/1939655/" rel="nofollow">http://archiv.twoday.net/stories/1939655/</a><br />
and the category &#8220;Open Access&#8221; of ARCHIVALIA (in German)</p>
]]></content:encoded>
	</item>
</channel>
</rss>
