<?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: Celebrity iLounge &#8211; the First Apple Lounge at Sea</title>
	<atom:link href="http://www.seasiteblog.com/2010/02/celebrity-ilounge-the-first-apple-lounge-at-sea/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.seasiteblog.com/2010/02/celebrity-ilounge-the-first-apple-lounge-at-sea/</link>
	<description>SeaSite blog is a community forum for corporate and group planners and cruise line partners to share stories, tips and experiences about managing events at sea</description>
	<lastBuildDate>Wed, 01 Feb 2012 22:08:01 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Celebrity Cruises video -technology keeps guests connected at sea &#124; SeaSite Blog &#38; Cruise Events Forum</title>
		<link>http://www.seasiteblog.com/2010/02/celebrity-ilounge-the-first-apple-lounge-at-sea/comment-page-1/#comment-127530</link>
		<dc:creator>Celebrity Cruises video -technology keeps guests connected at sea &#124; SeaSite Blog &#38; Cruise Events Forum</dc:creator>
		<pubDate>Tue, 27 Dec 2011 17:01:54 +0000</pubDate>
		<guid isPermaLink="false">http://www.seasiteblog.com/?p=920#comment-127530</guid>
		<description>[...] and integrated guest technology onboard each ship in the fleet. Whether surfing the web in the Celebrity iLounge, checking emails while relaxing by the pool, exploring fine art on an iPad tour, or scrolling [...]</description>
		<content:encoded><![CDATA[<p>[...] and integrated guest technology onboard each ship in the fleet. Whether surfing the web in the Celebrity iLounge, checking emails while relaxing by the pool, exploring fine art on an iPad tour, or scrolling [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>

