Group items tagged

Dion Hinchcliffe has an excellent article casting Google Wave as an Enterprise game-changer. He walks through Wave first, and then through some important enterprise features: ".....to fully understand Google Wave, one should appreciate the separation of concerns between the product Google is offering and the protocols and technologies behind it, which are open to the Web community: Google Wave has three layers: the product, the platform, and the protocol: The Google Wave product (available as a developer preview) is the web application people will use to access and edit waves. It's an HTML 5 app, built on Google Web Toolkit. It includes a rich text editor and other functions like desktop drag-and-drop (which, for example, lets you drag a set of photos right into a wave). Google Wave can also be considered a platform with a rich set of open APIs that allow developers to embed waves in other web services, and to build new extensions that work inside waves. The Google Wave protocol is the underlying format for storing and the means of sharing waves, and includes the "live" concurrency control, which allows edits to be reflected instantly across users and services. The protocol is designed for open federation, such that anyone's Wave services can interoperate with each other and with the Google Wave service. To encourage adoption of the protocol, we intend to open source the code behind Google Wave.

Good article.  One of the first to go beyond the demo, recognizing that Wave is application platform - a wrapper for the convergence of communications and content. Excerpt: Wave is a new way to build distributed applications, and it will open the door to an explosion of innovation. What the Wave demo showed is support for a continuum from the shortest messages to longer and longer forms of content. All of it can be shared with precise control, tagged, searched. The version history is kept. No more mailing around a document. This takes the beauty of e-mail and wikis and extends it in a more flexible way to a much larger audience. Google Wave is a platform for creating distributed applications. Each Wave server can be involved in a number of conversations involving Wavelets, what most people would think of as a document. Wavelets are actually a much more powerful and general because they are based on XML, which means you can have lots of depth of content, like headings and subheadings of a book, but on steroids. Adding a document repository to XMPP is just revolutionary. The XMPP protocol manages the communication between the Wave servers so that all the Wavelets can synchronize as they are changed. Then Google finished the job by making Wavelets tag-able, searchable and versioned, so you can play back changes. But Google Wave goes beyond just managing the content--it also manages the programs that act on the content. At any level, a program can be assigned to a Wavelet to render it, that is, show it to a user and help manage the conversation. Google Wave also manages the distribution and management of these programs. The idea of a platform that combines management of the data and the code is really powerful.

Summary: Collaborative document editing means multiple editors being able to edit a shared document at the same time.. Live and concurrent means being able to see the changes another person is making, keystroke by keystroke. Currently, there are already a number of products on the market that offer collaborative document editing. Some offer live concurrent editing, such as EtherPad and SubEthaEdit, but do not offer rich text. There are others that offer rich text, such as Google Docs, but do not offer a seamless live concurrent editing experience, as merge failures can occur. Wave stands as a solution that offers both live concurrent editing and rich text document support.  The result is that Wave allows for a very engaging conversation where you can see what the other person is typing, character by character much like how you would converse in a cafe. This is very much like instant messaging except you can see what the other person is typing, live. Wave also allows for a more productive collaborative document editing experience, where people don't have to worry about stepping on each others toes and still use common word processor functionalities such as bold, italics, bullet points, and headings. Wave is more than just rich text documents. In fact, Wave's core technology allows live concurrent modifications of XML documents which can be used to represent any structured content including system data that is shared between clients and backend systems. To achieve these goals, Wave uses a concurrency control system based on Operational Transformation.

Google programmers open source two components of the Google Wave messaging and collaboration prototype. One includes the Operational Transform, which forms the complex center of the Wave model. Google Wave is an example of the Pushbutton Web, where real-time communications rule the roost. Google July 24 said it released to open source the OT (Operational Transform) code, the framework that enables multiple people to edit a single document in real time across a wide-area network, as well as a basic client/server prototype that uses the wave protocol. The Google Wave Federation Protocol is an open extension to the XMPP core protocol, geared to allow near real-time communication of wave updates between two wave servers.

Some good questions are being asked about the future of Google Wave and collaborative computing.  He misses however another important play for Wave; moving to the center of the emerging Open Web Productivity Environment. excerpt:  Google Wave is another grab for the Holy Grail of collaborative computing. But, will it be more successful than previous attempts? Whenever you see something compared to Lotus Notes, as Google Wave has been, you know to expect an uphill slog. Add a comparison to Microsoft Groove, which I have not seen but seems reasonable, and you can expect deep trouble. Both Notes and Groove are wonderful, innovative applications that have never caught on as I had hoped. Why? They are too difficult to use and develop for. They were way ahead of their time. Maybe Google Wave, a workplace collaboration application that is being rolled out to an additional 100,000 beta testers, has arrived at the right time, finding the right mix of power vs. ease-of-use, and the right metaphor for delivering it. We have an excellent story that offers "Five Reasons To Dive Into Google Wave." That is, if you can find a way to get into the beta. The big question: Can Google Wave succeed where seemingly every collaboration application that has gone has failed?

A must-see video if you're interested in the dance of sugar plum documents, what can be done with HTML5-plus, and an outside-the-box approach to online collaboration. Google just may have a winner in Wave.

The company halted its work on Wave, but aspects of its radical approach to communication have been reincarnated for business collaboration. When Google Wave launched in 2009, the company suggested the program was a "new category" of communication because it combined the virtues of e-mail, instant messaging, and methods for sharing pictures, links, and other documents. Among its other features, Wave went a step beyond IM by letting people see what their message partners were writing as they typed it. That meant that the people on the receiving end of your messages would see characters appear onscreen even before you had finished formulating a sentence. It was a radical approach. I tried Wave myself and found it very distracting to watch people type, delete, retype, and misspell their thoughts. People I had persuaded to try it with me never signed in again, unsure as to how it was useful. We weren't alone in our confusion: last year, Google announced it would stop developing Wave. And yet, Google Wave lives on-in business software.

Excellent Wave coverage from Scott M. Fulton III.  The Hollywood Movie industry use case scenario is very interesting.  But Scott is one of the few people to draw an analogy between Google Wave convergence of concurrent communications and collaborative content and the early days of the Microsoft Office Productivity Platform where we saw DDE, OLE and MAPI rise and rule. Excerpt: Today, Google is expected to invite as many as 100,000 more participants into the private beta of its concurrent communications system, called Wave. As that happens, many more participants will be able to not only communicate with one another in a more granular form of real-time, but potentially collaborate on work and projects. It's that latter part of the program that's supposed to congeal at some point into a collective sense of purpose. But this time, unlike Microsoft's first experiments with Dynamic Data Exchange between applications on the same computer three decades ago, there isn't yet a clear, single purpose for the system. No question it could bring individuals as close together as people separated by indefinite distance could become; but as to the question of what they do with one another once they do get together, Google is hoping this question -- like so many others it puts out there in the open -- resolves itself. Yesterday, Google offered links to a number of different independent assessments of the possible, eventual purpose of Google Wave, though it offered them as use-case scenarios rather than projections of possible goals for the product...which is what many actually were.

"Gary Edwards on Mar 15, 8:25 PM said: There are only three apps i load at boot-up: gMail, gReader, and gWave. Ooops! Google Wave was cancelled over a year ago. Owning the end-users attention at boot-up proved to be an essential factor to the Microsoft monopoly. They built an iron fisted empire out of owning the point of boot-up. So it's very strange to see Google give up the very thing other cloud platform contenders would no doubt kill for. Very strange. Even stranger though is the perception that Google + will somehow now move to center stage? The only reason i use Google+ is because it's easy to point to an article and post a comment from Google Reader to my + circles. Other than that i have no use for +. Nicolas Carr posted an interesting comment on Google's cancellation of gReader yesterday. He tried to argue that there is a difference between "tools" and "platforms", and Google was more interested in building a platform than maintaining "tools" like gReader. So, Google+ is now essential to the Google Platform? Unfortunately, the otherwise brilliant and cosmic insightful Mr. Carr, fails to make that case. Microsoft became a platform when they succeeded in positioning their OS as the essential factor bridging an explosively innovative and rapidly commoditiz'ing Windows hardware reference platform, and, he equally rapid and innovative Windows software application platform. Both software and hardware were being written and developed to the Windows OS, with features doubling and costs being halved at a rate that even Moore's Law envied. Microsoft fully cemented the emerging hardware - OS - application platform with a business productivity environment that necessitated the use of the MS Office suite of servers and apps. That lock on business productivity has yet to be broken. And even though the mighty Google Apps has made some progress convincing businesses to rip-out-and-replace their legacy business productivity systems and re write to the Google Cloud P

Jonathan Rochelle and Dave Girouard: Google's long-term vision of computing is based around the notion that the Web and the browser become the primary vehicles for applications, and Google Docs is an important part of realizing that vision. The main improvement was to create a common infrastructure across the Google Docs products, all of which came into Google from separate acquisitions, Rochelle said. This has paved the way for Google to offer users a chance to do character-by-character real-time editing of a document or spreadsheet, almost the same way Google Wave lets collaborators see each other's keystrokes in a Wave. Those changes have also allowed Google to take more control of the way documents are rendered and formatted in Google Docs, instead of passing the buck to the browser to make those decisions. This allows Google to ensure that documents will look the same on the desktop or in the cloud, an important consideration for designing marketing materials or reviewing architectural blueprints, for example.

Oliver has a short post concerning Google Wave and the new world the Wave will have wrought. Once section in particular caught my eye:
Two behemoths going after each others markets
..."Google apps, while a very popular tool for students, has never caught on in the enterprise due to security concerns, with a few exceptions - Microsoft Office is the default in cubicle land. Google search meanwhile is currently the global market leader, and is a popular enterprise solution in the form of internal appliances behind the firewall, while Microsoft's search and associated electronically stored information taxonomy and tagging has been famously weak."
"While these two giants slug it out for the others coveted market the playing field may well change significantly as the third big internet revolution unfolds. We've gone from Web 1.0, the read only static html website world to Web 2.0, the read-write, 'user generated content' web. The explosion in interconnectedness is at the expense of information fragmentation: the third web generation (Web 3.0?) is all about the meaning and context of data and information.
"Behaviorally suggested content; the personalized experience of a web that seems to know you and anticipates what you want is just around the corner...."

ge post explaining why Google Wave is valuable to the way i "now" work.  Discusses Miro's NoteCase Pro, OpenOffice, HTML5, and Wave OTXML.

Wave has finally taken over gDOCS.  Entirely.  Are you paying attention Florian and Jason?  This is it.  Your ship has come in.  The final key for Google will be that of being able to work with native OOXML documents, in a Wave, without breaking them.  Round-trip of in-process compound business productivity documents is the last part of the puzzle Google needs to crack the mighty Microsoft monopoly. excerpt: "When we launched the new Google Docs last April, one of the big changes was moving comments to the sidebar and letting people reply to comments. Today, we're updating comments in Google Docs to facilitate rapid and seamless discussions and integrate with email in an intuitive way. Since there are a number of significant" improvements, this update is only available for newly created documents for now.

Good article from Stephen Shankland describing how the Wave-HTML5-O3D-Web Worker pieces fit. He left out GWT. But this after all, one very big picture. Google has thrown down a game changer. Wave represents one of those rare inflection points where everything immediately changes. There is no way to ignore the elephant that just sat on your face. Google has been demonstrating its sandboxing technology for making web applications perform at similar levels to those associated with native desktop applications. Google Native Client, still highly experimental, lets browsers run program modules natively on an x86 processor for higher performance than with web-programming technologies, such as JavaScript or Flash, that involve more software layers to process and execute the code. But to use it, there is a significant barrier: people must install a browser plug-in.

Om Malik has an interesting commentary on Google Voice, the Android OS, and a new gVoice application for iPhones and Androids. For sure, new gVoice app meshes into the Andorid OS as if it were hard coded into the silicon. I left a lengthy comment in the discussion section describing my experiences with gVoice and what i see emerging as Google's Unified Productivity Platform. Of course, gWave, Chrome, Chrome OS, webkit-HTML+, and the sweep of Google Web applications and service come into play. Excerpt: Can Google be your phone company? The answer is yes. I came to that conclusion after I met with Vincent Paquet, co-founder of GrandCentral (a company acquired by Google) and now a member of the Google Voice team. Earlier today he stopped by our office to show the mobile app versions of its Google Voice service for Blackberry and Android. Google recently announced that it was going to make the Voice service widely available to users in the U.S. soon.

Nice catch and cast from Michael Hickens. He walks us through some strange goings on at SalesForce.com. It seems Commander Benioff has ordered the good ship SlaesForce to turn on a dime, drop everything, and set a course for Wave. Good stuff: "...... Could Salesforce be reengineering its AppExchange platform to run standards-based code like HTML 5? The reason I ask is that none other than Salesforce CEO Marc Benioff listed his status on Facebook this weekend as: "working on salesforce.com's new architecture." There would have to be a very good reason, or a transformational event like Google's introduction of its Wave, for the company to change a key element of its strategy.

"Horizon Info Services is committed to offering industry-leading technology services to small businesses at affordable prices." This is an interesting approach. Horizon is a reseller of customized and enhanced Google services. They provide enterprises and SMB's with gMail hosting, on-line backup services, security, and customized Google Apps. They are also ready to dive into Google Wave, as the ultimate interface for aggregating Web based communications, messaging, conversations and collaborative documents.