Abstract: Direction based pointing services are enabled for a portable electronic device including a positional component for receiving positional information as a function of a location of the portable electronic device, a directional component that outputs direction information as a function of an orientation of the portable electronic device and a location based engine that processes the positional information and the direction information to determine points of interest relative to the portable electronic device as a function of at least the positional information and the direction information. A set of scenarios with respect to movable endpoints of interest in the system emerge.

Abstract: With the addition of directional information in the environment, a variety of service(s) can be provided on top of user identification or interaction with specific object(s) of interest by pointing at the objects. Sometimes either the device user and/or the publishers of content cannot complete a content exchange associated with a point of interest (POI) fast enough for the content to remain relevant. Thus, POIs and content for POIs can be predicted for users based on a variety of factors, such as an analysis of their present path and directional changes, rates of changes, or other factors, such that there is no noticeable, or minimal, latency between information being available with respect to such POIs and a request made via the user's device for such POI information.

Abstract: Mobile endpoints are provided that enable direction based pointing services including a positional component for receiving positional information as a function of a location of the portable electronic device, a directional component that outputs direction information as a function of an orientation of the portable electronic device and a location based engine that processes the positional information and the direction information to determine a subset of points of interest relative to the portable electronic device as a function of at least the positional information and the direction information. Devices can include compass(es), e.g., magnetic or gyroscopic, to determine a direction and GPS systems for determining location. A component for determining acceleration can also optionally be included.

Abstract: A variety of flexible conflict resolution policies are provided for loosely coupled devices to implement according to a variety of different synchronization scenarios. Choosing a conflict resolution policy, such as “Most Frequent Updater,” “Priority,” “PerCent Change,” “Arbiter Deadlock Resolution,” etc., enables devices to select how and when to resolve such synchronization conflicts. In addition, with reference to a conflict log, a user or synchronizing application can roll back synchronization state to a time before a conflict may have arisen, so that the user or application can undo a resolution of a conflict and/or the user or application can apply an alternative conflict resolution policy moving forward from that time.

Abstract: The subject disclosure relates to synchronizing among network nodes in a multi-master synchronization environment that extend a knowledge based synchronization framework to include notions of object quality. In one embodiment, additional dimension(s) are placed on a knowledge vector for a given version of an object that represent quality information for the object, which is accounted for during the synchronization process to allow nodes to decide what types of qualities of objects should be conveyed to them as part of the synchronization process. Other embodiments include tombstoning objects to avoid future synchronization with respect to same objects maintained by other nodes in the multi-master synchronization environment. Advantageously, according to the synchronization framework, endpoints can synchronize data in a way that allows a definition and consideration of quality of one or more objects of the synchronized data for purposes of a knowledge exchange.

Abstract: The subject disclosure relates to synchronizing among network nodes in a multi-master synchronization environment where a knowledge based synchronization framework is extended to include notions of initiation and/or expiration of synchronized object(s). Advantageously, according to the synchronization framework, endpoints can synchronize data in a way that allows a definition of when one or more objects of the synchronized data should come into existence for purposes of a knowledge exchange and/or when one or more objects of the synchronized data should cease to exist for purposes of a knowledge exchange. In one embodiment, additional dimension(s) are placed on a knowledge vector for a given object that represent incremental lifetime information for the object, which is accounted for during the synchronization process to allow operations on the object by synchronizing applications or processes during its lifetime.

Abstract: The subject disclosure relates to an efficient multi-master synchronization infrastructure is provided enabling loosely coupled networked client and server devices, applications and services to efficiently convey and receive synchronization knowledge across interconnecting network(s). A set of synchronization methods and standardized interfaces are also provided that enable rich offline application experiences and collaboration among devices, applications and services predicated on the efficient synchronization infrastructure.

Abstract: Various embodiments are provided for synchronizing with multidimensional data in a knowledge based synchronization framework for a multi-master synchronization environment. Prediction can be employed to transmit the next versions of a sequence of subsets of multidimensional data to consuming clients in an intuitive manner for a given application. For example, applications that render 2-D images on the client of multidimensional objects (e.g., 3-D graphical objects) stored on a server are achieved through synchronizing versions of the 2-D images to the client including predictively pre-computing and/or providing versions of the 2-D images to the client as synchronization updates.

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: Systems and methods that disclose alternative patterns for exchange of synchronization data and/or metadata, e.g., ‘knowledge’, to enhance performance of synchronization processes are disclosed. Accordingly, the innovation discloses synchronization mechanisms that employ exchange of data and metadata to alleviate a requirement of a complete ‘round-trip’ when synchronizing data. ‘Knowledge’ can be provided which informs a provider of data changes, modifications, additions or deletions. The ‘knowledge’ can lower expense and/or increase efficiencies of the synchronization exchanges by enabling informed decision-making related to enumerating changes within the synchronization processes.

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 variety of flexible conflict resolution policies are provided for loosely coupled devices to implement according to a variety of different synchronization scenarios. Choosing a conflict resolution policy, such as “Most Frequent Updater,” “Priority,” “PerCent Change,” “Arbiter Deadlock Resolution,” etc., enables devices to select how and when to resolve such synchronization conflicts. In addition, with reference to a conflict log, a user or synchronizing application can roll back synchronization state to a time before a conflict may have arisen, so that the user or application can undo a resolution of a conflict and/or the user or application can apply an alternative conflict resolution policy moving forward from that time.

Abstract: A sync community may include a group of synchronization endpoints. When two synchronization endpoints of the sync community synchronize with one another, a synchronization data conflict may be detected when the two synchronization endpoints make a change to a same particular data item and the two synchronization endpoints were unaware of the changes to the same particular data item made by the other respective synchronization endpoint at the time the changes were made. Resolution of the detected synchronization data conflict may be delayed and data indicative of the detected synchronization data conflict may be propagated to other synchronization endpoints during a synchronization operation.

Abstract: Synchronization of a web syndication item over a Really Simple Syndication (RSS) format between a publisher and a subscriber. The publisher creates the web syndication item by including a media content associated therewith. The synchronization metadata is defined to include a first virtual clock value associated with the created web syndication item. The first virtual clock value indicates when the web syndication item was last updated. A request for subscribing the published web syndication item is received from the subscriber. In response to the received request, the published web syndication item is transmitted to a location remote from the publisher and accessible by the subscriber. The first virtual clock value is provided to the subscriber for use by the subscriber to modify the first virtual clock value when the subscriber modifies the media content associated with the web syndication item.

Abstract: DRM protected content is shared in a peer-to-peer device context. In various embodiments, systems are enabled for peer-to-peer digital rights management (DRM) content roaming via revocation and synchronization. Local license revocation and remote license creation can facilitate P2P DRM content roam using license share counts. Derivative share count licenses, or other derivative licenses, are generated on the target device, reducing the local license commensurately.

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.

Abstract: Systems and methods for orchestrating synchronizations between different targets in a synchronization community. The order and nature of synchronizations may depend on multiple factors, including the initiator of the synchronization, the data being synchronized, and other characteristics of the synchronization participants and synchronization community.

Abstract: Various technologies and techniques are disclosed that improve synchronization of data between varying types of devices and/or services. A full participant receives a request from another participant to perform a synchronization operation. The synchronization engine determines whether the device or service is a full, partial, or simple participant. The device or service is a simple participant if it has a data store for synchronized data and no knowledge store. The device or service is a partial participant if it has a data store for synchronized data and a knowledge store, but does not understand the knowledge. The device or service is a full participant type if it has a data store for synchronized data and a knowledge store and understands the knowledge. The synchronization engine performs the synchronization operation with the device or service using a set of logic that is appropriate for the type of device or service.