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: Update-delete conflicts detected during synchronization can be resolved in favor of the update or the deletion. Resolving the conflict in favor of the deletion results in the entity deleted on one replica being deleted on all selected replicas. Resolving the conflict in favor of the update results in the updated entity, which includes an entity moved from one hierarchy to another, being replicated on all selected replicas. To resolve the conflict in favor of the update, the deletion is treated as though it were reported erroneously. The deleted entity is resurrected in the form of the updated entity. Change version information is maintained in all replicas. Update-delete conflicts are resolvable in accordance with various resolution policies such as the update wins, deletion wins, changes occurring on a particular device wins, and most recent event wins, for example.

Abstract: Disclosed are systems and methods pertaining to data synchronization and move handling support. In particular, a move log is maintained that identifies data that has moved in, out, and within a synchronization scope. Furthermore, the log comprises times associated with when data moves in and out of the synchronization scope. Systems and methods can interact easily with the generated and updated move log to facilitate determining data versions and identifying new data that may need to be synchronized.

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.

Abstract: Systems and methods that mitigate errors in positioning systems, by employing signal strength(s) of signal sources (e.g., towers adjacent to a mobile unit.) Such mitigation system verifies whether the mobile unit receiving GPS data is in static position (e.g., not moving) or is moving (e.g., dynamic position), and evaluates accuracy of the GPS reporting (e.g., discarding GPS data in static position and trusting GPS data in dynamic position.

Abstract: Several embodiments of the present invention employ synchronization adapters for synchronizing information between “WinFS” and non-“WinFS” data sources. Examples of adapters include an adapter that synchronizes address book information between a “WinFS” contacts folder and a non-WinFS mailbox. In these instances, adapter developers might use the “WinFS” synchronization core services API described herein for accessing services provided by the “WinFS” synchronization platform in order to develop schema transformation code between the “WinFS” schema and the non-“WinFS” data source schema. Additionally, the adapter developer provides protocol support for communicating changes with the non-“WinFS” data source. A synchronization adapter is invoked and controlled by using the synchronization controller API and reports progress and errors using this API.

Abstract: A system and method for synchronizing a database having metadata and raw data. Metadata may be fully synchronized between two systems, with copies stored on both systems. Raw data may be selectively synchronized, so that a client system need not store all of the raw data locally. When disconnected, the client system may identify certain portions of the raw data to store locally, and such data may be synchronized when reconnected to a server system.

Abstract: A method of synchronizing data between multiple endpoints each storing a copy of the data in accordance with different underlying schemas. An application model that provides a logical representation of an underlying schema is extended with a synchronization model that provides a logical representation of changes made to the data. The synchronization model comprises functions that provide synchronization information on the changes in a common format. Using such synchronization information, changes in a copy of the data stored in a first underlying schema on a first endpoints are applied to another copy of the data stored in a second underlying schema on a second endpoint in synchronization relationship with the first endpoint.

Abstract: Systems and methods that enable removal of data from an endpoint, while not propagating such removal to other endpoints when synchronizing data sources associated therewith. A designation component can indicate items as forgotten items, wherein such items are being known to an endpoint and deleted therefrom—yet, reintroduced therein and reappearing (e.g., as a create) upon re-synchronizing with the replica over again. Moreover, the forgotten items can employ additional metadata such as in from of an additional bit that indicates whether an item is a forgotten item.

Abstract: The claimed subject matter provides a system and/or a method that facilitates managing data consistency in connection with a plurality of devices. A collection of devices can be associated with a user. A web service can receive a portion of data from at least one device via an interface component, wherein the web service can host and relate the portion of data with an account for the user. A master sync component can leverage a computing resource from at least one device in order to maintain data consistency between at least one of the following: two or more devices within the collection of devices associated with the user; or the account hosted by the web service and two or more devices within the collection of devices associated with the user.

Abstract: A template creator creates a template class that stores at least one template parameter. The template creator also specifies at least one additional object to be created when an instance of the template class is created. A template user initiates the creation of a new instance of the template class. If an error occurs during the creation of the new instance of the template class, the template user receives a report identifying the error.

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: 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. For instance, a user can opt into a mesh network and leverage services available via the mesh network. The user can also contribute to knowledge within the mesh network by allowing for information related to the user to be aggregated and employed by others, e.g., targeted provisioning of services. The interaction with the mesh network can occur passively (e.g., as a background application not generally visible to the user), or actively where for example the user can initiate collecting or logging of information from/to the mesh network.

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 associated with a POI with which a user interacts will wish to delay the interaction with the POI and associated content. For such scenarios, items discovered through direction-based location services can be designated for later interaction, e.g., according to pre-defined criteria that define explicitly or implicitly when the later interaction will occur. Device users are thus provided with relevant content about endpoints of direction based services at relevant times, which may not be the time of initial contact with the POI.

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: 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. Image data representing a subset of real space near a portable computing device can be displayed including a set of points of interest (POIs) for direction based service(s) within scope and automatically overlaying POI content on the image data relating to the POIs. In one embodiment, the display is included in an electronic device worn such that the display is substantially in front of an eye, e.g., a heads up display.

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 and gesture based input in a location based services environment, a variety of service(s) can be provided on top of user identification or interaction with specific object(s) of interest.

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: 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.