Is there any one who is aware of and would like to discuss what is SyncML, what can it do for you and how can you take advantage of it?

If you inspect your phone, you might notice SyncML being one of it's features.

What's that?

According to Symbian's definition, SyncML (Synchronization Markup Language) is a data synchronization protocol optimized for wireless networks. The protocol rides on common transport such as http.

What can it do?

That would translate to enabling one with a SyncML compliance phone to conduct on-demand Remote Over-The-Air data synchronization over GPRS connections, etc, for data such as addressbook, calendar, to-do-list, etc without the need for attaching cables to or in proximity within fixed location PC/laptop each time you want to do so. You can be on the go anytime anywhere wirelessly.

Imagine what can this extended mobility, accessibility and convenience do for you and your mobile data, at work and at play?

The SyncML consortium was initially set up by IBM, Nokia and Psion. Several companies and phone makers had joined since, including Sony Ericsson, Motorola, Siemens, Vodafone, etc. Effort to standardize the protocol industry-wide is being consolidated at Open Mobile Alliance (OMA) http://www.openmobilealliance.org Current spec is v1.1.

We had seen SyncML becoming a native component in handsets and other devices ...

As such, though some current or earlier phones indicated having the SyncML feature, they might not be compliance to current industry standard OMA's specs for speaking correct SyncML on the protocol level.

For example, when initializing with the server, some phone-side SyncML implementations might not recognize the returned <Chal> tag or status [407] (ie. credentials missing) when being challenged by server to send authentication info during initialization stage, thereby causing an erroneous experience to users attempting to remote sync. Without sending authentication info to server enclosed within the <Cred> tag during the protocol handshake, the initialization phase could possibly fail during a sync attempt. In this case, the server expects but does not see the phone side responding any further with credential info to complete the initialization phase after asking for it with the <Chal> tag and [407] status returned earlier.

However, a majority of existing handsets are observed to be fine, eg. the Nokia series 60 and Sony Ericsson such as, but not limited to, 7610, 6680/1, 6600, SE K700i, SE K508i, etc ... speaking SyncML correctly based on OMA specs.

OMA SyncML compliance is expected to proliferate in current and future devices. Check out if your's has one in it for you to take advantage of ...