Abstract:
A messaging data structure for accessing data in an identity-centric manner. An identity may be a user, a group of users, or an organization. Instead of data being maintained on an application-by-application basis, the data associated with a particular identity is stored by one or more data services accessible by many applications. The data is stored in accordance with a schema that is recognized by a number of different applications and the data service. The messaging data structure includes fields that identify the target data object to be operated upon using an identity field, a schema field, and an instance identifier field. In addition, the desired operation is specified. Thus, the target data object is operated on in an identity-centric manner.
Abstract:
Processing a notification intended for delivery to multiple recipients associated with a broadcast list. Software executes within an alerts service environment to receive a notification addressed to a broadcast alias, determine a list of recipients associated with the broadcast alias to receive the notification, and broadcast the received notification to each recipient in the determined list.
Abstract:
A model for accessing data in an identity-centric manner. An identity (310) maybe a user, a group of users, or an organization. Instead of data being maintained on an application-by-application basis, the data associated with a particular identity is stored by one or more data services (511 through 518) accessible by many applications (320). The data is stored in accordance with a schema that is recognized by a number of different applications and hte data service (511 through 518). When a user is to perform an operatio on the identity's (310 data, the corresponding application (320) generates a message (531) that has a structure that is recognized by the data service (511 through 518). The message (531) represents a request to perform an operation on the data structure corresponding to the identity (310). The data service (511 through 518) receives and itnerprets the message. If authorized, the data service (511 through 518) then performs the operation.
Abstract:
A messaging data structure (700) for accessing data in an identity-centric manner, An identity may be a user, a group of users, or an organization. Instead of data being maintained on an application-by-application basis, the data associated with a particular identity is stored by one or more data services accessible by many applications. The data is stored in accordance with a schema that is recognized by number of different applications and the data service. The messaging data structure (700) includes fields that identify the target data object to be operated upon using an identity field (701), a schema field (703), and an instance identifier field (704). In addition, the desired operation (707) is specified. Thus, the target data objet is operated on in an identity-centric manner.
Abstract:
A model for accessing data in an identity-centric manner. An identity (310) maybe a user, a group of users, or an organization. Instead of data being maintained on an application-by-application basis, the data associated with a particular identity is stored by one or more data services (511 through 518) accessible by many applications (320). The data is stored in accordance with a schema that is recognized by a number of different applications and hte data service (511 through 518). When a user is to perform an operatio on the identity's (310 data, the corresponding application (320) generates a message (531) that has a structure that is recognized by the data service (511 through 518). The message (531) represents a request to perform an operation on the data structure corresponding to the identity (310). The data service (511 through 518) receives and itnerprets the message. If authorized, the data service (511 through 518) then performs the operation.
Abstract:
A messaging data structure (700) for accessing data in an identity-centric manner, An identity may be a user, a group of users, or an organization. Instead of data being maintained on an application-by-application basis, the data associated with a particular identity is stored by one or more data services accessible by many applications. The data is stored in accordance with a schema that is recognized by number of different applications and the data service. The messaging data structure (700) includes fields that identify the target data object to be operated upon using an identity field (701), a schema field (703), and an instance identifier field (704). In addition, the desired operation (707) is specified. Thus, the target data objet is operated on in an identity-centric manner.
Abstract:
Un procedimiento en una red de ordenadores, que comprende: recibir una notificación dirigida a un usuario desde una fuente de información (5021, 5022, 5023, .. , 502m) estando regularizada la notificación de acuerdo con un esquema de notificación (506), y determinar si el usuario debería recibir la notificación en base a las preferencias del usuario y los datos de contexto, y si es así, determinar un dispositivo de un conjunto de dispositivos de usuarios (5081, 5082, ... , 508n) para recibir la notificación y enviar la notificación al dispositivo; en el que los datos de preferencias comprenden datos de preferencia de la fuente regularizados de acuerdo con un esquema de preferencias de la fuente para acceder por la fuente de información, y los datos de preferencias principales regularizados de acuerdo con un esquema de preferencias principal para acceder por un agente de información donde se recibe la notificación, y que comprende además determinar en la fuente de información que el usuario debería recibir la notificación en base a los datos de preferencia de la fuente, y la modificación de los datos de la notificación en el agente de información en base a los datos de las preferencias principales antes de enviar la notificación al dispositivo.
Abstract:
A model for accessing data in an identity-centric manner. An identity may be a user, a group of users, or an organization. Instead of data being maintained on an application-by-application basis, the data associated with a particular identity is stored by one or more data services accessible by many applications. The data is stored in accordance with a schema that is recognized by a number of different applications and the data service. When a user is to perform an operation on the identity's data, the corresponding application generates a message that has a structure that is recognized by the data service. The message represents a request to perform an operation on the data structure corresponding to the identity. The data service receives and interprets the message. If authorized, the data service then performs the operation.
Abstract:
Directly operating on data structures in a generic manner regardless of the type of data structure being operated upon and without requiring dedicated executable code for manipulating data structures of the particular data type. A common set of commands (e.g -. insert, delete, replace, update, query) are recognized that may be used to operate on data structures (210, 220, 230, 240) of a number of different data types. A navigation module (250) accesses a request to execute one of the common command methods on at least an identified portion of an identified data structure (210, 220, 230, 240). Then, the navigation module (250) accesses a navigation assistance module (260) to access a set of rules associated with the particular data type, the set of rules allowing the navigation module (250) to find the portion of the data structure (210, 220, 230, 240) that is to be operated on. If appropriate, the command operation is then executed on the identified portion of the data structure (210, 220, 230, 240).
Abstract:
Authorizing a requesting entity to have a server perform a particular action in a manner that is at least partially independent of the underlying target data structure. An authorization station maintains a number of role templates (310) that each define basic access permissions with respect to a number of command methods. The authorization station also maintains a number of role definitions (350) that each define access permissions for specific requesting entities by using one or more of the role templates (310). When the authorization station receives a request from the requesting entity, the authorization station then identifies the appropriate role definition (350). Using this role definition (350), the authorization station determines access permissions for the requesting entity with respect to the requested action.