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.

Byron Deeter is right, but perhaps he's holding back on his reasoning.  Silicon Valley is all about platform, and platform plays only come about once every ten to twenty years.  They come like great waves of change, not replacing the previous waves as much as taking away and running with the future.   Cloud Computing is the fourth great wave.  It will replace the PC and Network Computing waves as the future.  It is the target of all developers and entrepreneurs.   The four great waves are mainframe, workstation, pc and networked pc, and the Internet.  Cloud Computing takes the Internet to such a high level of functionality that it will now replace the pc-netwroking wave.  It's going to be enormous.  Especially as enterprises move their business productivity and data / content apps from the desktop/workgroup to the Cloud.  Enormous. The key was the perfect storm of 2008, where mobility (iPhone) converged with the standardization of tagged PDF, which converged with the Cloud Computing application and data model, which all happened at the time of the great financial collapse.   The financial collapase of 2008 caused a tectonic shift in productivity.  Survival meant doing more with less.  Particularly less labor since cost of labor was and continues to be a great uncertainty.  But that's also the definition of productivity and automation.  To survive, companies were compelled to reduce labor and invest in software/hardware systems based productivity.  The great leap to a new platform had it's fuel; survival. Social applications and services are just the simplest manifestation of productivity through managed connectivity in the Cloud.  Wait until this new breed of productivity reaches business apps!  The platform wars have begun, and it's for all the marbles. One last thought.  The Internet was always going to win as the next computing platform wave.  It's the first time communications have been combined and integrated into content, and vast dat

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?

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.

Good discussion, but it really deserves a more in-depth thrashing.  The basic concept is that a perfect storm of mobility, cloud-computing and HTML5-JavaScript has set the stage for a major, massive shift in application development.  The shift from C++ to Java is now being replaced by a greater shift from Java and C++ to JavaScript-JSON-HTML5. Interesting, but i continue to insist that the greater "Perfect Storm" triggered in 2008, is causing a platform shift from client/server computing to full on, must have "cloud-computing".   There are three major "waves"; platform shifts in the history of computing at work here.  The first wave was "Mainframe computing", otherwise known as server/terminal.  The second wave was that of "client/server" computing, where the Windows desktop eventually came to totally dominate and control the "client" side of the client/server equation. The third wave began with the Internet, and the dominance of the WWW protocols, interfaces, methods and formats.  The Web provides the foundation for the third great Wave of Cloud-Computing. The Perfect Storm of 2008 lit the fuse of the third Wave of computing.  Key to the 2008 Perfect Storm is the world wide financial collapse that put enormous pressure on businesses to cut cost and improve productivity; to do more with less, or die.  The survival maxim quickly became do more with less people - which is the most effective form of "productivity".  The nature of the collapse itself, and the kind of centralized, all powerful bailout-fascists governments that rose during the financial collapse, guaranteed that labor costs would rise dramatically while also being "uncertain".  Think government controlled healthcare. The other aspects of the 2008 Perfect Storm are mobility, HTML5, cloud-computing platform availability, and, the ISO standardization of "tagged" PDF.   The mobility bomb kicked off in late 2007, with the introduction of the Apple iPhone.  No further explanation needed :) Th

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.

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.

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

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.

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...."

Another great review for Conrado. Summary: OpenGoo is an open source web/Cloud office where all resources and aspects of contact and project management are linked. This includes eMail, calendar, task, schedules, time lines, notes, documents, workgroups and data. Great stuff. OpenGoo and hosted sister Feng Office are the first Web Office systems to challenge the entire Microsoft Office productivity environment. Very polished, great performance. Excellent use of URI's to replace Win32-OLE functionality. Lacks direct collaboration of Zoho and gDOCS. Could easily make up for that and more with the incorporation of Wave computing (Google). I'm wondering when Conrado will take on the vertical market categories; like Real Estate - Finance? I also think OpenGoo and Feng Office have reached the point where governments would be interested. Instead of replacing existing MSOffice desktops, migrate the project/contact management stuff to OpenGoo, and shut down the upgrade treadmill. Get into the Cloud. I suspect also that Conrado is looking carefully at Wave Computing, and the chellenge of incorporating Wave into OpenGoo.

This is a really good descriptive "story" about Google Wave, and why it' revolutionary.

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.

Another good article form Michael Hickins, this time linking the success of Google Wave to the success of Microsoft OOXML. Rob Weir jumps in to defend , well, i'm not sure. I did however respond. Excerpt: Developers hoping to hitch a ride on Google's Wave have discovered that Microsoft may have unwittingly helped them resolve the single greatest problem they needed to overcome in order to challenge the dominance of Office. When Microsoft set out to create Office 2007 using a brand new code base - Office Open XML (OOXML) - it needed to accomplish two goals: make it compatible with all previous versions of Office, and have it accepted as a standard file format for productivity tools so that governments could continue using it while complying with rules forcing them to use standards-based software. ..... Depending on your perspective, either Microsoft has sowed the seeds of its own undoing, or international standards bodies succeeded in forcing Microsoft to open itself up. Either way, Microsoft has given away the key to compatibility with Office documents, allowing all comers to overcome the one barrier that has heretofore prevented customers from dumping Microsoft's Office suite.