<?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: Worklight Enters the Enterprise Facebook Market</title>
	<atom:link href="http://www.fastforwardblog.com/2007/12/20/worklight-enters-the-enterprise-facebook-market/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.fastforwardblog.com/2007/12/20/worklight-enters-the-enterprise-facebook-market/</link>
	<description></description>
	<pubDate>Wed, 07 Jan 2009 00:05:59 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.7</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Tina</title>
		<link>http://www.fastforwardblog.com/2007/12/20/worklight-enters-the-enterprise-facebook-market/comment-page-1/#comment-151564</link>
		<dc:creator>Tina</dc:creator>
		<pubDate>Tue, 01 Apr 2008 16:32:58 +0000</pubDate>
		<guid isPermaLink="false">http://www.fastforwardblog.com/2007/12/20/worklight-enters-the-enterprise-facebook-market/#comment-151564</guid>
		<description>i saw more info on this blog www.ntechmania.blogspot.com very useful information good for someone who is intrested in this subject</description>
		<content:encoded><![CDATA[<p>i saw more info on this blog <a href="http://www.ntechmania.blogspot.com" rel="nofollow">http://www.ntechmania.blogspot.com</a> very useful information good for someone who is intrested in this subject</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: David Lavenda</title>
		<link>http://www.fastforwardblog.com/2007/12/20/worklight-enters-the-enterprise-facebook-market/comment-page-1/#comment-134185</link>
		<dc:creator>David Lavenda</dc:creator>
		<pubDate>Fri, 04 Jan 2008 12:51:36 +0000</pubDate>
		<guid isPermaLink="false">http://www.fastforwardblog.com/2007/12/20/worklight-enters-the-enterprise-facebook-market/#comment-134185</guid>
		<description>Alan,
Your observation about WorkBook/WorkLight is correct - WorkBook and Facebook are only part of the bigger picture. WorkLight however, is not an "RSS vendor" per se; RSS is only one of many Web 2.0 technologies that we enable within a secure enterprise environment.  WorkLight, in fact, allows employees to collaborate with peers and access application data via many Web 2.0 tools like RSS, personalized home pages, widgets and gadgets, social networks, social bookmarking and others. 

In this sense, WorkLight is an Enterprise 2.0 "platform" or "operating system." Today, we support many enterprise applications and Web 2.0 tools and services. If tomorrow, another application is needed or if another web 2.0 service becomes popular, we do not have to re-architect the product, we merely add another interface through which information can be extracted or can be displayed through. All the essential elements of the Enterprise 2.0 platform, such as the capability to extract/display information across multiple systems, being able to tap into native security systems to authenticate and apply access control to data, to ensure that data is secured end-to-end, and to provide web 2.0 self-service capabilities to employees, are all basic parts of the WorkLight platform. RSS is just one aspect of the big picture.</description>
		<content:encoded><![CDATA[<p>Alan,<br />
Your observation about WorkBook/WorkLight is correct - WorkBook and Facebook are only part of the bigger picture. WorkLight however, is not an &#8220;RSS vendor&#8221; per se; RSS is only one of many Web 2.0 technologies that we enable within a secure enterprise environment.  WorkLight, in fact, allows employees to collaborate with peers and access application data via many Web 2.0 tools like RSS, personalized home pages, widgets and gadgets, social networks, social bookmarking and others. </p>
<p>In this sense, WorkLight is an Enterprise 2.0 &#8220;platform&#8221; or &#8220;operating system.&#8221; Today, we support many enterprise applications and Web 2.0 tools and services. If tomorrow, another application is needed or if another web 2.0 service becomes popular, we do not have to re-architect the product, we merely add another interface through which information can be extracted or can be displayed through. All the essential elements of the Enterprise 2.0 platform, such as the capability to extract/display information across multiple systems, being able to tap into native security systems to authenticate and apply access control to data, to ensure that data is secured end-to-end, and to provide web 2.0 self-service capabilities to employees, are all basic parts of the WorkLight platform. RSS is just one aspect of the big picture.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Alan Morrison</title>
		<link>http://www.fastforwardblog.com/2007/12/20/worklight-enters-the-enterprise-facebook-market/comment-page-1/#comment-133946</link>
		<dc:creator>Alan Morrison</dc:creator>
		<pubDate>Thu, 03 Jan 2008 22:40:29 +0000</pubDate>
		<guid isPermaLink="false">http://www.fastforwardblog.com/2007/12/20/worklight-enters-the-enterprise-facebook-market/#comment-133946</guid>
		<description>Appreciate your sharing thoughts on this topic. I've just seen a demo of the WorkLight software, and Facebook is only a part of the picture. Securing and feeding widgets in iGoogle pages (and even enabling SAP transactions in them) is another capability they cite. 

I'd classify them as an enterprise RSS vendor with some novel security approaches to platforms and portals that have open APIs. The bigger picture is not the Facebook interface, it's all the systems WorkLight taps into and makes more accessible, via whatever front end.</description>
		<content:encoded><![CDATA[<p>Appreciate your sharing thoughts on this topic. I&#8217;ve just seen a demo of the WorkLight software, and Facebook is only a part of the picture. Securing and feeding widgets in iGoogle pages (and even enabling SAP transactions in them) is another capability they cite. </p>
<p>I&#8217;d classify them as an enterprise RSS vendor with some novel security approaches to platforms and portals that have open APIs. The bigger picture is not the Facebook interface, it&#8217;s all the systems WorkLight taps into and makes more accessible, via whatever front end.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Bill Ives</title>
		<link>http://www.fastforwardblog.com/2007/12/20/worklight-enters-the-enterprise-facebook-market/comment-page-1/#comment-130749</link>
		<dc:creator>Bill Ives</dc:creator>
		<pubDate>Wed, 26 Dec 2007 18:31:53 +0000</pubDate>
		<guid isPermaLink="false">http://www.fastforwardblog.com/2007/12/20/worklight-enters-the-enterprise-facebook-market/#comment-130749</guid>
		<description>David - Thanks for the clear explanation of Workbook. As I said in my post, I think that Workbook can serve a useful function both in terms of actual functionality but also overcoming concerns in the adoption process. My comments on the cover charge were, in part, in fun. Clearly you deserve the fee if you provide the value described. I was also wondering about the Facebook model in general. I know that they open up their application for third party tools at no cost to the third party. This was a smart move on their part for the reasons you stated.  I had just not seen an third party that charged a fee before (again they were generally not business services like yours which deserves a fee), perhaps I had just missed this, and others do as well.   Bill</description>
		<content:encoded><![CDATA[<p>David - Thanks for the clear explanation of Workbook. As I said in my post, I think that Workbook can serve a useful function both in terms of actual functionality but also overcoming concerns in the adoption process. My comments on the cover charge were, in part, in fun. Clearly you deserve the fee if you provide the value described. I was also wondering about the Facebook model in general. I know that they open up their application for third party tools at no cost to the third party. This was a smart move on their part for the reasons you stated.  I had just not seen an third party that charged a fee before (again they were generally not business services like yours which deserves a fee), perhaps I had just missed this, and others do as well.   Bill</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: David Lavenda</title>
		<link>http://www.fastforwardblog.com/2007/12/20/worklight-enters-the-enterprise-facebook-market/comment-page-1/#comment-129945</link>
		<dc:creator>David Lavenda</dc:creator>
		<pubDate>Mon, 24 Dec 2007 14:43:17 +0000</pubDate>
		<guid isPermaLink="false">http://www.fastforwardblog.com/2007/12/20/worklight-enters-the-enterprise-facebook-market/#comment-129945</guid>
		<description>Bill,

WorkBook is a security overlay for Facebook. The way it works is an employee to a company logs into his public Facebook account and then installs the WorkBook application, just like they would install Funwall or SuperPoke. Once the application is installed, they are authenticated by their enterprise authentication engine, which provides them with the appropriate access to enterprise data based upon their corporate roles. This information is served from the WorkBook server (which is installed behind the firewall) and viewed on a Facebook canvas (technically an iFrame).

What the customers are paying for is not for any Facebook functionality, but rather for an on-premise server that is able to securely serve protected enterprise data through Web 2.0 tools, like Facebook. Facebook, in this case, is the front-end tool through which information is delivered, much like iGoogle, MS Live, Netvibes, and other home page servers can be used to display application data via gadgets, widgets, or RSS (which is the original WorkLight functionality).

“Enterprise data” in the WorkBook context includes things like “Q&#38;A,” search for expertise, news sharing, contact information sharing, even application data, – basically all the social networking functions one would expect. However, Facebook provides none of this functionality – it all comes from WorkBook.

The Facebook model is to encourage vendors like WorkLight to develop 3rd party apps and hence, enrich Facebook’s value by bringing more users to the party. As such, the assumption that a fee for WorkBook should be shared with Facebook is not correct. Just thought I would clear that up.</description>
		<content:encoded><![CDATA[<p>Bill,</p>
<p>WorkBook is a security overlay for Facebook. The way it works is an employee to a company logs into his public Facebook account and then installs the WorkBook application, just like they would install Funwall or SuperPoke. Once the application is installed, they are authenticated by their enterprise authentication engine, which provides them with the appropriate access to enterprise data based upon their corporate roles. This information is served from the WorkBook server (which is installed behind the firewall) and viewed on a Facebook canvas (technically an iFrame).</p>
<p>What the customers are paying for is not for any Facebook functionality, but rather for an on-premise server that is able to securely serve protected enterprise data through Web 2.0 tools, like Facebook. Facebook, in this case, is the front-end tool through which information is delivered, much like iGoogle, MS Live, Netvibes, and other home page servers can be used to display application data via gadgets, widgets, or RSS (which is the original WorkLight functionality).</p>
<p>“Enterprise data” in the WorkBook context includes things like “Q&amp;A,” search for expertise, news sharing, contact information sharing, even application data, – basically all the social networking functions one would expect. However, Facebook provides none of this functionality – it all comes from WorkBook.</p>
<p>The Facebook model is to encourage vendors like WorkLight to develop 3rd party apps and hence, enrich Facebook’s value by bringing more users to the party. As such, the assumption that a fee for WorkBook should be shared with Facebook is not correct. Just thought I would clear that up.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
