Abstract: The compilation a transformation chain of a recalculation user interface that displays an electronic canvas that contains one or more displayed result of a transformation chain. The transformation chain includes transforms between a respective data source and data sink. User editing of the recalculation user interface could cause one or more of the transforms to be re-executed, thereby causing recalculation. The compilation involves analyzing the transformation chain of the recalculation user interface for dependencies to create a dependency graph of dependencies between entities. For instance, some dependencies might be between entities so as to indicate that if one entity is evaluated, then the other should be also. The dependency graph is then used to create a lower level of execution steps. The dependency graph is further provided to a runtime for the program, so that the dependency graph may be available during operation of the recalculation user interface.

Abstract: The facilitated selection of an event that would trigger a control to perform a behavior. The control has multiple events that that may be used to trigger a behavior. It could perhaps be difficult for a user, especially a non-programmer, to select the appropriate event that triggers any given behavior. The system helps by automatically identifying a set of one or more events that are consistent with an intent for the control to perform a behavior of interest, in response to the user specifying the behavior. The automatically identified event might also depend on data of interest that the user identifies as to be operated upon by the control in performing the behavior. The system might propose one or more of the automatically identified events, and might even automatically configure the control to perform the behavior in response to a selected event.

Abstract: A computerized tool to visually display data using a graphical object. Visual display components may be identified that can represent a portion of the data and may be proposed to a user, based on visual characteristics of each of the visual display components and parameter(s) of the data. A visual display component selected from these components based on user input may be linked to the portion of the data set so that the visual display component will modify the appearance of the graphical object in a way that represents the portion of the data. Different visual display components may be identified and suggested for a user's selection to represent other portions of the data using the graphical object. The graphical object may thus be incrementally refined to ultimately result in the visual representation of the data.

Abstract: The use of a data stream object to enumerate elements of a data stream to thereby drive rendering of a data-driven model. The data driven model includes multiple view components that may use their own construction logic to render visual items based on data provided to their input parameter(s). The data stream may be quite large, in which case, only a portion of the data stream is enumerated by the data stream object. The enumerated elements of the data stream may be used to populate the input parameters of the view components, and or may be provided to analytics, from which input parameters of the view components may be derived. Thus, a data stream, regardless of its size, may be dealt with in the consistent manner to thereby drive the data-driven model.

Abstract: The present invention extends to methods, systems, and computer program products for allowing a computer system user to extend the functionality of a data-centric software application. The method includes instantiating the data-centric software application, where the data-centric application has portions of business logic categorized and associated with items of data-centric application functionality defined in a schema. The method includes receiving customization input to customize at least one of the portions of business logic. The method includes formulating a representative model corresponding to at least one of the portions of customized business logic. The method includes applying the representative model to the schema to generate a customized schema that extends the business logic of the data-centric software application.

Abstract: Visualization frameworks may include solvers. The solvers may be used to determine the properties of view components of view compositions. In some instances, the solvers may be explicitly composed using a relational structure, such as a dependency tree. In some instances, the solvers may be implicitly composed based on property-setters having solvers invoking other property-setters having solvers.

Abstract: Validating executable data for interactions among a plurality of process artifacts at design time. A data context is created to include the plurality of process artifacts. The data context carries interaction rules among the plurality of process artifacts. The executable data from a data source is associated with the plurality of process artifacts in the created data context. A subset of the interaction rules is selected corresponding to at least one of the plurality of process artifacts. The associated executable data is validated when the associated executable data is in accordance with the selected subset of the interaction rules.

Abstract: The composition of multiple analytical visual composition models into a single whole. A model importation mechanism allows a model author or other user import all or portions of other models. By so doing, the author might cause the following to be supplemented or changed in an existing analytics-driven model: 1) additional model input data as well to generate a supplemented set of model input data; 2) additional bindings between the supplemental set of model input data to the model parameters; 3) additional model parameters to generate a supplemental set of model parameters; and 4) additional analytical relationships between the supplemental set of model parameters. Accordingly, the author may borrow from models by other authors, allowing for effective collaboration in order to construct increasingly complex models.

Abstract: The present invention extends to methods, systems, and computer program products for using cinematic technique taxonomies to present data. Embodiments of the invention can be used to infer and identify cinematic techniques or combinations thereof based on a model and user action. Cinematic techniques can be used to meet the data exploration and analysis requirements of a user. As such, embodiments of the invention permit users (including non-programmers) to employ cinematic techniques from a cinematic technique hierarchy (possibly in combination with other techniques) to gain insights into their data and also convey appropriate emotional messages.

Abstract: The present invention extends to methods, systems, and computer program products for assisting users with presenting data using cinematic techniques. Embodiments of the invention can be used to infer and generate cinematic techniques or combinations thereof based on a model and user action. Cinematic techniques can be used to meet the data exploration and analysis requirements of a user. As such, embodiments of the invention assist users (including non-programmers) to employ cinematic techniques (possibly in combination with other techniques) to gain insights into their data and also convey appropriate emotional messages.

Abstract: The present invention extends to methods, systems, and computer program products for using cinematic techniques to present data. Embodiments of the invention can be used to infer and generate cinematic techniques or combinations thereof based on a model and user action. Cinematic techniques can be used to meet the data exploration and analysis requirements of a user. As such, embodiments of the invention permit users (including non-programmers) to employ cinematic techniques (possibly in combination with other techniques) to gain insights into their data and also convey appropriate emotional messages.

Abstract: An interactive recommendation system generates one or more recommendations (e.g., recommended products, travel destinations, etc.) for a user based on a recommendation model. The recommendation model includes one or more criteria that are used to analyze a datastore of user characteristics (e.g., a user's age, location, past online behavior, etc.) and generate one or more recommendations based thereon. The interactive recommendation system further presents a user interface that allows the user to interactively modify the criteria of the recommendation model and to apply the modified recommendation model to the datastore in order to generate one or more modified recommendations. In this manner, for example, the user can customize the recommendations he or she receives by interacting with the recommendation system to modify the recommendation model used to generate such recommendations.

Abstract: The rendering of sequential data-driven scenes. Each data-driven scene is constructed using a plurality of view components, each receiving data into its input parameters, and using construction logic to formulate a rendering of corresponding visual item(s). When a transition even is detected, the data-driven scene changes from one scene to the next. For instance, the transition might occur by changing any one or more of the following: changing the data that is applied to the view components, 2) changing the set of view components, 3) changing the dimension set, or 4) changing one or more geometries used to construct the scene. Thus, data-driven scenes may be presented sequentially.

Abstract: Aspects described relate to analyzing data at a high level of abstraction. “Smarts,” incorporating one or more analytic patterns, may be applied to data sources. These Smarts may be in the form of at least one of an equation, rule, constraint or expression to generate a result from applying the analytic pattern to the data. Smarts may be pre-defined and selected from a library based on user preference and the data input. Any suitable user interface may be used to apply analytic pattern(s) to items of data as well as provide a visual environment for a user to make intuitive adjustments to the data, add controls in the user interface to filter or constrain the data, or combinations thereof, resulting in one or more modified results.

Abstract: The rendering on a user interface of a potentially complex computerized scene generation system. The user interface includes visual item(s) that have associated data. In addition, another set of visual items may be driven by data provided to input parameters, and may represent elements in the scene. Through user gestures, a user may correlate data items in the data source visual items with the element visual items to thereby automatically populate the element visual items with data, affecting the rendering of the data-driven element visual items. The element visual items might be linked, once again, perhaps through user gestures, to a parent visual item. In so doing, properties of the parent visual item might change and/or input parameters of the element visual items might change. Accordingly, complex visual scenes may be created through potentially quite simple user gestures.

Abstract: The use of a data structure that is a symbolic representation of a keyed array that has an array variable and an associated key variable. There is a correlation maintained between the variable type of the array variable and the corresponding keying set that is to be bound to the associated key variable. The keyed array may remain unbound thereby being simply symbolically represented, or the keying set may be bound to the key variable more immediately. In one embodiment, once the keying set is bound to the key variable, data may be bound to the array variable itself. This may be repeated for multiple keyed arrays. The data from multiple keyed arrays may be operated upon to about another array of values, which may then be aggregated in some way.

Abstract: Visual items may each be constructed and placed in position using logic defined by a view component corresponding to each visual item, where that logic may depend on one or more values populated into parameter(s) of the view component. Some of those parameter values may correspond to known model parameter values. Others, however, may have been solved for using a model that defines analytical relationships between the model parameters. In one embodiment, which of the model parameters are known, and which are unknown, may not be predetermined. Accordingly, a solver might be prepared for multiple solve operation paths even using a single model. The view composition process may be entirely data-driven, and may include a mechanism for canonicalizing input data, and binding canonicalized input data to the model parameters. The view composition framework may operate the same regardless of the domain.

Abstract: Technologies are presented herein for self-describing re-usable software components. Metadata is generated and published with a re-usable software component that identifies the capabilities of the software component, identifies other software components that the re-usable software component may be integrated with, and identifies mechanisms for integrating the re-usable software component with other software components. The metadata can then be used to discover re-usable software components and to integrate the re-usable software components with other software components.

Abstract: The inference of a dependency graph that represents a graph of solves that leads from input model parameter(s) to output model parameters using analytics. In one embodiment, the dependency graph is part of visually driven analytics in which the output model parameter(s) are used to formulate data-drive scenes. As the identity of the input and/or output model parameter(s) change, or as the analytics themselves change, the dependency graph may also change. This might trigger a resolve of the analytics. In one embodiment, the intermediate parameters involved in the dependency graph may be viewed and evaluated by the user.

Abstract: A dynamic verification system is described that enables application developers to safely include significant custom business logic in their applications. The dynamic verification system receives application behavior criteria that specify behavior of an application of interest to an application host. The system executes an application and instruments an application execution environment to detect application behavior that meets the application behavior criteria. The system determines when the application has performed an action that satisfies the application behavior criteria and provides a notification about the application behavior that occurred that a system administrator can use to take action against the application.