The two-year-old SyncML protocol for synchronising data between servers and PCs, handhelds or mobile phones is now bearing fruit, with the release of enterprise middleware products supporting the SyncML standard. These first products support only a subset of SyncML, and will not displace proprietary tools overnight. However, the proprietary tools and SyncML tools should be able to co-operate in the future, synchronising different data types to the same mobile devices.

Based on the Extensible Markup Language (XML) standard, SyncML defines a set of data types that any compliant product must support, and also defines how that information is exchanged between devices. However, software developers remain free to add features of their own, such as security, file or ODBC database synchronisation, and mobile device management.

"SyncML defines five data types - contacts, calendar items, tasks, memos and email," explained Andre Sant'Anna, chief technology officer at synchronisation specialist Pumatech. "It has a device management sub-protocol called SyncML-DM, which is not released yet, but some firms, including ours, have already demonstrated device management at the Amsterdam SyncFest."

Pumatech's Enterprise Intellisync software currently uses proprietary technology to synchronise personal information manager (PIM), email and database information among desktops, servers and mobile devices.

The SyncML Initiative group carries out so-called SyncFests to test the compatibility of proposed SyncML products. Thierry Bonfante, product manager for wireless, synchronisation and Web products at software maker Steltor, said, "When you develop a SyncML product, you ask the SyncML Initiative group for certification. You go in with your software and it has to work against at least two other compliant products." In practice, however, a product such as Steltor's SyncServer will probably to be verified against 10 or more products.

Requirements for extra services and functionality will ensure that there is still a need for proprietary synchronisation tools, according to David Hofacker, UK manager for Extended Systems. His firm's XtndConnect products all support SyncML as well as proprietary protocols. It therefore seems likely that synchronisation tools will offer SyncML services to standard clients and extended services to those with matching proprietary client software.

However, a device can run multiple clients simultaneously for synchronisation with different corporate applications. This is already happening, according to Hofacker. "British Airways uses PDAs with our XtndConnect for Lotus Notes data, plus AvantGo to synchronise Web content," he said.

Firms such as Extended Systems are supporting SyncML and are helping to define the specification to reduce their development burden, while extending the range of devices that their software can talk to.

"If I provide a [SyncML compliant] server, I don't have to worry about providing a client, because it's a standard item," Hofacker said. "As a middleware supplier that's great for me - if I have a standard to develop to it makes my job much easier."

It also makes it possible to envisage a mesh of related servers, exchanging data with each other and providing any SyncML client with transparent access to a wide range of corporate services and data.

"It will be a server business - the strategic component of SyncML is the ability for the back-end systems to talk to each other," commented Steltor's Bonfante. "Nobody can provide a comprehensive synchronisation solution today, but SyncML will eventually allow the servers to connect and each would fill in a different part of the puzzle."

Have your say: contact IT Week