Abstract: A Web service synchronization protocol is provided that sets forth the metadata and messaging by which endpoints roam, share and synchronize common information with one another in a multi-master networked computing ecosystem. A general SOAP-based protocol is defined for synchronizing data between two endpoints where one or more of the endpoints supports a Web service. Defining messaging for knowledge-based transfers using XML Web services, the protocol allows devices, services and applications to synchronize through firewalls, allows for flexibility by allowing any common set or subset of information across endpoints and allows for extensibility by not prescribing the schema of the actual data being synchronized at the endpoints.

Abstract: A Web service synchronization protocol is provided that sets forth the metadata and messaging by which endpoints roam, share and synchronize common information with one another in a multi-master networked computing ecosystem. A general SOAP-based protocol is defined for synchronizing data between two endpoints where one or more of the endpoints supports a Web service. Defining messaging for knowledge-based transfers using XML Web services, the protocol allows devices, services and applications to synchronize through firewalls, allows for flexibility by allowing any common set or subset of information across endpoints and allows for extensibility by not prescribing the schema of the actual data being synchronized at the endpoints.

Abstract: A Web service synchronization protocol is provided that sets forth the metadata and messaging by which endpoints roam, share and synchronize common information with one another in a multi-master networked computing ecosystem. A general SOAP-based protocol is defined for synchronizing data between two endpoints where one or more of the endpoints supports a Web service. Defining messaging for knowledge-based transfers using XML Web services, the protocol allows devices, services and applications to synchronize through firewalls, allows for flexibility by allowing any common set or subset of information across endpoints and allows for extensibility by not prescribing the schema of the actual data being synchronized at the endpoints.

Abstract: An efficient way is provided to represent and exchange knowledge and/or partial knowledge across nodes when synchronizing between any two nodes. A first node sends a second node its knowledge and/or partial knowledge, including objects and versions of those objects. The second node compares its knowledge and/or partial knowledge with the knowledge and/or partial knowledge of the first node, and then sends the first node any latest versions of objects of which the first node is unaware. In addition, the second node sends its knowledge and/or partial knowledge to the first node. The first node then performs a similar object-by-object version comparison to determine any conflicts due to independent evolution of objects and any changes that should be sent to the second node in order to bring the objects of the second node up to date with the knowledge and/or partial knowledge of the first node.

Abstract: A Web service synchronization protocol is provided that sets forth the metadata and messaging by which endpoints roam, share and synchronize common information with one another in a multi-master networked computing ecosystem. A general SOAP-based protocol is defined for synchronizing data between two endpoints where one or more of the endpoints supports a Web service. Defining messaging for knowledge-based transfers using XML Web services, the protocol allows devices, services and applications to synchronize through firewalls, allows for flexibility by allowing any common set or subset of information across endpoints and allows for extensibility by not prescribing the schema of the actual data being synchronized at the endpoints.

Abstract: An efficient way is provided to represent and exchange knowledge and/or partial knowledge across nodes when synchronizing between any two nodes. A first node sends a second node its knowledge and/or partial knowledge, including objects and versions of those objects. The second node compares its knowledge and/or partial knowledge with the knowledge and/or partial knowledge of the first node, and then sends the first node any latest versions of objects of which the first node is unaware. In addition, the second node sends its knowledge and/or partial knowledge to the first node. The first node then performs a similar object-by-object version comparison to determine any conflicts due to independent evolution of objects and any changes that should be sent to the second node in order to bring the objects of the second node up to date with the knowledge and/or partial knowledge of the first node.

Abstract: An efficient way is provided to represent and exchange knowledge across nodes when synchronizing between any two nodes. A first node sends a second node its knowledge, including objects and versions of those objects. The second node compares its knowledge with the knowledge of the first node, and then sends the first node any latest versions of objects of which the first node is unaware. In addition, the second node sends its knowledge to the first node. The first node then performs a similar object-by-object version comparison to determine any conflicts due to independent evolution of objects and any changes that should be sent to the second node in order to bring the objects of the second node up to date with the knowledge of the first node.