Group items tagged

It's the document model! There is nothing wrong with RiA. Adobe is doing great stuff, and they fully support the WebKit flow document model in their RiA. Silverlight on the other hand is a true threat to the Open Web because it implements uniquely proprietary format, protocol and interface alternatives. The problem with AJAX is that it's difficult to scale. Advancing JavaScript libraries, structured WebKit, BrowserPlus and Google's GWT-Google Gears promise to tame that problem. At the end of the day though, i see AJAX as an important aspect of the browser as an RiA runtime engine. Here's what concerns me; 500 million MSOffice desktops that anchor most of the world's client/server business processes speak XAML "fixed/flow". These desktops are the information pumps for billions of business critical documents. And they do not speak the language of the Open Web. They speak the language of the Microsoft Web-Stack and Mesh services.

Connectivity The marketplace is very fragmented. To reach every device you have to target about 14 different platforms. Not every development team has the resources to build it for every platform. We believe over time the browser on mobile devices will be the entry point for many applications. But today the majority of mobile phones don’t have the browser that can do it. Android is an open source world class mobile stack. We hope the industry will adopt it. The WebKit browser comes with Android.

Although it appears that the mobile hardware providers are competing through the development of incompatible platforms, i think there's reason to be hopeful. There seems to be movement towards a universal web application model able to join legacy Web with an Open-Web future where devices, desktops, web-stacks, and clouds connect, access, exchange and collaborate with all kinds of information systems. Above the metal, at the web application layer, there is a war between competing runtime engines. The recent Web 2.0 Conference was a showcase for Sun Java FX, Adobe RiA, and Microsoft .NET Silverlight. The exhibitors floor featured a large and prominent Microsoft Silverlight-Mesh island surrounded by Flex RiA providers, with currents of IT and developers asking the same question; Can Adobe run with Microsoft?

On the surface SharePoint is merely a document management system which lets everyone in your company share and find Office documents easily. But critics like our own Matt Asay call it a Trojan Horse, which will bind companies which deploy it to Microsoft forever. You can put together everything SharePoint does using open source projects, but it takes work. You can combine Alfresco (from the Electronic Content Management (ECM) software company Matt works for), the Liferay portal, JasperSoft for reporting, and Zimbra’s e-mail server. Throw in some Jive forums and you’re more than done. But what does that cost, really, compared to just using something from Microsoft which already works with your current Office applications? Exactly. Once companies start using SharePoint, Asay worries, there is no way for them to ever ditch Microsoft applications and file formats. SharePoint is tied to those formats, and as the share fills the cost of switching away rises exponentially.

Some of the next generation collaboration platforms are succeeding precisely because they are silo bunker busters. The problem of dozens of digital filing cabinets full of thousands of iterations of hard to find documents within enterprise environments is arguably being solved by the new generation of nimble project contextual tools. Taxonomies and tagging, threaded discussion, wikis and other ‘Enterprise 2.0‘ tools are an alternative solution to the problem of generating mountains of hard to find silo’d information and associated email. Microsoft have a fabulously lucrative franchise with their Office suite of Word, PowerPoint, Excel et al desktop products. A huge issue in the enterprise space is blizzards of email containing links to documents created with these products on shared drives, or iterations actually attached to the mail messages. Add mobile users on laptops with intermittent connection and you also have serious synch headaches.

I agree with DonnieBoy. Microsoft will try to leverage their MSOffice monopoly to dominate the newly emerging marketplace of Web-Stack and Cloud Computing solutions. I also believe that for Microsoft, the final pieces of this puzzle fell into place on March 29th, 2008 with ISO approval of the MSOffice-OOXML document format.

"XML doesn't have the monopoly it used to have," Bray said. "It used to be that if you wanted to send messages back and forth across the wire, XML was the only game in town." "Clearly, there is going to more heterogeneity for wire formats, too," he added. "Increasingly, given that the future will have more than two programming languages, there will be a lot more messages being passed around."

Bray comes to the issue from a unique perspective. As a co-author of the original XML specifications, he helped create a language that at one point had been intended to become the lingua franca for all Web communications. He now admits that he wasn't entirely accurate in his original vision of where XML would end up.

"I was so completely wrong on everything," Bray admitted. "We thought we were going to replace HTML and that turned out to be a silly idea. It turned out be used for syndication feeds and purchase orders and a million other things, and that's fine. Things find their own level." However, in today's world of language proliferation, Bray has another favorite approach for exchanging information. "I am a strong partisan of the REST (define) approach, which provides a Web-based approach for integration of anything to anything," Bray said. "REST isn't tied to XML or JSON but it makes it easy to use either."

W3C today announced new standards that will make it easier for people to browse the Web on mobile devices. Mobile Web Best Practices 1.0, published as a W3C Recommendation, condenses the experience of many mobile Web stakeholders into practical advice on creating mobile-friendly content.

Until today, content developers faced an additional challenge: a variety of mobile markup languages to choose from. With the publication of the XHTML Basic 1.1 Recommendation today, the preferred format specification of the Best Practices, there is now a full convergence in mobile markup languages, including those developed by the Open Mobile Alliance (OMA). The W3C mobileOK checker (beta), when used with the familiar W3C validator, helps developers test mobile-friendly Web content.

W3C is also developing resources to help authors understand how to create content that is both mobile-friendly and accessible to people with disabilities. A draft of Relationship between Mobile Web Best Practices (MWBP) and Web Content Accessibility Guidelines (WCAG) is jointly published by the The Mobile Web Best Practices Working Group and WAI's Education & Outreach Working Group (EOWG).

Microsoft is incubating a componentized non-Windows operating system known as Midori, which is being architected from the ground up to tackle challenges that Redmond has determined cannot be met by simply evolving its existing technology.SD Times has viewed internal Microsoft documents that outline Midori’s proposed design, which is Internet-centric and predicated on the prevalence of connected systems.

The Midori documents foresee applications running across a multitude of topologies, ranging from client-server and multi-tier deployments to peer-to-peer at the edge, and in the cloud data center. Those topologies form a heterogeneous mesh where capabilities can exist at separate places.

The newly-renamed project is being expanded with workflow capabilities that Novell hopes will expand business usage. The Kablink project is Novell's effort to grow the market for open source collaboration solutions, and chip away at the hold that Microsoft's Sharepoint commands among small business users.

"We have a system inside of Kablink that allows developers to create business objects and these business objects model data," McConnell explained. "Then with the model of the data you can pass it views for forms and displaying the business model. So you can model a business object and then add collaboration items for that object." With the Kablink release, workflow capability is being added to the ICEcore collaboration features. A business user can now create a business workflow for a process -- be it approval, development or otherwise and attach that workflow to the business objects.

"We think our offering is unique; there are point solutions that have workflow embedded in them but the kind of social networking collaboration that we do, I don't know anyone that has a workflow component that can do the things that we can," McConnell claimed. "There are customers that have designed ISO 9000 processes with this, so it's a nifty thing to have, especially in an open source project."

According to Ts'o, the difference between organic and non-organic is related to how much influence a single corporation has in the development of an open source product. The broader the developer community around a project and the lower the barrier to contributing, the more organic it is. Citing Linux, Apache, Mozilla, and Eclipse among those in the organic open source camp, Ts'o singled out OpenSolaris as a prime example of non-organic open source. In fact, he objected to "Sun claiming that Solaris is just like Linux because it's open source"--a characterization that seemed to inspire his interest in asserting these definitions.

But it’s not all roses on the SharePoint front — especially when it comes to the growing trend by customers to use SharePoint not just as a set of loosely integrated applications, but as a development platform in its own right. A couple of new studies highlight the potential risks of which customers should be aware when betting big on SharePoint.

WSO2 is releasing on Monday WSO Mashup Server Version 1.5, an open-source product for deploying mashup services featuring Google Gadgets support and interfaces to relational databases and other data sources.

The mashup server uses JavaScript to describe logic for acquiring information, combining data, and exposing it to a user. Information can be acquired from sources such as Web services and scraped pages and published as a new Web service, feeds, Web pages, or notifications. Version 1.5 features stubs and templates for Google Gadgets, which can be hosted within Mashup Server or externally such as in an iGoogle page. A beta dashboard add-in is featured for hosting Google Gadgets within Mashup Server. Google Gadgets enable dynamic content to be placed on a Web page. Data services enhancements provide Web services interfaces to relational databases and other data sources such as Excel spreadsheets and comma-separated values.

A second survey showed that basic PC and network hardware, as well as professional services providers, would bear the largest proportion of spending cuts. It also showed that CIOs planned to emphasize economizing measures over investments in new technologies, with cloud computing emerging as the last item on their priority lists, despite the hype around it.

The CIOs indicated that server virtualization and server consolidation are their No. 1 and No. 2 priorities. Following these two are cost-cutting, application integration, and data center consolidation. At the bottom of the list of IT priorities are grid computing, open-source software, content management and cloud computing (called on-demand/utility computing in the survey) -- less than 2% of the respondents said cloud computing was a priority.

Gundotra said Google “believes in the vision of software as a service.” But the barrier to enabling enterprises to use cloud computing on an even greater scale is that the browsers have to become more powerful to have the full client computing capability of the PC platform. He noted that this is already starting to happen. Google, he said, is “thrilled” with the new features built into the Mozilla Firefox 3.0 browsers. Google said this is a sign that the next generation of browsers, including Internet Explorer, “will have very significant improvements” that will give the features they need for cloud computing.

Apple’s Trojan horse in multi-platform, multimedia runtime is a piece of open source technology that’s already on Windows, Mac OS X, Linux, Adobe Flex/AIR, iPhone, iPod touch, Nokia S60 smartphones and Google’s new Android/Open Handset Alliance, with 30+ partners around the globe: WebKit 3.0.

- publishers of Flash apps have to port their apps to native Web apps if they want to run inside a Web browser going forward because the Web has moved off the PC, you can’t accessorize it with PC software anymore, WebKit is so small and light and cross-platform that it is the plug-in now, inside iPhone, iPod, Nokia, Android, iTunes and other Mac and Windows apps - publishers of Flash video have to deploy MPEG-4 H.264/AAC if they want to run inside an audio-video player (on any device) going forward, the decoder chips for this are already in EVERYTHING, from iPod to Blu-Ray to NVIDIA GPU’s Most of the world has already done both of the above, including Google and Apple. This is not the beginning of the end for Flash, it is the end of the end.

Notice he doesn’t say at all that Flash is running natively on the ARM CPU inside the iPhone. And once again, as I point out in the article above, technical problems may be solved by Adobe, but cross-platform runtime compatibility and multi-touch UI frameworks remain as serious impediments.

the direction Apple is taking in WebKit with canvas, downloadable fonts, SVG, CSS animation, CSS transformations, faster JavaScript, HTML5 audio/video embedding, exposure of multi-touch to JS and so on is precisely to create an open source alternative to the Flash runtime engine, without having to download a proprietary plugin:

What sort of cloud computer(s) should we be building or expecting from vendors? Are there issues of lock-in that should concern customers of either SaaS clouds or PaaS clouds? I’ve been thinking about this problem as the CEO of a PaaS cloud computing company for some time. Clouds should be open. They shouldn’t be proprietary. More broadly, I believe no vendor currently does everything that’s required to serve customers well. What’s required for such a cloud? I think an ideal PaaS cloud would have the following nine features:

1. Virtualization Layer Network Stability

2. API for Creation, Deletion, Cloning of Instances