Abstract: Architecture that includes a platform independent, configuration driven, presentation composition engine. The composition engine that allows dynamic generation of multiplatform user experience (UX) based on a data contract. By composition, the user can select the parts, interactions, and constraints between the interaction and parts, as well as the placement with respect to each other. The UX is dynamically composed from components that are targeted to particular data classes. At runtime, platform dependent component implementations are automatically selected by the engine based on the execution platform of the composition host. A user can create or customize the UX without writing code by composing from a wide variety of presentation widgets that access a wide variety of data sources that can work on many platforms. Compositions are targeted to both a data class and presentation type and can be either predefined or generated.

Abstract: Various implementations are described herein for providing unified user experiences using data attributes and data models. By referencing structural information of data attributes included in data models, users are able to interact with and/or view related data stored in different databases. Contextual information for the different databases, data attributes, and data models provide a seamless unified user experience when running reports, scripts, web controls and so forth associated with the related data.

Abstract: An abstraction layer (e.g., transport) between consumer logic (e.g., presentation) and provider logic (e.g., business) that makes composition of, for example, many presentation technologies to many business logic data providers possible without imposing strict interface boundaries to each. The abstraction layer can be an abstract transport data model bus that provides serialization, transformation, and transport services. A core concept of the data access library implementation is a transmittable data object based on a flexible property bag data structure and abstract type system. Pluggable data providers declare the associated data model, and pluggable consumer clients declare the data model consumed (a many-to-many implementation). In other words, declarative (codeless) combinations of front ends and back ends are employed. Moreover, the abstraction layer is hidden from the developer.

Abstract: A dashboard can be composed of pre-defined data provider, presentation, and processor components. The data provider component acquires data from a source, and the presentation component visualizes data. The processor component enhances the data for actionable usability by various means (e.g., data aggregation, filtering, projections, wave shaping, anomaly detection, and combination . . . ).

Abstract: Architecture that includes a platform independent, configuration driven, presentation composition engine. The composition engine that allows dynamic generation of multiplatform user experience (UX) based on a data contract. By composition, the user can select the parts, interactions, and constraints between the interaction and parts, as well as the placement with respect to each other. The UX is dynamically composed from components that are targeted to particular data classes. At runtime, platform dependent component implementations are automatically selected by the engine based on the execution platform of the composition host. A user can create or customize the UX without writing code by composing from a wide variety of presentation widgets that access a wide variety of data sources that can work on many platforms. Compositions are targeted to both a data class and presentation type and can be either predefined or generated.

Abstract: An abstraction layer (e.g., transport) between consumer logic (e.g., presentation) and provider logic (e.g., business) that makes composition of, for example, many presentation technologies to many business logic data providers possible without imposing strict interface boundaries to each. The abstraction layer can be an abstract transport data model bus that provides serialization, transformation, and transport services. A core concept of the data access library implementation is a transmittable data object based on a flexible property bag data structure and abstract type system. Pluggable data providers declare the associated data model, and pluggable consumer clients declare the data model consumed (a many-to-many implementation). In other words, declarative (codeless) combinations of front ends and back ends are employed. Moreover, the abstraction layer is hidden from the developer.

Abstract: Various implementations are described herein for providing unified user experiences using data attributes and data models. By referencing structural information of data attributes included in data models, users are able to interact with and/or view related data stored in different databases. Contextual information for the different databases, data attributes, and data models provide a seamless unified user experience when running reports, scripts, web controls and so forth associated with the related data.