Unified Messaging Demands Open Standards
In a world where messages are sent to and from an almost limitless variety of communication devices, like iPods, Cell phones, Blackberry's (or NPD-berrys), and something currently in a lab, the need to retain messages for subsequent access and retrieval says that we must have a set of standards that define messaging formats. If not, we have to render the message differently each time it's requested or worse, store each message in a number of different formats.
Here's a scenario: An employee sends a video message using her cellphone to a colleague who reads it on a laptop in the departure lounge of the airport , but he then wants to see it again on his Blackberry while waiting in line at the car rental agency. We could go on with this forever. The point is that messages are no longer transiatory - they have a shelf-life of months or years and as a result cannot be confined by a specific sending or receiving technology. Organizations with unified messaging in their plans should pressure the industry to agree on messaging standards or face nightmarish storage management.
The old expression "the great thing about standards is that we have plenty of them" once again, applies. We have standards for Internet mail, SMS, instant messages (sort of), X.400/x.435 for specialty applications. And of course, pretty much every industry has its own set of message standards e.g., SWIFT for banking; AFTN for air traffic control, etc.
However, standards do exist that can be leveraged for this purpose. Standards like RFC 822 for Internet e-mail or XML document standards can, and are likely to, be used for message storage that is independent of device and delivery methods.
If you are looking for product information please go to http://www.northseasamt.com/