Abstract: Various embodiments of the present invention are directed to synchronization utilizing one or more optimizations through the utilization of metadata. For several embodiments of the present invention, one method for optimizing synchronization is to reduce the overhead required for said synchronization by having each peer only tracking changes for itself and other peers within its change community (or communities) (a.k.a., “Intra-Community-Only Change Tracking Optimization”). For certain embodiments of the present invention, another method for optimizing synchronization is to not create synchronization overhead until required. For numerous embodiments of the present invention, yet another method for optimizing synchronization is to minimize redundant use of a partner's unique global ID—a large and cumbersome number—and to instead maintain a table that cross-references each partner (and its unique global ID) with a smaller and much less cumbersome partner key.

Abstract: Architecture for restoring nodes. After restoring a node, fix-up occurs to make the node appears as a different node than before the restore operation. The node appears as a new node, which new node knows the data up to a certain point from when the new node had the prior identity. This allows for new changes generated by the new node to flow to the other nodes in the topology, as well as have the changes that the prior identity sent to other nodes flow back to the new node. In other words, the architecture maintains information to create the new node in the topology while maintaining prior data knowledge. Additionally, item level metadata of associated data items is updated to correlate with the updated data items so that changes can be correctly enumerated and applied. This metadata update occurs across scopes of which the data items are included.

Abstract: Architecture that eliminates the need for on-disk full backups of data retaining only changes that have occurred, in a separate table. Thus, the architecture provides for incremental recovery of incremental changes in a relational database (e.g., SQL). The architecture provides improved recovery time and recovery point objectives. By using the incremental capture of changed data (e.g., in an XML format), the capability is provided to capture schema changes, query the incremental change data and efficiently restore user data to an earlier point-in-time state. Changes (e.g., insert, update and delete operations) are tracked (e.g., continuously) by a set of triggers and the incrementally captured changed rows are inserted in a data capture table (a differential change “delta” table) in a human-readable format (e.g., XML). Rollback is also provided.

Abstract: The subject disclosure relates to cross scope synchronization among different sets of nodes that synchronize the same data item(s) according to different synchronization scopes. In one aspect, create and update versions are defined for a scope in which a data item was created and updated, respectively, and create and update versions are defined for a local node shared for different groups of nodes synchronizing according to the different synchronization scopes (e.g., a server node).

Abstract: Tombstones can be removed from a data store without data corruption. Tombstones placed into a forgotten knowledge list can be compared against each other and/or items in a tombstone table, and deleted when tombstones representing subsequently deleted items are extant. Also, creation database version information can be kept along with database items, and databases can record database version information when they synchronize. If a synchronizing database discovers an item that it does not have, but the creation database version information associated with the item reflects that the synchronizing database “should” have the item, then it can be inferred that the item was subsequently deleted, and item resurrection can be prevented.

Abstract: Techniques are described herein for pricing access to data using contribution analysis. A user may issue a query to a store that stores data. The store may analyze a subset of the data to determine a result that is to be provided to the user in response to the query. The subset is referred to as contribution data. A data access price calculator performs a contribution analysis to determine a price to be charged to the user to access the result. The contribution analysis takes into consideration a number of rows and/or columns of data in the contribution data, a number of rows and/or columns of data in the result, functions used during the store's analysis of the contribution data, or a combination thereof. The data access price calculator may derive such information from an indicator that is received from the store and/or to some extent from the result itself.

Abstract: The claimed subject matter provides a system and/or a method that facilitates synchronizing data within a data storage system. An interface component can leverage a synchronization technique within the data storage system. A sync component can provide a secure peer to peer data synchronization based at least in part upon the synchronization technique to allow a tiered access to the synchronized data.

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: The subject disclosure provides a device, computer readable storage medium, and method for converting gestures undergone by a device into digital graffiti. The disclosure includes ascertaining an orientation of the device and a path traversed by the device. Gestures undergone by the device are identified as a function of the orientation and the path. Digital graffiti corresponding to the gestures are then superimposed onto a digital canvas.

Abstract: The subject specification provides a system, method, and computer readable storage medium directed towards allocating digital canvasses for digital graffiti. The specification discloses receiving data corresponding to digital graffiti formed from a gesture undergone by a device. The specification also discloses identifying a digital canvas corresponding to the digital graffiti as a function of the received data.

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. Items discovered through direction-based location services can be designated for present or later interaction, with information about those interactions uploaded to intelligent portal services exposed via one or more networks. Device users can interact with the portal services at a later time after an intelligent analysis has been applied to data representing the user's interactions, enabling a variety of scenarios, such as recommendation engines, sharing engines, shopping scenarios, etc. via the portal services.

Abstract: Described is a technology by which a mobile device outputs an alert for a reminder based upon a current location of the mobile device with respect to an entity (person, place or thing) associated with the reminder. The reminders may be maintained and provided by a service. Each reminder includes a reference to target-related information. When the device moves to within a threshold proximity of the target, and other criteria (e.g., time of day) is satisfied, an alert is output by the device. A user may gesture with a device towards an entity to set a reminder associated with that entity, or to get any reminder associated with that entity. A device may also get reminders by scanning or image processing, e.g., by reading a barcode associated with a product to get any reminders associated with that product.

Abstract: Aspects of the subject matter described herein relate to initializing a database to be used for synchronization. In aspects, a peer in a synchronization topology creates a consistent copy of its database. Metadata associated with this copy is marked to distinguish changes made before the copy was created from changes made after the copy was created and also that the copy needs to be prepared before being used in synchronization. Any client may then download the copy and start immediately reading and modifying its downloaded copy. Before the client synchronizes its copy with other databases already in the synchronization topology, the downloaded copy is prepared for use in the topology using the markers.

Abstract: Systems and methods that track changes in a database via a change tracking layer that enables separation of change tracking and change enumeration. Such an arrangement enables multiple change enumeration and sync technologies over a single change tracking layer, while reducing amount of tracking information that are maintained.

Abstract: Conflicts detected during synchronization of replicas are enumerated and resolved according to a specified policy, comprising conditions and actions or simply a specified action. Specified actions may be drawn from a set of standard actions and custom actions may also be composed. The conflicts are enumerated and resolved in logical groups. A logical group is a collection of one or more item envelopes, each comprising entities, such as items, links, and/or extensions. In an example configuration, both constraint-based conflicts, such as a name collision, and non-constraint-based conflicts are handled via the same application programming interface.

Abstract: Embodiments define a set of rules such that a type designer can express as part of a type's definition whether the type has extended the logic and/or constraints of its ancestral types in such a way that applications written against that ancestral type will continue to function correctly. Nonconformity can also be indicated and an embodiment can enforce limitations on a set of operations that can be performed on such instances when treated as their ancestral types. Applications can use standard interfaces to discover from embodiments whether such limitations can be in force for a particular instance and provide a user experience that accounts for those limitations. Embodiments can also provide mechanisms to enable type designers to limit a degree of extensibility for both types and/or Items.

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, when a user points at a particular item at a particular location or place, this creates an opportunity, e.g., an advertising opportunity, for anyone having an interest in that particular item to communicate with the user regarding that item or related items at a point in time when the user's focus is on the particular item. User context for the interaction can also be taken into account to supplement the provision of one or more interactive direction based services.

Abstract: The subject invention pertains to systems and methods of data item synchronization. More specifically, the invention concerns synchronization of data entities utilizing an intermediary or shared storage system and associated data store. Each client sync device can include or be associated with an interface that facilitates communication between client synchronization devices and the intermediary storage system. The interface can send change information to the shared store utilizing change data packets including a data change attribute, a prerequisite knowledge attribute and a learned knowledge attribute. The data change attribute can specify changes to be made to certain data, while the attribute can include a complete copy or reference to a complete copy or single instance of data.

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: The subject invention pertains to data synchronization across replicas. Disclosed are systems and methods of detecting and handling constraint-based conflicts that occur during a synchronization session. In accordance with one particular aspect of the invention, name-constraint violations can be detected. These violations can be resolved by generating a single merged identity that can be utilized to refer to data units, for example on different replicas that had the same name. A property of the merged identity can be merge history, which specifies the identifiers subsumed by the merge.