Pluggable domain-specific typing systems and methods of use

1. A method for generating a pluggable domain-specific data type, the method comprising:

determining a schema for the domain-specific data type, the schema including a data protocol that defines how data units are to be encoded into a domain-specific data unit and locations of a plurality of acceptable data sources, the domain-specific data unit including first data unit having a first unit of measure and a second data unit having a second unit of measure, the first and second data units;

assigning a third unit of measure to the domain-specific data unit, the third unit of measure based upon the first and second units of measure;

generating the domain-specific data type utilizing the determined schema, the domain-specific data type having a pluggable format such that the domain-specific data type may be utilized by a third-party application; and

storing the domain-specific data type in a pluggable domain-specific data type library, the pluggable domain-specific data type being at least one of transferable to other applications or incorporable into other domain-specific data type libraries.

2. The method according to claim 1 , further comprising:

assembling a domain-specific data unit by:

searching the plurality of acceptable data sources to locate a plurality of the first and second data units;

obtaining the first and second data units from the plurality of acceptable data sources;

encoding the first and second data units into the domain-specific data unit according to the schema; and

storing the assembled domain-specific data unit in a storage media.

3. The method according to claim 1 , wherein the data units may include any of a primitive, a tuple, a series, a date series, a temporal type, an aggregate comparison of primitives, geographical data, pre-existing data units, and combinations thereof.

4. The method according to claim 1 , further comprising decoding the domain-specific data unit into data units utilizing the schema such that the data units may be stored in a legacy data source.

5. The method according to claim 1 , wherein encoding further includes associating a metadata audit trail with the domain-specific data unit, the metadata audit trail including information that corresponds to at least one of the two or more data units, the one or more data sources, the combination of the two or more units, and the storage of the domain-specific data unit.

6. The method according to claim 1 , further comprising decoding the domain-specific data unit to recover the two or more data units utilizing the metadata audit trail.

7. The method according to claim 1 , further comprising establishing units of measurement for each of a plurality of data units.

8. The method according to claim 7 , further comprising converting a first domain-specific data unit into a second domain-specific data unit utilizing the units of measurement for both the first and second domain-specific data units.

9. The method according to claim 1 , further comprising normalizing at least one of the two or more data units before the step of encoding.

10. The method according to claim 1 , further comprising establishing behavioral characteristics for the schema, the behavioral characteristics determining how the domain-specific data units behave relative to one or more standard operations.

11. The method according to claim 1 , further comprising performing an evaluative function with one or more domain-specific data units.

12. A system for generating a pluggable domain-specific data type, the system comprising:

a memory for storing executable instructions;

a processor for executing the instructions, the instructions including:

a typing generator module that:

establishes a schema for the domain-specific data type, the schema including a data protocol that defines how data units are to be encoded into a domain-specific data unit, the domain-specific data unit including a first data unit having a first unit of measure and a second data unit having a second unit of measure, the first and second data units received from one or more data sources;

assigns a third unit of measure to the domain-specific data unit, the assignment of the third unit of measure based upon the first and second units of measure;

generates the domain-specific data type utilizing the determined schema, the domain-specific data type having a pluggable format such that the domain-specific data type may be utilized by a third-party application; and

stores the domain-specific data type in a pluggable domain-specific data type library.

13. The system according to claim 12 , further comprising:

a data gathering module that:

searches the plurality of acceptable data sources to locate a plurality of the first and second data units, and

obtains the first and second data units from the plurality of acceptable data sources; and

an encoding module that encodes the first and second data units into a domain-specific data unit according to the schema and stores the encoded domain-specific data unit in a storage media.

14. The system according to claim 12 , wherein the data units may include any of a primitive, a tuple, a series, a date series, a temporal type, an aggregate comparison of primitives, geographical data, and combinations thereof.

15. The system according to claim 12 , further comprising a metadata generator that generates a metadata audit trail for the domain-specific data unit, the metadata audit trail including information that corresponds to at least one of the two or more data units, the one or more data sources, the combination of the two or more units, and the storage of the domain-specific data unit.

16. The system according to claim 15 , wherein the encoding module decodes the domain-specific data unit to recover the two or more data units utilizing at least one of the schema and the metadata audit trail.

17. The system according to claim 12 , wherein the typing generator module establishes units of measurement for each of the data units.

18. The system according to claim 17 , further comprising an analysis module that converts a first domain-specific data unit into a second domain-specific data unit utilizing the units of measurement for both the first and second domain-specific data units.

19. The system according to claim 12 , wherein the analysis module normalizes at least one of the two or more data units before the step of encoding.

20. A non-transitory computer readable storage media having a program embodied thereon, the program being executable by a processor to perform a method generating pluggable domain-specific data types, the method comprising:

determining a schema for the domain-specific data type, the schema including a data protocol that defines how data units are to be encoded into a domain-specific data unit and locations of a plurality of acceptable data sources, the domain-specific data unit including a first data unit having a first unit of measure and a second data unit having a second unit of measure, the first and second data units, assigning a third unit of measure to the domain-specific data unit, the third unit of measure based upon the first and second units of measure

generating the domain-specific data type utilizing the determined schema, the domain-specific data type having a pluggable format and including instructions that instruct a third party legacy application in the creation and utilization of domain-specific data units, such that the domain-specific data type may be utilized by the third-party legacy application; and

storing the domain-specific data type in a pluggable domain-specific data type library the pluggable domain-specific data type being at least one of transferable to other applications or incorporable into other domain-specific data type libraries.