Systems and methods for generating pluggable domain-specific data types

• US 10,114,879 B2
• Filed: 03/16/2017
• Issued: 10/30/2018
• Est. Priority Date: 09/30/2011
• Status: Active Grant

• Current Assignee: Saama Technologies LLC (Saama Technologies, Inc.)
• Original Assignee: Comprehend Systems, Inc. (Saama Technologies, Inc.)
• Inventors: Morrison, Rick, Gardner, Jud, Saffer, Matthew
• Primary Examiner(s): Dwivedi, Mahesh H
• Application Number:
  US15/461,463
• Publication Number:
  US 20170249372A1
• Time in Patent Office: 593 Days
• Field of Search: 707803, 707809
• CPC Class Codes: G06F 16/211 Schema design and management
• CPC Class Codes: G06F 16/212 with details for data modelling support
• CPC Class Codes: G06F 16/22 Indexing; Data structures therefor; Storage structures
• CPC Class Codes: G06F 16/258 Data format conversion from or to a database

Abstract

Systems and methods for generating pluggable domain-specific data types are provided herein. According to some embodiments, methods for generating pluggable domain-specific data types may include 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, the domain-specific data unit including two or more data units received from one or more data sources, 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 domain-specific data type library.

Claims

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, the domain-specific data unit including two or more data units received from one or more data sources, each data unit having a unit of measure;

assigning a third unit of measure to the domain-specific data type, the third unit of measure based upon at least two of the two or more data units;

converting a first domain-specific data unit into a second domain-specific data unit utilizing the units of measure for both the first and second domain-specific data units;

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 domain-specific data type library.

2. The method according to claim 1, further comprising assembling a domain-specific data unit by:

obtaining the two or more data units from the one or more data sources;

encoding the two or more units into the domain-specific data unit according to the schema; and

storing the 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, 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 2, 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 5, 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 measure for the domain-specific data unit.

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

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

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

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

a memory for storing executable instructions; and

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 two or more data units received from one or more data sources, each data unit having a unit of measure;

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

generates the domain-specific data type utilizing the established 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 domain-specific data type library; and

an analysis module that converts a first domain-specific data unit into a second domain-specific data unit utilizing the units of measure for both the first and second domain-specific data units.

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

a data gathering module that obtains the two or more data units from the one or more data sources; and

an encoding module that encodes the two or more units into the domain-specific data unit according to the schema and stores the domain-specific data unit in a storage media.

13. The system according to claim 11, 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.

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

15. The system according to claim 14, 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.

16. The system according to claim 11, wherein the typing generator module establishes units of measurement for the domain-specific data unit.

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

18. 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, the domain-specific data unit including two or more data units received from one or more data sources, each data unit having a unit of measure;

assigning a third unit of measure to the domain-specific data type, the third unit of measure based upon at least two of the two or more data units;

converting a first domain-specific data unit into a second domain-specific data unit utilizing the units of measure for both the first and second domain-specific data units;

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 domain-specific data type library.