<?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: Mobile media for cultural and historical heritage, guidelines and pilot projects</title>
	<atom:link href="http://themuseumofthefuture.com/2010/05/02/mobile-media-for-cultural-and-historical-heritage-guidelines-and-pilot-projects/feed/" rel="self" type="application/rss+xml" />
	<link>http://themuseumofthefuture.com/2010/05/02/mobile-media-for-cultural-and-historical-heritage-guidelines-and-pilot-projects/</link>
	<description>Thoughts, examples and best-practices for innovation in museums and the cultural sector.</description>
	<lastBuildDate>Fri, 27 Apr 2012 09:19:00 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.2</generator>
	<item>
		<title>By: Museum Android App Gap &#8211; More thoughts and a response</title>
		<link>http://themuseumofthefuture.com/2010/05/02/mobile-media-for-cultural-and-historical-heritage-guidelines-and-pilot-projects/#comment-539</link>
		<dc:creator>Museum Android App Gap &#8211; More thoughts and a response</dc:creator>
		<pubDate>Mon, 28 Mar 2011 11:05:27 +0000</pubDate>
		<guid isPermaLink="false">http://themuseumofthefuture.com/?p=125#comment-539</guid>
		<description>[...] where services are tailored to all available options.  Blog posts such as Jasper Visser&#8217;s Guidelines for Mobile and Heritage provide outline for this concept.  One where the product trumps the technology and where the [...]</description>
		<content:encoded><![CDATA[<p>[...] where services are tailored to all available options.  Blog posts such as Jasper Visser&#8217;s Guidelines for Mobile and Heritage provide outline for this concept.  One where the product trumps the technology and where the [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Steven Kamminga (MF)</title>
		<link>http://themuseumofthefuture.com/2010/05/02/mobile-media-for-cultural-and-historical-heritage-guidelines-and-pilot-projects/#comment-280</link>
		<dc:creator>Steven Kamminga (MF)</dc:creator>
		<pubDate>Tue, 17 Aug 2010 11:20:00 +0000</pubDate>
		<guid isPermaLink="false">http://themuseumofthefuture.com/?p=125#comment-280</guid>
		<description>Looking over my previous comment, I realise my first sentence makes no sense at all. &quot;specific sites&quot; should be replaced with &quot;specific subjects or museums&quot;.</description>
		<content:encoded><![CDATA[<p>Looking over my previous comment, I realise my first sentence makes no sense at all. &#8220;specific sites&#8221; should be replaced with &#8220;specific subjects or museums&#8221;.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Vincent Roman</title>
		<link>http://themuseumofthefuture.com/2010/05/02/mobile-media-for-cultural-and-historical-heritage-guidelines-and-pilot-projects/#comment-188</link>
		<dc:creator>Vincent Roman</dc:creator>
		<pubDate>Wed, 21 Jul 2010 02:15:56 +0000</pubDate>
		<guid isPermaLink="false">http://themuseumofthefuture.com/?p=125#comment-188</guid>
		<description>Thanks Jasper ... Some sound points, and definitely interested in finding out more about how you intend to implement such features in any contextual &#039;apps&#039; for mobile.  So much going on in that respect and it&#039;s an interesting &#039;space&#039; to watch.</description>
		<content:encoded><![CDATA[<p>Thanks Jasper &#8230; Some sound points, and definitely interested in finding out more about how you intend to implement such features in any contextual &#8216;apps&#8217; for mobile.  So much going on in that respect and it&#8217;s an interesting &#8216;space&#8217; to watch.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jasper Visser</title>
		<link>http://themuseumofthefuture.com/2010/05/02/mobile-media-for-cultural-and-historical-heritage-guidelines-and-pilot-projects/#comment-115</link>
		<dc:creator>Jasper Visser</dc:creator>
		<pubDate>Tue, 18 May 2010 16:08:05 +0000</pubDate>
		<guid isPermaLink="false">http://themuseumofthefuture.com/?p=125#comment-115</guid>
		<description>@ Steven, I couldn&#039;t agree more, see point 3 and 5. A mobile website is so much more useful than yet another app. Before we all go out to develop apps, we&#039;ll have to make our website accessible from mobile devices and use the specifics of mobile on the mobile version of our websites.

However, I do believe in museum specific apps. I think we will see apps turn into intelligent bookmarks. A (bad) example might be the 9292ov app that does little more than get your current location and redirect you to their website. Good examples will follow. At least, I hope so!</description>
		<content:encoded><![CDATA[<p>@ Steven, I couldn&#8217;t agree more, see point 3 and 5. A mobile website is so much more useful than yet another app. Before we all go out to develop apps, we&#8217;ll have to make our website accessible from mobile devices and use the specifics of mobile on the mobile version of our websites.</p>
<p>However, I do believe in museum specific apps. I think we will see apps turn into intelligent bookmarks. A (bad) example might be the 9292ov app that does little more than get your current location and redirect you to their website. Good examples will follow. At least, I hope so!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Steven Kamminga (MF)</title>
		<link>http://themuseumofthefuture.com/2010/05/02/mobile-media-for-cultural-and-historical-heritage-guidelines-and-pilot-projects/#comment-114</link>
		<dc:creator>Steven Kamminga (MF)</dc:creator>
		<pubDate>Tue, 18 May 2010 14:01:06 +0000</pubDate>
		<guid isPermaLink="false">http://themuseumofthefuture.com/?p=125#comment-114</guid>
		<description>Looking over my previous comment, I realise my first sentence makes no sense at all. &quot;specific sites&quot; should be replaced with &quot;specific subjects or museums&quot;.</description>
		<content:encoded><![CDATA[<p>Looking over my previous comment, I realise my first sentence makes no sense at all. &#8220;specific sites&#8221; should be replaced with &#8220;specific subjects or museums&#8221;.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Steven Kamminga (MF)</title>
		<link>http://themuseumofthefuture.com/2010/05/02/mobile-media-for-cultural-and-historical-heritage-guidelines-and-pilot-projects/#comment-113</link>
		<dc:creator>Steven Kamminga (MF)</dc:creator>
		<pubDate>Tue, 18 May 2010 13:59:42 +0000</pubDate>
		<guid isPermaLink="false">http://themuseumofthefuture.com/?p=125#comment-113</guid>
		<description>Though I agree with most of your remarks, and being a strong believer in the potential of adding value to cultural heritage through mobile media, I do wonder about the point you make about creating apps for specific sites. Roeland Stekelenburg, boss of NOS new media division recently complained about having to develop numerous different apps for the growing number of phones and their operating systems - iPhone, Android (different versions), Symbian, Blackberry etc. So I&#039;d suggest the best and cheapest way for cultural organisations is to invest in a proper mobile site rather than several mobile OS-apps.</description>
		<content:encoded><![CDATA[<p>Though I agree with most of your remarks, and being a strong believer in the potential of adding value to cultural heritage through mobile media, I do wonder about the point you make about creating apps for specific sites. Roeland Stekelenburg, boss of NOS new media division recently complained about having to develop numerous different apps for the growing number of phones and their operating systems &#8211; iPhone, Android (different versions), Symbian, Blackberry etc. So I&#8217;d suggest the best and cheapest way for cultural organisations is to invest in a proper mobile site rather than several mobile OS-apps.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Steven Kamminga (MF)</title>
		<link>http://themuseumofthefuture.com/2010/05/02/mobile-media-for-cultural-and-historical-heritage-guidelines-and-pilot-projects/#comment-279</link>
		<dc:creator>Steven Kamminga (MF)</dc:creator>
		<pubDate>Tue, 18 May 2010 13:59:00 +0000</pubDate>
		<guid isPermaLink="false">http://themuseumofthefuture.com/?p=125#comment-279</guid>
		<description>Though I agree with most of your remarks, and being a strong believer in the potential of adding value to cultural heritage through mobile media, I do wonder about the point you make about creating apps for specific sites. Roeland Stekelenburg, boss of NOS new media division recently complained about having to develop numerous different apps for the growing number of phones and their operating systems - iPhone, Android (different versions), Symbian, Blackberry etc. So I&#039;d suggest the best and cheapest way for cultural organisations is to invest in a proper mobile site rather than several mobile OS-apps.</description>
		<content:encoded><![CDATA[<p>Though I agree with most of your remarks, and being a strong believer in the potential of adding value to cultural heritage through mobile media, I do wonder about the point you make about creating apps for specific sites. Roeland Stekelenburg, boss of NOS new media division recently complained about having to develop numerous different apps for the growing number of phones and their operating systems &#8211; iPhone, Android (different versions), Symbian, Blackberry etc. So I&#8217;d suggest the best and cheapest way for cultural organisations is to invest in a proper mobile site rather than several mobile OS-apps.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: nosuic</title>
		<link>http://themuseumofthefuture.com/2010/05/02/mobile-media-for-cultural-and-historical-heritage-guidelines-and-pilot-projects/#comment-79</link>
		<dc:creator>nosuic</dc:creator>
		<pubDate>Sun, 02 May 2010 20:10:33 +0000</pubDate>
		<guid isPermaLink="false">http://themuseumofthefuture.com/?p=125#comment-79</guid>
		<description>RT @jaspervisser: Guidelines and pilots for mobile &amp; heritage, from our Wednesday expert meeting - http://themuseumofthefuture.com/2010/05/...</description>
		<content:encoded><![CDATA[<p>RT @jaspervisser: Guidelines and pilots for mobile &#038; heritage, from our Wednesday expert meeting &#8211; <a href="http://themuseumofthefuture.com/2010/05/" rel="nofollow">http://themuseumofthefuture.com/2010/05/</a>&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: nosuic</title>
		<link>http://themuseumofthefuture.com/2010/05/02/mobile-media-for-cultural-and-historical-heritage-guidelines-and-pilot-projects/#comment-278</link>
		<dc:creator>nosuic</dc:creator>
		<pubDate>Sun, 02 May 2010 20:10:00 +0000</pubDate>
		<guid isPermaLink="false">http://themuseumofthefuture.com/?p=125#comment-278</guid>
		<description>RT @jaspervisser: Guidelines and pilots for mobile &amp; heritage, from our Wednesday expert meeting - http://themuseumofthefuture.com/2010/05/...</description>
		<content:encoded><![CDATA[<p>RT @jaspervisser: Guidelines and pilots for mobile &amp; heritage, from our Wednesday expert meeting &#8211; <a href="http://themuseumofthefuture.com/2010/05/" rel="nofollow">http://themuseumofthefuture.com/2010/05/</a>&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: jaspervisser</title>
		<link>http://themuseumofthefuture.com/2010/05/02/mobile-media-for-cultural-and-historical-heritage-guidelines-and-pilot-projects/#comment-78</link>
		<dc:creator>jaspervisser</dc:creator>
		<pubDate>Sun, 02 May 2010 19:41:15 +0000</pubDate>
		<guid isPermaLink="false">http://themuseumofthefuture.com/?p=125#comment-78</guid>
		<description>Guidelines and pilots for mobile &amp; heritage, from our Wednesday expert meeting - http://themuseumofthefuture.com/2010/05/...</description>
		<content:encoded><![CDATA[<p>Guidelines and pilots for mobile &amp; heritage, from our Wednesday expert meeting &#8211; <a href="http://themuseumofthefuture.com/2010/05/" rel="nofollow">http://themuseumofthefuture.com/2010/05/</a>&#8230;</p>
]]></content:encoded>
	</item>
</channel>
</rss>

