DISTRIBUTED MANAGEMENT FRAMEWORK FOR PERSONAL ATTRIBUTES
First Claim
1. A system comprising:
- a first client that includes;
a first attribute data store;
one or more first destination stores;
an engine for identifying attribute updates to the first data store, for generating a permissions-based transaction including the data associated with the updates, and for transmitting the updated data associated with the permissions-based transaction;
a second client that includes;
a second attribute data store;
one or more second destination stores;
an engine for identifying permissions-based updates to the first data store, generating a transaction including the data associated with the permissions-based updates, and for transmitting the data associated with the permissions-based updates;
a server, coupled to the first client and the second client, that includes;
a module that receives attribute data from the first client;
a permissions database where first permissions associated with the first client are set at the individual attribute level for the second client;
an engine for updating the permissions database and for validating the first permissions for the second client;
an engine for distributing first client updates based on validated permissions to destinations associated with the one or more second destination stores.
1 Assignment
0 Petitions
Accused Products
Abstract
A technique for distributed management of attributes includes propagating attributes based upon attribute-granularity permissions. An example of a system according to the technique may include a server, coupled to a first client and a second client, that includes a module that receives attribute data from the first client; a permissions database where first permissions associated with the first client are set at the individual attribute level for the second client; an engine for updating the permissions database and for validating the first permissions for the second client; and an engine for distributing first client updates based on validated permissions to destinations associated with the one or more second destination stores.
-
Citations
11 Claims
-
1. A system comprising:
-
a first client that includes; a first attribute data store; one or more first destination stores; an engine for identifying attribute updates to the first data store, for generating a permissions-based transaction including the data associated with the updates, and for transmitting the updated data associated with the permissions-based transaction; a second client that includes; a second attribute data store; one or more second destination stores; an engine for identifying permissions-based updates to the first data store, generating a transaction including the data associated with the permissions-based updates, and for transmitting the data associated with the permissions-based updates; a server, coupled to the first client and the second client, that includes; a module that receives attribute data from the first client; a permissions database where first permissions associated with the first client are set at the individual attribute level for the second client; an engine for updating the permissions database and for validating the first permissions for the second client; an engine for distributing first client updates based on validated permissions to destinations associated with the one or more second destination stores. - View Dependent Claims (2, 3, 4, 5, 6, 7, 8, 9, 10, 11)
-
Specification