Modeled types-attributes, aliases and context-awareness
First Claim
1. A computer-readable storage medium that is not a signal and that comprises computer-executable instructions that when executed by one or more processors of a computing environment cause the computing environment to:
- receive input specifying a name for a first modeled type, an underlying type for the first modeled type, at least one attribute of the first modeled type, and programming logic to be executed on a program element of the first modeled type during execution of an application to validate the program element against a range of valid values of the program element;
save, in a first library, the first modeled type and the programming logic to be executed on the program element of the first modeled type during execution of the application;
receive input specifying a second modeled type based on the first modeled type and a name for the second modeled type and providing a description of how to determine an explicit value for the at least one attribute during execution of the application; and
save, in a second library, the second modeled type including the description of how to determine the explicit value for the at least one attribute during execution of the application, the second library being different from the first library in which the first modeled type is saved.
2 Assignments
0 Petitions
Accused Products
Abstract
Modeled Types allow a developer to define attributes and/or code when defining a new type. When the Modeled Type is used, specific values may be assigned to the attributes. The consumer of the values of the attributes can be the type itself by executing the logic during application execution, or the consumer may be the runtime framework or the application using the values by querying the meta-data of the Modeled Type. Modeled Type Aliasing defines a Modeled Type based on another Modeled Type allowing both a new unique name but at the same time optionally supplying specific values to one or more of the attributes of the base Modeled Type. Context-aware Modeled Types provide a description of how to determine the value for the attribute.
18 Citations
9 Claims
-
1. A computer-readable storage medium that is not a signal and that comprises computer-executable instructions that when executed by one or more processors of a computing environment cause the computing environment to:
-
receive input specifying a name for a first modeled type, an underlying type for the first modeled type, at least one attribute of the first modeled type, and programming logic to be executed on a program element of the first modeled type during execution of an application to validate the program element against a range of valid values of the program element; save, in a first library, the first modeled type and the programming logic to be executed on the program element of the first modeled type during execution of the application; receive input specifying a second modeled type based on the first modeled type and a name for the second modeled type and providing a description of how to determine an explicit value for the at least one attribute during execution of the application; and save, in a second library, the second modeled type including the description of how to determine the explicit value for the at least one attribute during execution of the application, the second library being different from the first library in which the first modeled type is saved. - View Dependent Claims (2, 3)
-
-
4. A computer-implemented method for using modeled types, the method comprising:
-
receiving, by one or more processors, input specifying a name for a first modeled type, an underlying type for the first modeled type, at least one attribute of the first modeled type, and programming logic to be executed on a program element of the first modeled type during execution of an application to validate the program element against a range of valid values of the program element; saving, by the one or more processors, in a first library, the first modeled type and the programming logic to be executed on the program element of the first modeled type during execution of the application; receiving, by the one or more processors, input specifying second modeled type based on the first modeled type and a name for the second modeled type and providing a description of how to determine an explicit value for the at least one attribute during execution of the application; and saving, by the one or more processors, in a second library, the second modeled type including the description of how to determine the explicit value for the at least one attribute during execution of the application, the second library being different from the first library in which the first modeled type is saved. - View Dependent Claims (5, 6)
-
-
7. A computing system for using modeled types, the system comprising:
-
one or more processors; memory having stored therein computer-executable instructions that when executed by the one or more processors cause the computing system to; receive input specifying a name for a first modeled type, an underlying type for the first modeled type, at least one attribute of the first modeled type, and programming logic to be executed on a program element of the first modeled type during execution of an application to validate the program element against a range of valid values of the program element; save, in a first library, the first modeled type and the programming logic to be executed on the program element of the first modeled type during execution of the application; receive input specifying second modeled type based on the first modeled type and a name for the second modeled type and providing a description of how to determine an explicit value for the at least one attribute during execution of the application; and save, in a second library, the second modeled type including the description of how to determine the explicit value for the at least one attribute during execution of the application, the second library being different from the first library in which the first modeled type is saved. - View Dependent Claims (8, 9)
-
Specification