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.

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.

Abstract: A method may include: retrieving a particular blank universal form based on a universal form template, the particular blank universal form having a universal form identifier, and the particular blank universal form created by a universal form creator; providing the particular blank universal form to a universal form filler; receiving a verified form from a universal form filler, the verified form corresponding to the particular blank universal form; and providing the verified form to the universal form creator.

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.

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.

Abstract: A method may include: maintaining one or more attributes of a first user; maintaining a risk profile scheme configured by the first user, the risk profile scheme comprising a passive permission table indicating whether a second user has permission to the one or more attributes; allowing the first user to grant dynamic permissions to the second user to access the one or more attributes in accordance with the risk profile scheme; allowing the first user to perform content blobulation of the one or more attributes; and allowing the first user to perform content reblobulation of the one or more attributes in accordance with the risk profile scheme.

Abstract: Granting permissions for attributes in a distributed data store involves implementing a federated control system. The system can include dynamic permissions granted to content blobs. Acknowledgment of dynamic permissions facilitates identification of users that receive content to enable restoring data on a machine following data loss. Acceptance of dynamic permissions can further facilitate automatic updates to data, or providing content blobs in response to changes in user attributes.

Abstract: Creating an agency relationship among clients of a computer system with respect to personal privileged, or otherwise sensitive permissions and/or attributes, is described. The technique enables a querying client to obtain permission and/or attributes from a queried client, even if the queried client is unavailable.

Abstract: Granting permissions for attributes in a distributed data store involves implementing a federated control system. The system can include dynamic permissions granted to content blobs. Acknowledgment of dynamic permissions facilitates identification of users that receive content to enable restoring data on a machine following data loss. Acceptance of dynamic permissions can further facilitate automatic updates to data, or providing content blobs in response to changes in user attributes.

Abstract: Creating an agency relationship among clients of a computer system with respect to personal privileged, or otherwise sensitive permissions and/or attributes, is described. The technique enables a querying client to obtain permission and/or attributes from a queried client, even if the queried client is unavailable.

Abstract: A computer system and methods for creating an agency relationship among clients of a computer system with respect to personal privileged, or otherwise sensitive permissions and/or attributes, is described. The system and methods allow a querying client to obtain permission and/or attributes from a queried client, even if the queried client is unavailable.

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.

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.

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.

Abstract: A computer system and methods for creating an agency relationship among clients of a computer system with respect to personal privileged, or otherwise sensitive permissions and/or attributes, is described. The system and methods allow a querying client to obtain permission and/or attributes from a queried client, even if the queried client is unavailable.

Abstract: Methods and systems are described for controlling query access to attributes associated with subscribers of a system. Permission setting variables are provided to allow subscribers considerable control over query access to attributes associated with the subscribers. A subscriber may manipulate one or more permission setting variables to control aspects of the response a querying party may receive when a query matches attributes associated with the subscriber. Advantages of the invention include flexible management of query access to subscriber information.

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.

Abstract: Test circuitry is included in a PROM memory for detecting shorts between bit lines and word lines and shorts or leaks in a memory cell. The circuitry enables a selected positive voltage to be applied across all memory cells in the memory so that the existence of leaky memory cells or shorts in the memory can be detected during testing. The test circuitry has no appreciable effect on the memory during normal operation of the memory.

Abstract: Circuitry is provided for testing fusible link arrays for short circuits around the fusible links. Each link is electrically isolated and compared with a pair of reference fusible links to detect the presence or absence of a short circuit.

Abstract: The present invention combines in either a logical AND function of N logical input signals, where N is a selected positive integer greater than or equal to 1, and provides programmably, either a direct AND output signal or a NAND output signal. The invention accomplishes this using a minimum number of components in the data path, between the logical input leads and logical output leads. A minimum of components in the data path reduces the propagation delay introduced by the circuit. The invention accomplishes this by providing two AND gates connected to the same set of N logical input signals. The output signal of one AND gate is inverted by an inverter with an enable/disable input lead. The output signal of the other AND gate is inverted twice by two inverters. The second inverter has an enable/disable input lead. Means are provided for exclusively enabling one or the other of the two inverters with an enable/disable input lead.