Open Web

Join your on-premises data sources with the web without coding. Feed data from/to APIs, mashups, and mashup building tools.

This document discusses the primary reason ODF failed in Massachusetts: compatibility with the MSOffice productivity environment, and, the billions of binary documents in use by MSOffice bound workgroups and the business processes so important to them.

Gary Edwards's List: Compatibility matters - The lessons of Massachusetts are many. Application level "compatibility" with existing MSOffice desktops and workgroups is vital. Format level "compatibility" with the legacy of billions of binary documents is vital. And "ecosystem" compatibility with the MSOffice productivity environment.

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.

Some good commentary on chrome OS from InformationWeek's Thomas Claburn. Excerpt: With Chrome OS, Google aims to make the Web the primary platform for software development....... The fact that Chrome OS applications will be written using open Web standards like JavaScript, HTML, and CSS might seem like a liability because Web applications still aren't as capable as applications written for specific devices and operating systems. But Google is betting that will change and is working to effect the change on which its bet depends. Within a year or two, Web browsers will gain access to peripherals, through an infrastructure layer above the level of device drivers. Google's work with standards bodies is making that happen..... ..... According to Matt Womer, the "ubiquitous Web activity lead" for W3C, the Web standards consortium, Web protocol groups are working to codify ways to access peripherals like digital cameras, the messaging stack, calendar data, and contact data. There's now a JavaScript API that Web developers can use to get GPS information from mobile phones using the phone's browser, he points out. What that means is that device drivers for Chrome OS will emerge as HTML 5 and related standards mature. Without these, consumers would never use Chrome OS because devices like digital cameras wouldn't be able to transfer data. Womer said the standardization work could move quite quickly, but won't be done until there's an actual implementation. That would be Chrome OS...... ..... Chrome OS will sell itself to developers because, as Google puts it, writing applications for the Web gives "developers the largest user base of any platform."

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.

Microsoft has announced the next generation of MSOffice, and it turns out to be SharePoint at the center of the deep connected MSOffice "rich client" desktop productivity environment, and, an online Web version of MSOffice. Who would have guessed that one of the key features to MOSS would be universal accessibility to and collaboration on MSOffice documents - without loss of fidelity? No doubt the embedded logic that drive BBP's (Bound Business Processes) is also perfectly preserved. Excerpt: "Office Web Applications, the online companion to Word, Excel, PowerPoint and OneNote applications, allow you to access documents from anywhere. You can even simultaneously share and work on documents with others online," Microsoft says on its Office 2010 Technical Preview site. "View documents across PCs, mobile phones, and the Web without compromising document fidelity. Create new documents and do basic editing using the familiar Office interface."

.... "While i don't see Google or anyone else replacing the MSOffice productivity environment anytime soon, i do see Google challenging Microsoft wherever the Web comes into play. As for the future, that battle for desktop productivity will take place, just not with ChromeOS, Linux, or, the MacOS. What has to happen before the assault on the Microsoft's productivity empire can begin is that the business systems bound to the MSOffice productivity environment must transition to the Open Web, via SaaS or some other replacement. Or, the productivity environment itself must be re-purposed to the Open Web. The tricky part will be that re-purposing play. ChromeOS is a blockbuster announcement. Not a declaration of war, but a shot across the bow that shouts; Google will defend the Open Web, and profitable business they have there. ..... ~ge~

Introducing the Chrome OS alternative to Windows: excerpt: What Google is doing is not recreating a new kind of OS, they're creating the best way to not need one at all. So why release this new OS instead of using Android? After all, it has already been successfully ported to netbooks. Google admits that there is some overlap there. But a key difference they don't mention is the ability to run on the x86 architecture. Android cannot do that (though there are ports), Chrome OS can and will. But more, Google wants to emphasize that Chrome OS is all about the web, whereas Android is about a lot of different things. Including apps that are not standard browser-based web apps. But Chrome OS will be all about the web apps. And no doubt HTML 5 is going to be a huge part of all of this. A lot of people are still wary about running web apps for when their computer isn't connected to the web. But HTML 5 has the potential to change that, as you'll be able to work in the browser even when not connected, and upload when you are again.

Modernizr is a new library that detects various HTML5 and CSS3 features and lets you know so you can use them: Enables the writing of conditional CSS and conditional JavaScript! The JS tools just keep coming.

Ouch! Phil lands on Cisco like a ton of bricks. He hears them Talk the talk but doubts Cisco can walk the walk. This is a very detailed analysis and indictment. Sounds to me that Cisco will sooner rather than later be out there shopping for Collaborative Web systems. Excerpt: Color me skeptical, but I feel the detail behind yesterday and today's Cisco Live event hasn't matched the aspirations set out in executive keynotes. I like the vision set out by CEO John Chambers of providing a technology infrastructure that (as Oliver Marks puts it) does a better job of connecting people. I'm highly supportive when CTO Padmasree Warrior looks ahead to a future fabric of 'intercloud' interoperability standards - ending lock-in by individual cloud providers - and talks about 'federation' between cloud and on-premise. But when I look at the map of where Cisco claims to play in the cloud, I'm struck by how feeble its tenure is at each level, from the underlying foundation all the way up to both Paas and SaaS, where WebEx is its undernourished poster child, as I'll discuss below.

A video with slide presentation featuring Google's Joshua Bloch. The topic is Java API Summary: A well-written API can be a great asset to the organization that wrote it and to all that use it. Given the importance of good API design, surprisingly little has been written on the subject. In this talk (recorded at Javapolis), Java library designer Joshua Bloch teaches how to design good APIs, with many examples of what good and bad APIs look like.

Über technologist Michael Hickens writes about the recent Cisco announcement that they intend on competing with Google, Zoho and MOSS in the cloud collaboration space. I left a lengthy comment on this page, trying to come to grips with the meaning of this challenge. I titled my comment, "Cisco Office? Maybe they should consider Feng Office-in-the-Cloud". Good luck Conrado. Go get them. Interestingly, Jason Harrop and i met Ms. Alex Hadden-Boyd, director of marketing for the collaboration software group at Cisco. She was kind enough to refer me directly to David Knight, the technology director of Cisco's WebEX Conferencing initiative. Alex is quoted in a CNet article at: http://news.cnet.com/8301-1001_3-10276549-92.html Cisco is striving to redefine itself as a vendor connecting inner and outer clouds, thus reasserting its relevance in the context of a fluid Web-driven IT world increasingly dominated by the likes of Google, Salesforce, Oracle and IBM. It also hopes to parlay its legacy of infrastructure expertise into a reassuring presence, particularly for veteran IT administrators struggling to balance their in-house infrastructures against the cost-savings and potential efficiencies of cloud computing.