<?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: Fluid Engage</title>
	<atom:link href="http://wiki.museummobile.info/museums-to-go/products-services/fluid-engage/feed" rel="self" type="application/rss+xml" />
	<link>http://wiki.museummobile.info</link>
	<description>Media and Technology on the Go</description>
	<lastBuildDate>Mon, 23 Jan 2012 19:39:10 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
	<item>
		<title>By: MuseumMobile Wiki &#187; Opensource Mobile Solutions: Omeka &#38; Fluid</title>
		<link>http://wiki.museummobile.info/museums-to-go/products-services/fluid-engage/comment-page-1#comment-843</link>
		<dc:creator>MuseumMobile Wiki &#187; Opensource Mobile Solutions: Omeka &#38; Fluid</dc:creator>
		<pubDate>Mon, 07 Sep 2009 16:00:41 +0000</pubDate>
		<guid isPermaLink="false">http://wiki.museummobile.info/?page_id=289#comment-843</guid>
		<description>[...] up of what the difference is between the two leading opensource solutions currently in development, Fluid Engage and Omeka, so I thought I&#8217;d tweet it to those most involved in both projects for their [...]</description>
		<content:encoded><![CDATA[<p>[...] up of what the difference is between the two leading opensource solutions currently in development, Fluid Engage and Omeka, so I thought I&#8217;d tweet it to those most involved in both projects for their [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: MuseumMobile Wiki &#187; Fresh From Twitter today</title>
		<link>http://wiki.museummobile.info/museums-to-go/products-services/fluid-engage/comment-page-1#comment-79</link>
		<dc:creator>MuseumMobile Wiki &#187; Fresh From Twitter today</dc:creator>
		<pubDate>Tue, 23 Jun 2009 13:29:41 +0000</pubDate>
		<guid isPermaLink="false">http://wiki.museummobile.info/?page_id=289#comment-79</guid>
		<description>[...] for the Fluid Engage project from @rjstein of IMA at http://is.gd/17O37 &#8211; Answers on Mon 22 June! #fluid #mtogo RT @NancyProctor: Fluid Engage: open source project [...]</description>
		<content:encoded><![CDATA[<p>[...] for the Fluid Engage project from @rjstein of IMA at <a href="http://is.gd/17O37" rel="nofollow">http://is.gd/17O37</a> &#8211; Answers on Mon 22 June! #fluid #mtogo RT @NancyProctor: Fluid Engage: open source project [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Nancy Proctor</title>
		<link>http://wiki.museummobile.info/museums-to-go/products-services/fluid-engage/comment-page-1#comment-77</link>
		<dc:creator>Nancy Proctor</dc:creator>
		<pubDate>Sun, 21 Jun 2009 02:10:44 +0000</pubDate>
		<guid isPermaLink="false">http://wiki.museummobile.info/?page_id=289#comment-77</guid>
		<description>To the Fluid Engage group from Rob Stein, Indianapolis Museum of Art, on 19 June 2009:
 
We&#039;ve pretty much got a working Drupal based content management system which can author a TourML document and bundle the associated media files...  we can then drag and drop this into iTunes and our TAP iPhone app will consume the TourML document and build a tour based on that content and the media files contained in the zip...  Daniel [Incandela] and our new media team are in the process of editing video shot in Spain during the Easter processions for the tour content to be launched in the Fall.  As we get a few more content stops... we&#039;ll be happy to give you an early install of the app so you can check it out if you like.
 
 
The iPhone support for consistent user interface features between apps has been really powerful in developing the TAP application in a way which is consistent with the user experience us iPhone users have come to expect.  1 really key contribution which is currently lacking on other mobile devices is this common set of functionality that can also be robust and solid between applications and devices... perhaps Fluid Engage can come up with an application platform which would be similar to the app platform on iPhones which would bundle the user interface features they have developed?

[See also the Indianapolis Museum of Art Project page, their TourML page, and thoughts and a very nice diagram in in the Software Architecture Proposal!]</description>
		<content:encoded><![CDATA[<p>To the Fluid Engage group from Rob Stein, Indianapolis Museum of Art, on 19 June 2009:</p>
<p>We&#8217;ve pretty much got a working Drupal based content management system which can author a TourML document and bundle the associated media files&#8230;  we can then drag and drop this into iTunes and our TAP iPhone app will consume the TourML document and build a tour based on that content and the media files contained in the zip&#8230;  Daniel [Incandela] and our new media team are in the process of editing video shot in Spain during the Easter processions for the tour content to be launched in the Fall.  As we get a few more content stops&#8230; we&#8217;ll be happy to give you an early install of the app so you can check it out if you like.</p>
<p>The iPhone support for consistent user interface features between apps has been really powerful in developing the TAP application in a way which is consistent with the user experience us iPhone users have come to expect.  1 really key contribution which is currently lacking on other mobile devices is this common set of functionality that can also be robust and solid between applications and devices&#8230; perhaps Fluid Engage can come up with an application platform which would be similar to the app platform on iPhones which would bundle the user interface features they have developed?</p>
<p>[See also the Indianapolis Museum of Art Project page, their TourML page, and thoughts and a very nice diagram in in the Software Architecture Proposal!]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: MuseumMobile Wiki &#187; Fresh From Twitter today</title>
		<link>http://wiki.museummobile.info/museums-to-go/products-services/fluid-engage/comment-page-1#comment-76</link>
		<dc:creator>MuseumMobile Wiki &#187; Fresh From Twitter today</dc:creator>
		<pubDate>Sat, 20 Jun 2009 20:18:12 +0000</pubDate>
		<guid isPermaLink="false">http://wiki.museummobile.info/?page_id=289#comment-76</guid>
		<description>[...] Fluid Engage [...]</description>
		<content:encoded><![CDATA[<p>[...] Fluid Engage [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>

