| Team-Fly | |
 | SyncML®: Synchronizing and Managing Your Mobile Data
By Uwe Hansmann, Riku Mettälä, Apratim Purakayastha, Peter Thompson, Phillipe Kahn
| | Table of Contents | | | Appendix B. Glossary |
- Access Control List
A table that indicates the access rights a user has for a particular system object.
- Asynchronous Request-Response Protocol
A message-exchange protocol between two computers where one party issues a request and another party optionally responds to the request, with the requesting party not waiting for the response. If the requesting party expects a response, it either checks for a response repeatedly or is alerted when a response is ready. A typical example of this protocol is SMTP.
- Authentication
The process of determining whether someone or something is, in fact, who or what it is declared to be.
- Database Transaction Processing
A sequence of information exchange and related work that is treated as a unit for the purposes of satisfying a request and for ensuring database integrity.
- Bootstrapping
The process by which the unconfigured mobile device is taken from the initial state to the minimally configured state.
- Certificates
A digital certificate is an electronic object that establishes credentials. It is issued by a certification authority. It contains a name, a serial number, expiration dates, a copy of the certificate holder's public key (used for encrypting messages and digital signatures), and the digital signature of the certificate-issuing authority so that a recipient can verify the certificate.
- Change Log
A data structure that stores the history of operations made to data items in a datastore. A timestamp may be stored along with each operation.
- Client Implementation
An implementation of SyncML that operates in the Client Role.
- Client Software
The software that implements the SyncML Client Role.
- Content Format
The format of the content, e.g. vCard or vCalendar.
- Data Synchronization
The process by which copies of data shared between two or more computers is kept consistent.
- Datastore
The storage location of data, e.g. a Database or a file.
- Database Transaction Processing
A sequence of information exchange and related work that is treated as a unit for the purpose of satisfying a request and for ensuring database integrity.
- Device Description Framework
SyncML DDF DTD used for describing data within the Management Tree.
- DM Client
A Client that implements the SyncML Device Management Protocol.
- DM Server
A Server that implements the SyncML Device Management Protocol.
- Field Mapping
The process of correlating fields (or columns) in a data record in the datastore of one computer with those in another computer.
- Footprint (Static)
The size of the object code or that of the interpreted bytecode for a program or a system.
- Footprint (Dynamic)
The overall memory required when code is executed. This is dependent on an actual execution instance.
- Identifier (ID) Mapping
The process of correlating identifiers of data items in the datastore of one computer with those in another computer.
- Integrity Violation
A condition where an operation on a data item contradicts certain constraints on the value of the data item. A typical example is updating some data value out of a prescribed range.
- Load Balancing
The process by which workload is equally (or close to equally) distributed among a set of computers.
- Local Synchronization
Data synchronization over a short-range (proximity-based) network connection such as a serial cable, infrared, or Bluetooth™. This type of synchronization typically occurs between a mobile device and a personal computer.
- Management Tree
The mechanism used by SyncML DM to access individual items on a DM Client.
- Management Object
The entities that can be manipulated by SyncML DM Servers.
- Many-to-one Synchronization
A synchronization topology that consists of a group of two or more entities, where there is only a single entity with which the other entities synchronize data. A typical example is a PDA and a laptop computer synchronizing with a desktop computer. This topology is also called the Star topology or the Central Master topology. Note that one-to-one synchronization is a special case of this topology.
- Many-to-many Synchronization
A synchronization topology that consists of a group of two or more entities, where any entity can synchronize data with any other entity. A typical example is a PDA, a laptop computer, and a desktop computer synchronizing with each other. This topology is also called the Peer-to-Peer topology. Note that Many-to-one and One-to-one topologies are special cases of this topology.
- Multiple-Path Synchronization
The context of many-to-one synchronization where all accesses to the central datastore do not pass through the synchronization Server.
- One-to-one Synchronization
A synchronization topology that consists strictly of a two-member group, where the members only synchronize data with each other. A typical example is a PDA that only synchronizes with a specific the personal computer and vice-versa. This topology is also called the dedicated-pair topology.
- One-way Synchronization
Data synchronization between two entities where only one entity informs the other about data updates.
- Remote Synchronization
Data synchronization over a longer-range (infrastructure-based) network connection such as a wireline/wireless local/wide area network. This type of synchronization typically occurs between a mobile device or a personal computer and a server.
- Server Alert
The process a Server sending an Alert or Trigger to a client.
- Service Provider
An entity that provides internet-enabled applications such as email, contacts, and calendar-management. Typically, the services are made available using a web server or a web portal.
- Servlet
A server-side Java™ application invoked by an HTTP server that handles requests from internet clients
- Single-Path Synchronization
The context of many-to-one synchronization where all accesses to the central datastore pass through the synchronization Server.
- Slow Synchronization
The process of synchronization where one entity exchanges the values of all items in a datastore with another entity. This is typically performed to recover from failures when it is not possible to determine the last common synchronization anchor between two entities.
- Synchronization Analysis
The process of analyzing changes made to data items by two synchronizing entities, detecting conflicts (changes made to the same data item by both entities), and possibly resolving conflicts.
- Synchronous Request-Response Protocol
A message-exchange protocol between two computers where one party issues a request and another party responds to the request, with the requesting party waiting until the response arrives. A typical example of this protocol is HTTP.
- Synchronization Vendor
A software vendor that specializes in developing software for synchronizing data between applications on different computers. Typically, synchronization vendors are not the original vendors of the applications.
- Sync Anchor
A marker associated with a datastore and one of its synchronizing partners, logically indicating the last instance of synchronization with that partner. The marker can be a timestamp or a logical counter.
- Sync Type
One of the supported synchronization scenarios. E.g. Two-way Sync, Slow Sync.
- SyncML Client (Client)
An implementation of the SyncML Data Synchronization Protocol, specifically implementing the Client Role.
- SyncML Component
One of the SyncML DTDs or Specifications.
- SyncML Entity (Client/Server)
A device that implements the SyncML specifications (in either a Client or Server Role or both).
- SyncML Framework
The Framework encompasses the Representation Protocol, the Synchronization Protocol, the Transport Binding and the SyncML Adapter. It does not include any Sync Agent(s), Sync Engine(s) or associated applications.
- SyncML Message
A Message is a a well-formed XML document that contains the SyncML Header and Body. SyncML Messages are used to communicate the necessary synchronization information.
- SyncML Package
A synchronization session consists of SyncML Packages being exchanged between a Client and a Server. A SyncML Package may be split into multiple SyncML Messages, if there are size constraints.
- SyncML Server (Server)
An implementation of the SyncML DS Protocol, specifically implementing the Server role.
- Timestamp
The actual time of an operation on a datastore on an individual data item or a group of data items. Many synchronization systems store the actual time of an operation along with the operation itself to select which updates are appropriate for a particular synchronization session.
- Two-way Synchronization
Data synchronization between two entities where the entities exchange information about data updates that occurred in each entity.
- Transcoding
The process of altering the format of data items to make them suitable for the characteristics of a mobile device.
- Transport Binding
The specification of how a higher-level protocol (e.g., a synchronization protocol) utilizes a specific transport protocol (e.g., HTTP). For example, in the context of SyncML® and HTTP, this entails specifying exactly how SyncML messages are encapsulated and transferred using the format and message-exchange sequence prescribed by HTTP.
- Uniform Resource Indicator (URI)
A uniform method of object location within the Internet. URLs (Universal Resouce Locator) and URNs (Universal Resouce Name) are special cases of URIs.
- Version Vector
An array of logical counters associated with a data item in a datastore, where the value of the ith counter indicates the version of the data item in the ith peer in a peer-to-peer synchronization topology.
|
| | Team-Fly | |
|
| |
