<?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>Kommentare zu: Interview with Markus Hegi, Founder &amp; CEO Colayer</title>
	<atom:link href="http://blog.internet-briefing.ch/2009/06/22/interview-with-markus-hegi-founder-ceo-colayer/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.internet-briefing.ch/2009/06/22/interview-with-markus-hegi-founder-ceo-colayer/</link>
	<description>Beobachtet das Internet - Web 2.0, Ajax, Online Marketing, Usability, Best Practices etc.</description>
	<lastBuildDate>Tue, 17 Jan 2012 12:28:59 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>Von: Quora</title>
		<link>http://blog.internet-briefing.ch/2009/06/22/interview-with-markus-hegi-founder-ceo-colayer/comment-page-1/#comment-322477</link>
		<dc:creator>Quora</dc:creator>
		<pubDate>Wed, 29 Dec 2010 10:51:10 +0000</pubDate>
		<guid isPermaLink="false">http://blog.internet-briefing.ch/?p=1650#comment-322477</guid>
		<description>&lt;strong&gt;How Colayer is different from Google Wave or is it just an extension of it?...&lt;/strong&gt;

Colayer was there long before Google Wave. Hence it is neither an extension, nor based on the same platform, but the concepts are very similar. 
Colayer did not have a public version, but was for enterprises only and therefore little known to the publi...</description>
		<content:encoded><![CDATA[<p><strong>How Colayer is different from Google Wave or is it just an extension of it?&#8230;</strong></p>
<p>Colayer was there long before Google Wave. Hence it is neither an extension, nor based on the same platform, but the concepts are very similar.<br />
Colayer did not have a public version, but was for enterprises only and therefore little known to the publi&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>Von: Rob Betgem</title>
		<link>http://blog.internet-briefing.ch/2009/06/22/interview-with-markus-hegi-founder-ceo-colayer/comment-page-1/#comment-230962</link>
		<dc:creator>Rob Betgem</dc:creator>
		<pubDate>Mon, 27 Jul 2009 13:45:14 +0000</pubDate>
		<guid isPermaLink="false">http://blog.internet-briefing.ch/?p=1650#comment-230962</guid>
		<description>Most interesting subject on collaboration, keeping lots of minds busy on how business processes and communication can be improved. These two initiatives (Google wave and Colayer) focusing on how to attack fragmentation and duplication of information; stimulating collaborative way on how to exchange information, eliminating the number of tools exposed to the user , keeping track of the context and history of all content associated with a particular task etc.. All things concerning the collaboration problem set. 

It might be worthwhile mentioning that some OS portal / CMS solution providers try to address this problem for quite some time. Maybe an opportunity to have a closer look at LifeRay OS collaboration software, the recently announced Social Office solution, which covers lots of these areas as described above. Main targets are, as mentioned in the previous article, bringing down the number of different tools, structuring, organizing data, keeping track of versioning and more content management aspects. Keeping the communication wire clean. Losts these aspects are getting covered by LifeRay collaboration software. And not totally unimportant, it is for free, it is backed up by professional support, has an impressive user and development community, and is from stretch build on top of open standards. For integrators a relieve, no exotic non standard technologies that might lock you in on one provider.

Another problem area is how to integrate more than all these chats, documents, message boards, blogs and wikis into this information wave. How can we integrate core business data from our core systems into this mix of information. And specifically here is where the power of the on open standards based  LifeRay solution has a strong point, the seamless integration of ESB and BPM solutions like jboss JBM and Apache service mix. This will open the door for integrating other processes and data into this information mix, based on standards like webservices, WSRP, SOAP, BPEL and so on.

Another nice aspect is that end users are not forced to change the way they handle their office suite. &quot;LifeRay Social Office makes use of publicly available SharePoint® protocols to allow users to open, save, version, lock, and share documents directly between LifeRay Social Office and Microsoft Office®. This opens up new ways of integrating desktop workflow with web-based collaboration and document storage.&quot;


Allows you to work on a task based criteria, collecting all relevant context and history on artefacts belonging to that specific task. Important is that this task can be teamed up with users participating in this flow of work. Problem is however, who are you collaborating with, how can you organize this collaboration within the guidelines of engagement on who you are allowed to exchange certain data with, what are the security issues here. LifeRay portal helps solving these organizational structure issues and enables setting up well designed workflows on top of complex organization structures, so you get the 
actual collaboration structure and content context in a secured and manageable fashion. 

Apart of this all, accept the fact that lifeRay is build on top of standards and widely used technologies, LifeRay supports all major application servers, databases and operating systems, minimizing the danger to get locked in by what kind of extend and making your final solutions flexible and scalable in a production like environment. 

Getting curious?, just check out the feature list on this most elegant framework. http://www.liferay.com/web/guest/products/social_office

Btw, maybe it would nice to open a dedicated blog post on portal technology.

Rob</description>
		<content:encoded><![CDATA[<p>Most interesting subject on collaboration, keeping lots of minds busy on how business processes and communication can be improved. These two initiatives (Google wave and Colayer) focusing on how to attack fragmentation and duplication of information; stimulating collaborative way on how to exchange information, eliminating the number of tools exposed to the user , keeping track of the context and history of all content associated with a particular task etc.. All things concerning the collaboration problem set. </p>
<p>It might be worthwhile mentioning that some OS portal / CMS solution providers try to address this problem for quite some time. Maybe an opportunity to have a closer look at LifeRay OS collaboration software, the recently announced Social Office solution, which covers lots of these areas as described above. Main targets are, as mentioned in the previous article, bringing down the number of different tools, structuring, organizing data, keeping track of versioning and more content management aspects. Keeping the communication wire clean. Losts these aspects are getting covered by LifeRay collaboration software. And not totally unimportant, it is for free, it is backed up by professional support, has an impressive user and development community, and is from stretch build on top of open standards. For integrators a relieve, no exotic non standard technologies that might lock you in on one provider.</p>
<p>Another problem area is how to integrate more than all these chats, documents, message boards, blogs and wikis into this information wave. How can we integrate core business data from our core systems into this mix of information. And specifically here is where the power of the on open standards based  LifeRay solution has a strong point, the seamless integration of ESB and BPM solutions like jboss JBM and Apache service mix. This will open the door for integrating other processes and data into this information mix, based on standards like webservices, WSRP, SOAP, BPEL and so on.</p>
<p>Another nice aspect is that end users are not forced to change the way they handle their office suite. &#8220;LifeRay Social Office makes use of publicly available SharePoint® protocols to allow users to open, save, version, lock, and share documents directly between LifeRay Social Office and Microsoft Office®. This opens up new ways of integrating desktop workflow with web-based collaboration and document storage.&#8221;</p>
<p>Allows you to work on a task based criteria, collecting all relevant context and history on artefacts belonging to that specific task. Important is that this task can be teamed up with users participating in this flow of work. Problem is however, who are you collaborating with, how can you organize this collaboration within the guidelines of engagement on who you are allowed to exchange certain data with, what are the security issues here. LifeRay portal helps solving these organizational structure issues and enables setting up well designed workflows on top of complex organization structures, so you get the<br />
actual collaboration structure and content context in a secured and manageable fashion. </p>
<p>Apart of this all, accept the fact that lifeRay is build on top of standards and widely used technologies, LifeRay supports all major application servers, databases and operating systems, minimizing the danger to get locked in by what kind of extend and making your final solutions flexible and scalable in a production like environment. </p>
<p>Getting curious?, just check out the feature list on this most elegant framework. <a href="http://www.liferay.com/web/guest/products/social_office" rel="nofollow"></a><a href='http://www.liferay.com/web/guest/products/social_office'>http://www.liferay.com/web/guest/products/social_office</a></p>
<p>Btw, maybe it would nice to open a dedicated blog post on portal technology.</p>
<p>Rob</p>
]]></content:encoded>
	</item>
	<item>
		<title>Von: Jennifer</title>
		<link>http://blog.internet-briefing.ch/2009/06/22/interview-with-markus-hegi-founder-ceo-colayer/comment-page-1/#comment-223103</link>
		<dc:creator>Jennifer</dc:creator>
		<pubDate>Tue, 23 Jun 2009 04:57:04 +0000</pubDate>
		<guid isPermaLink="false">http://blog.internet-briefing.ch/?p=1650#comment-223103</guid>
		<description>Most organisations use have their own home built system like the hospital I work at uses MedWay to store patients documents. Has all the features such as last modified by what doctor etc.</description>
		<content:encoded><![CDATA[<p>Most organisations use have their own home built system like the hospital I work at uses MedWay to store patients documents. Has all the features such as last modified by what doctor etc.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

