Abstract: The type definition of particular types such that different portions of the corresponding object graph may have different permissions assigned to those portions during instantiation. This allows structured permissions to be applied to instantiations of the object graphs of those defined types, allowing fine grained control over what access permissions are enforced against which portions of the object graph. In some embodiments, different instantiations of the object graph may apply permissions differently.

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 type definition of particular types such that different portions of the corresponding object graph may have different permissions assigned to those portions during instantiation. This allows structured permissions to be applied to instantiations of the object graphs of those defined types, allowing fine grained control over what access permissions are enforced against which portions of the object graph. In some embodiments, different instantiations of the object graph may apply permissions differently.

Abstract: A language extension that advances safety in system programming by specifying a lifetime of a reference that represents a resource. In accordance with the language extension, the lifetime references a particular scope in a manner that the compiler generates computer-executable instructions that enforce the lifetime of the reference to be a function of (e.g., no longer than) the lifetime of the particular scope. Accordingly, the resource lifetime may be specified in advance to have a particular scope. This helps in performing resource management as typical managed language programs can allow resources to exist indefinitely. Furthermore, because the resources have a defined finite lifetime, they might be more conveniently allocated on a stack, instead of on a heap, for much more efficient processing.

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: 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: 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.