Group items matching

in title, tags, annotations or url

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

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.

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.

Cloud computing will give rise to the 'power collaborator', who will "connect with people and find dispersed information across an organization and make it relevant," said speaking in Boston at the Enterprise 2.0 conference continuing through Thursday. The concept of cloud computing and Enterprise 2.0 Web-based applications and interactivity has apparently struck a positive chord with a fair number of businesses. Up to 69% cite collaboration as a key reason for the appeal of such environments, according to a survey released this week by AIIM, a non-profit group that tackles issues involving document management, content, records, and business processes. Other factors include: Improved agility and responsiveness (56%), faster communications (55%); increased innovation (39%); and a reduction in IT costs (36%).

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

It is the infrastructural paradigm shift that is sweeping across the Enterprise IT world, but how is it best defined? I refer of course to 'Cloud Computing' - the phenomenon that currently has as many definitions as there are squares on a chess-board. To try and narrow it down we bring here a round-up of some recent attempts to bring welcome precision where there risks being unnecessary vagueness. Enjoy!

This is Draft 2.0 of The Open Group's SOA ontology. This draft is being exposed for comment outside The Open Group prior to formal Open Group company review. Interested parties are invited to sent comments, and those comments will be addressed in the version submitted to formal review by The Open Group.

Google (NSDQ: GOOG) has obtained a broad patent for a data center in a container, which might put a kink in product plans for companies like Sun Microsystems (NSDQ: JAVA), Rackable Systems, and IBM (NYSE: IBM). The patent, granted Tuesday, covers "modular data centers with modular components that can implemented in numerous ways, including as a process, an apparatus, a system, a device, or a method."

The U.S. Patent Trademark Office site reveals patent number 7,278,273 as describing modules in intermodal shipping containers, or those that can be shipped by multiple carriers and systems. It also covers computing systems mounted within temperature-controlled containers, configured so they can ship easily, be factory built and deployed at data center sites.

If this sounds familiar, it might just be. Google's patent description resembles Sun Microsystems' data center in a box, called Project Blackbox. During its debut last year, Sun installed a Blackbox -- essentially a cargo container for 18-wheelers -- outside of Grand Central Station in New York City to show how easily one of their data centers could be installed. Google's patent description also has similarities to Rackable Systems' ICE Cube as well as IBM's Scalable Modular Data Center.

00 meters under the ground in Japan, Sun along with ten other IT firms are building a datacenter. The datacenter is located at such a low depth to take advantage of the cooler air as a means of bringing the 40% of energy usage, for cooling, down a few notches. The datacenter will also be reluctant to Japan’s earthquake potential by being built on the solid bedrock floor of the crater hollowed out for the project.

In the underground pictures it is clear that the Sun Modular Datacenter 20 is going to be a successful format for the datacenter because it is self contained and there is an abundant resource of ground water in the cave for a cooling system. The data center will be used by government agencies, it will serve as a service center for IT clients, and it will be used by businesses.

The Sun MD 20 Sun is included the design of this datacenter. In the earthquake analysis, the prototype was placed on a large shake table in California, and put through a simulation of the Northridge earthquake of 1993. The results were very conclusive. The location of Japan’s underground datacenter is still undisclosed. More Information

For much of this decade, Web browsing has been dominated by Microsoft's Internet Explorer (IE), which at its height achieved market share numbers approaching 95%, with the result that Microsoft owned a de facto standard for the Web and held effective veto power over the future of HTML. During much of this period, Microsoft suspended development of IE, with the result that virtually no new features appeared within the world's dominant browser from 2001 to 2006. But while IE was sleeping, one of the biggest phenomena of the computer age happened: Ajax. Clever Web developers discovered gold in them there mountains. Using Ajax techniques, Web developers could create desktop-like rich user interfaces right in the browser. Not only that, Ajax was evolutionary. Ajax offered an incremental path from the industry's existing HTML-based infrastructure and know-how, allowing Web developers to add rich Ajax elements to an existing HTML page.

A companion community effort helping to accelerate the adoption of open standards is the Web Standards Project (http://www.webstandards.org), which is producing a set of "acid tests" that verify browser support for Open Web technologies, such as HTML, CSS and JavaScript. Acid2 is focused mainly on CSS support, and is now supported by Opera, Safari/WebKit, and IE. Acid3 (http://www.webstandards.org/action/acid3) tests DOM scripting, CSS rendering,

Runtime Advocacy Task Force

Service orientation addresses these challenges by centering on rapidly evolving XML and Web services standards that are revolutionizing how developers compose systems and integrate them over distributed networks. No longer are developers forced to make do with rigid and proprietary languages and object models that used to be the norm before service orientation came into play. The emergence of this new methodology is helping to develop new approaches specifically for Web-based distributed computing. This revolution is transforming the business by integrating disparate systems to establish a real-time enterprise. Making information available where it is needed to simplify merchandising processes requires a methodology that is based on loosely coupled integration between various in-store and back-end applications. This demand makes it critical for an architecture that is based on service orientation for integration between disparate applications. In addition, surfacing information at the right place requires the ability to compose dynamic applications using an array of underlying services. The Office Business Applications platform provides this ability to create composite applications, such as dashboards for the store, regional, and corporate managers.