Comments on: Collaborating with competitors http://www.wikinomics.com/blog/index.php/2009/06/03/collaborating-with-competitors/ Exploring How Mass Collaboration Changes Everything Sun, 28 Aug 2011 14:21:24 +0000 hourly 1 http://wordpress.org/?v=3.2.1 By: Potty Training http://www.wikinomics.com/blog/index.php/2009/06/03/collaborating-with-competitors/comment-page-1/#comment-348708 Potty Training Sat, 27 Feb 2010 07:49:23 +0000 http://www.wikinomics.com/blog/?p=3860#comment-348708 It's good business but too bad most competitors don't see eye to eye on this. You tap into a source of very VERY targeted leads and create a win/win situation! It’s good business but too bad most competitors don’t see eye to eye on this. You tap into a source of very VERY targeted leads and create a win/win situation!

]]> By: Kevin Cochrane http://www.wikinomics.com/blog/index.php/2009/06/03/collaborating-with-competitors/comment-page-1/#comment-289452 Kevin Cochrane Fri, 12 Jun 2009 03:28:46 +0000 http://www.wikinomics.com/blog/?p=3860#comment-289452 Arvind: great question. Today, a web developer building a new application may typically download various components like an open source database and application server and directly build his/her app directly against the RDBMS. All of the core content services the developer will have to implement atop the RBDMS - versioning, observation, access control, search, and more. And then for the next application, rebuild the entirety of that bespoke functionality again for the next app. This is inefficient. As a backend persistance manager, RDBMSes will not go away. However, as Jackrabbit adoption grows, directly building apps atop the RDBMS will shift as developers increasingly build their content applications directly atop Jackrabbit to eliminate the need for building bespoke content services again and again and instead take advantage of the pre-built capabilities and higher level API afforded by Jackrabbit or any other JCR implementation. Will all content applications one day be based on a standardized content repository infrastructure? Here at Day and at many other of the newer, JCR-based CMS vendors, we certainly think so. Arvind: great question. Today, a web developer building a new application may typically download various components like an open source database and application server and directly build his/her app directly against the RDBMS. All of the core content services the developer will have to implement atop the RBDMS – versioning, observation, access control, search, and more. And then for the next application, rebuild the entirety of that bespoke functionality again for the next app. This is inefficient.

As a backend persistance manager, RDBMSes will not go away. However, as Jackrabbit adoption grows, directly building apps atop the RDBMS will shift as developers increasingly build their content applications directly atop Jackrabbit to eliminate the need for building bespoke content services again and again and instead take advantage of the pre-built capabilities and higher level API afforded by Jackrabbit or any other JCR implementation.

Will all content applications one day be based on a standardized content repository infrastructure? Here at Day and at many other of the newer, JCR-based CMS vendors, we certainly think so.

]]> By: Links 07/06/2009: More Migrations to GNU/Linux in Schools, Shop | Boycott Novell http://www.wikinomics.com/blog/index.php/2009/06/03/collaborating-with-competitors/comment-page-1/#comment-288350 Links 07/06/2009: More Migrations to GNU/Linux in Schools, Shop | Boycott Novell Mon, 08 Jun 2009 00:35:28 +0000 http://www.wikinomics.com/blog/?p=3860#comment-288350 [...] Collaborating with competitors From ancient philosophers to modern day journalists, the rules of engagement for discourse and collaboration have always been hot topics. In ancient times mass collaboration was limited to communities building churches, discussion in public squares, or monks taking turns to painstakingly write text. Today, in addition to facilitating public debate online, mass collaboration has the ability to build robust and super efficient software. Collaboration is central to Day Software’s ethos. Not only is Day Software born through mass collaboration but its software has social collaboration central to its user experience. We also embrace collaboration with our competitors. The last area is one I want to focus on for this post. [...] [...] Collaborating with competitors From ancient philosophers to modern day journalists, the rules of engagement for discourse and collaboration have always been hot topics. In ancient times mass collaboration was limited to communities building churches, discussion in public squares, or monks taking turns to painstakingly write text. Today, in addition to facilitating public debate online, mass collaboration has the ability to build robust and super efficient software. Collaboration is central to Day Software’s ethos. Not only is Day Software born through mass collaboration but its software has social collaboration central to its user experience. We also embrace collaboration with our competitors. The last area is one I want to focus on for this post. [...]

]]> By: Arvind Gupta http://www.wikinomics.com/blog/index.php/2009/06/03/collaborating-with-competitors/comment-page-1/#comment-287432 Arvind Gupta Thu, 04 Jun 2009 10:57:44 +0000 http://www.wikinomics.com/blog/?p=3860#comment-287432 As jackrabbit evolves application will be able to collabarate more with each other. How do you see roles of database at that time? As jackrabbit evolves application will be able to collabarate more with each other. How do you see roles of database at that time?

]]>