Open Web

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.

excerpt:  Social Business 4.0 (SBS), is Jive's latest version of its enterprise collaboration technology. In this new release, Jive includes deep integration with Microsoft Office, a mobile application for the iPhone and Blackberry plus the ability to bridge from internal to external communities. Jive is offering the ability to create or save documents in Microsoft Office with automatic upload to the Jive platform. Documents are rendered for the browser for users to view and make comments.Users may also collaborate on documents such as Power Point presentations. This co-authoring feature is similar to what you can do in Google Docs.

Review of SharePoint-Office 2010 integration.  MSOffice access and integration with SharePoint "content" has been improved and expanded.  Templates, forms and reports have been moved to the SharePoint center.  Or should i say "the many possible SharePoint centers".   There is also an interesting integration of the tagging system, with smart-tags becoming Bing enriched.  Good-bye Google.  Good-bye RDF - RDFa. excerpt:  Many enterprises buy into Microsoft's integrated vision of collaboration because they assume their products work well together. While in the case of SharePoint and Office this is technically true (more so with the 2007 versions), many of these integrations are either not used by or not visible to the average Office user. However, integrations introduced in SharePoint and Office 2010 may change this perception because they are exposed in menus and dialogs used by nearly every Office user. Perhaps supporting SharePoint Online and having SharePoint provide the basis of Office Live Workspaces is encouraging the SharePoint and Office planners to take a more user-centric perspective. In any case, here are some of the new integrations between SharePoint and Office 2010 that you should look for.

The ripples from the European Commission v. Microsoft decision continue to flow. The catch, of course, is that the patent rights will almost certainly be subject to the Microsoft Open Specification Promise, a weasel-worded document that actually grants no rights. http://law.bepress.com/unswwps/flrps/art71/ But someone with some clout will push that issue sooner or later.

Gartner Analyst Michael Silver wrote the study, "Windows 7 is all but inevitable".  Here is a quote explaining why it's near impossible to migrate away from MSOffice and the MSOffice Productivity Environment: There have been many organizations that have investigated moving off Microsoft Office, usually to a distribution of OpenOffice.org (including the free download, Sun's StarOffice, Novell Edition and IBM Symphony), but relatively few have actually made the migration. Impediments include switching costs, issues with macros, stationery, databases and mail clients. For better or worse, for the past 15 years, organizations have chosen to overprovision and deploy a product that can do everything the most-advanced user requires to every user for the sake of homogeneity. Organizations that want to deploy OpenOffice.org (OO.o) need to come to terms with the fact that some users will still require MS Office and they will be forced to support a mix of products. To Gartner, it makes sense to take advantage of viable perpetual licenses for Microsoft Office for as long as possible. The expensive product you already own will be cheaper than the cheap or "free" product you need to spend money to which to migrate.

excerpt: The trend in Office development is the migration of solutions away from in-application scripted processing toward more data-centric development. Of course this is a primary purpose of Open XML, and it is great to see the amount of activity in this area. We've seen customers scripting Word in a server environment to batch process / print documents or for other automation tasks. In reality Word isn't built to do that on a large scale, it is better to work directly against the document rather than via the application whenever possible. The Open XML SDK unlocks a "whole nuther" environment for document processing, and gets you out of the business of scripting client apps on servers to do the work of a true server application (not to mention the licensing problems created by installing Office on a server). comment:  Gray makes a very important point here.  The dominance of the desktop based MSOffice Productivity Environment was largely based the embedded logic driving "in-process" documents that was application and platform (Win32 API) specific.  Tear open any of these workgroup-workflow oriented compound documents and you find application specific scripts, macros, OLE, data bindings, security settings and other application specific settings.  These internal components are certain to break whenever these highly interactive and "live" compound documents are converted to another format, or application use.  This is how MSOffice documents and the business processes they represent become "bound" to the MSOffice Productivity Environment. What Gray is pointing to here is that Microsoft is moving the legacy Productivity Environment to an MSWeb based center where OpenXML, Silverlight, CAML, XAML and a number of other .NET-WPF technologies become the workgroup drivers.  The key applications for the MS WebStack are Exchange/SharePoint/SQL Server.  To make this move, documents had to be separated from the legacy desktop Productivity Environment settings. Note th

Michael Hickins separates the platform forest from the application trees, putting the focus of the future where it belongs - the movement of the legacy MSOffice Productivity Environment to the Web.  The only question will be which Web?  The Open Web?  Or the MS-Web? excerpt:  Microsoft and Apple have leveraged a particular dominant proprietary platform (Windows/Office in one case, the iPhone/iTunes duopoly in the other) to turn every other vendor into a bit player; and by allowing other vendors to sell products or services that integrate with theirs, they offer just enough incentives for the others to play along. Google is also leveraging a dominant platform (in this case, the Web, the largest platform there is) just as relentlessly as Microsoft and Apple have done, but with an open source philosophy that encourages others to compete. The ecosystem includes everything from a development platform to application suites, but its strength emanates from a basic understanding of what it takes to dominate technology: you have to control what former Open Document Foundation director Gary Edwards calls the "point of assembly" - that crucial spot where end users have to come in order to save, share and retrieve their documents - the final work product that all this technology is meant to help create. What Google is in the process of doing is moving that point of assembly from the desktop, where Microsoft and Apple rule, to the Web, where Google is king.

Neil McAllister provides an in-depth no-holds-barred comparison of Google, Zoho and Micorsoft Web Office Productivity Apps.  It's not pretty, but spot on honest.  Some of the short comings are that Neil overly focuses on document fidelity, but is comparatively light on the productivity environment/platform problems of embedded business logic.  These document aspects are represented by internal application and platform specific components such as OLE, scripting, macros, formulas, security settings, data bindings, media/graphics, applications specific settings, workflow logic, and other ecosystem entanglements so common to MSOffice compound "in-process" business documents.   Sadly, Neil also misses the larger issue that Microsoft is moving the legacy MSOffice Productivity Environment to a MS-Web center.   excerpt:  A spreadsheet in your browser? A word processor on the Web? These days, SaaS (software as a service) is all the rage, and the success of Web-based upstarts like Salesforce.com has sent vendors searching for ever more categories of software to bring online. If you believe Google, virtually all software will be Web-based soon -- and as if to prove it, Google now offers a complete suite of office productivity applications that run in your browser. Google isn't the only one. A number of competitors are readying Web-based office suites of their own -- most prominently Zoho, but even Microsoft is getting in on the act. In addition to the typical features of desktop productivity suites, each offering promises greater integration with the Web, including collaboration and publishing features not available with traditional apps.

Well well well.  Doug Crawford is concerned about "breakign the Web".  He even mentions "avalon", otherwise known as the Windows Presentation Foundation layer of proprietary MS-Web technologies designed as rich-Web alternatives to Open Web Standards like AJAX, HTML, CSS, SVG/Canvas, and JavaScript. excerpt:  Among the key issues in the Internet space today is the ongoing struggle between openness and stability in terms of standard Web technology, said a Yahoo Web technology expert. Doug Crockford, a JavaScript expert at Yahoo, calls on his company and others to not "break the Web" as they each vie for developer hearts and minds.