Abstract: Data may be stored by receiving the data to be stored, determining whether the data is regulated in a jurisdiction, and, responsive to the determination, selecting between a regulated storage scheme, requiring that the data be stored and/or processed in the jurisdiction in accordance with one or more laws pertaining to the jurisdiction, and an unregulated storage scheme, in which the data is not required to be stored in the jurisdiction and/or is not required to be stored in accordance with the one or more laws. Further, the regulated storage scheme may be followed by initiating storage of the data in the jurisdiction in accordance with the one or more laws.

Abstract: Data may be stored by receiving the data to be stored, determining whether the data is regulated in a jurisdiction, and, responsive to the determination, selecting between a regulated storage scheme, requiring that the data be stored and/or processed in the jurisdiction in accordance with one or more laws pertaining to the jurisdiction, and an unregulated storage scheme, in which the data is not required to be stored in the jurisdiction and/or is not required to be stored in accordance with the one or more laws. Further, the regulated storage scheme may be followed by initiating storage of the data in the jurisdiction in accordance with the one or more laws.

Abstract: Data may be stored by receiving the data to be stored, determining whether the data is regulated in a jurisdiction, and, responsive to the determination, selecting between a regulated storage scheme, requiring that the data be stored and/or processed in the jurisdiction in accordance with one or more laws pertaining to the jurisdiction, and an unregulated storage scheme, in which the data is not required to be stored in the jurisdiction and/or is not required to be stored in accordance with the one or more laws. Further, the regulated storage scheme may be followed by initiating storage of the data in the jurisdiction in accordance with the one or more laws.

Abstract: A monitoring module interfaces with existing non-retrospective data storage systems, thus providing mechanisms for detecting and reporting changes in data values stored in such systems. The monitoring module acts as a change detection layer that can operate in connection with multiple disparate systems and/or locations, so as to provide users with a unified view into data stored in such systems. For example, a user can consult a single app, website, or software application, to view changes for data values stored in multiple disparate systems and/or locations; the app can be configured to automatically generate notifications and alerts to users, and can provide the ability to respond to such notifications and alerts, take actions, and/or dive deeper into underlying data.

Abstract: According to various embodiments, a consolidated identity system and method are implemented to provide improved identity management and resource access management, particularly in the context of an enterprise system that requires a tight trust model. In at least one embodiment, the described system and method provide mechanisms for mapping identities among resources. The system and method are able to extract information relevant to a particular entity, such as an employee or user, and to consolidate and/or personalize such information as needed.

Abstract: A monitoring module interfaces with existing non-retrospective data storage systems, thus providing mechanisms for detecting and reporting changes in data values stored in such systems. The monitoring module acts as a change detection layer that can operate in connection with multiple disparate systems and/or locations, so as to provide users with a unified view into data stored in such systems. For example, a user can consult a single app, website, or software application, to view changes for data values stored in multiple disparate systems and/or locations; the app can be configured to automatically generate notifications and alerts to users, and can provide the ability to respond to such notifications and alerts, take actions, and/or dive deeper into underlying data.

Abstract: Data may be stored by receiving the data to be stored, determining whether the data is regulated in a jurisdiction, and, responsive to the determination, selecting between a regulated storage scheme, requiring that the data be stored and/or processed in the jurisdiction in accordance with one or more laws pertaining to the jurisdiction, and an unregulated storage scheme, in which the data is not required to be stored in the jurisdiction and/or is not required to be stored in accordance with the one or more laws. Further, the regulated storage scheme may be followed by initiating storage of the data in the jurisdiction in accordance with the one or more laws.

Abstract: A monitoring module interfaces with existing non-retrospective data storage systems, thus providing mechanisms for detecting and reporting changes in data values stored in such systems. The monitoring module acts as a change detection layer that can operate in connection with multiple disparate systems and/or locations, so as to provide users with a unified view into data stored in such systems. For example, a user can consult a single app, website, or software application, to view changes for data values stored in multiple disparate systems and/or locations; the app can be configured to automatically generate notifications and alerts to users, and can provide the ability to respond to such notifications and alerts, take actions, and/or dive deeper into underlying data.

Abstract: According to various embodiments, a consolidated identity system and method are implemented to provide improved identity management and resource access management, particularly in the context of an enterprise system that requires a tight trust model. In at least one embodiment, the described system and method provide mechanisms for mapping identities among resources. The system and method are able to extract information relevant to a particular entity, such as an employee or user, and to consolidate and/or personalize such information as needed.

Abstract: A monitoring module interfaces with existing non-retrospective data storage systems, thus providing mechanisms for detecting and reporting changes in data values stored in such systems. The monitoring module acts as a change detection layer that can operate in connection with multiple disparate systems and/or locations, so as to provide users with a unified view into data stored in such systems. For example, a user can consult a single app, website, or software application, to view changes for data values stored in multiple disparate systems and/or locations; the app can be configured to automatically generate notifications and alerts to users, and can provide the ability to respond to such notifications and alerts, take actions, and/or dive deeper into underlying data.

Abstract: A content management system generates views of digital content for presentation on a user client. The content management system includes different publication templates having different layouts for presenting content on different types of viewing devices. The publication template is based on a layout, which specifies a spatial arrangement of sections. The publication template associates publication elements such as a leading article with sections of a layout. A view matches components such as an article with sections of a publication template based on a mapping between the components and publication elements associated with the sections. The content management system generates different views for different types of viewing devices. The content management system also analyzes interactions between user clients, components, and views, and the content management system includes an analytics interface to present data about these interactions.

Abstract: A content management system generates views of digital content for presentation on a user client. The content management system includes different publication templates having different layouts for presenting content on different types of viewing devices. The publication template is based on a layout, which specifies a spatial arrangement of sections. The publication template associates publication elements such as a leading article with sections of a layout. A view matches components such as an article with sections of a publication template based on a mapping between the components and publication elements associated with the sections. The content management system generates different views for different types of viewing devices. The content management system also analyzes interactions between user clients, components, and views, and the content management system includes an analytics interface to present data about these interactions.

Abstract: A distributed network identity is provided. An identity provider stores a portion of a user's personal information. A service provider accesses user information from one or more identity providers. System entities such as identity providers and service providers can be linked to enable information sharing and aggregation. User policies and privacy preferences are provided to control how information is shared. A single sign-on architecture is provided where an identity provider is used to facilitate cross-domain authentication and to enhance user convenience. Service delegation features are also provided.

Abstract: A distributed network identity is provided. An identity provider stores a portion of a user's personal information. A service provider accesses user information from one or more identity providers. System entities such as identity providers and service providers can be linked to enable information sharing and aggregation. User policies and privacy preferences are provided to control how information is shared. A single sign-on architecture is provided where an identity provider is used to facilitate cross-domain authentication and to enhance user convenience. Service delegation features are also provided.

Abstract: A distributed network identity is provided. An identity provider stores a portion of a user's personal information. A service provider accesses user information from one or more identity providers. System entities such as identity providers and service providers can be linked to enable information sharing and aggregation. User policies and privacy preferences are provided to control how information is shared. A single sign-on architecture is provided where an identity provider is used to facilitate cross-domain authentication and to enhance user convenience. Service delegation features are also provided.

Abstract: A distributed network identity is provided. An identity provider stores a portion of a user's personal information. A service provider accesses user information from one or more identity providers. System entities such as identity providers and service providers can be linked to enable information sharing and aggregation. User policies and privacy preferences are provided to control how information is shared. A single sign-on architecture is provided where an identity provider is used to facilitate cross-domain authentication and to enhance user convenience. Service delegation features are also provided.

Abstract: A distributed network identity is provided. An identity provider stores a portion of a user's personal information. A service provider accesses user information from one or more identity providers. System entities such as identity providers and service providers can be linked to enable information sharing and aggregation. User policies and privacy preferences are provided to control how information is shared. A single sign-on architecture is provided where an identity provider is used to facilitate cross-domain authentication and to enhance user convenience. Service delegation features are also provided.

Abstract: Distributed and replicated sessions are implemented in a grid architecture. A session including conversational state is stored at a server in the grid. An incoming request is directed to a server via a load balancing mechanism. When a server receives an incoming request, it either a) retrieves the session from the server that currently holds the state, or b) forwards the request to the server that currently holds the session. Each server maintains the session for the requests that it has serviced until relieved of this responsibility by another server. A server holding a session is relieved of responsibility for the state when another server retrieves the session. In one aspect of the invention, each session is replicated among a number of servers, so as to provide additional redundancy and thereby avoid having any single server as a single point of failure for the session which it maintains.

Abstract: A distributed system having a client and a server includes a state manager interposed between the client and the server. The state manager has a capability to generate a list of object attributes required to represent a state of the distributed system and a capability to cache object attributes so as to be locally accessible by the client. The distributed system further includes a service component interposed between the state manager and the server. The service component has a capability to fetch data from the server based on the list of object attributes.

Abstract: A method for a system having distributed collaborating components includes restricting direct interaction between distributed collaborating components by introducing an application-independent interface between distributed collaborating components and invoking a service from the application-independent interface in order to enable interaction between distributed collaborating components.