Flexible metadata composition
Various embodiments provide an ability to abstract type resolution between multiple type systems. At least one type can be described in one or more programmatically accessible file(s). In some embodiments, an application using a different type system can programmatically access and resolve a type of the at least one type system without knowledge of a location of where a description of the type resides. Alternately or additionally, type descriptions contained in the one or more programmatically accessible file(s) can be analyzed and restructured into one or more new programmatically accessible file(s) based, at least in part, upon the type descriptions.
1. A computer-implemented method comprising:
receiving one or more input criteria associated with generating one or more output files, at least one input criteria associated with a namespace hierarchy;
receiving one or more input metadata files that include information associated with at least one type contained within the namespace hierarchy, the information associated with the at least one type comprising type resolution information described with an abstract type system;
responsive to receiving the one or more input metadata files, reorganizing the information associated with the at least one type based, at least in part, on the one or more input criteria; and
generating at least one output metadata file configured to include the reorganized information associated with the at least one type.
2. The computer-implemented method of claim 1 , the at least one output metadata file utilizing a naming convention based, at least in part, on the namespace hierarchy.
3. The computer-implemented method of claim 1 , the at least one input criteria associated with a namespace hierarchy comprising a criteria specifying a level of namespace hierarchy at which to partition the information into the one or more output files.
4. The computer-implemented method of claim 1 , the at least one type comprising an object-oriented class.
5. The computer-implemented method of claim 1 , the method further comprising analyzing the information associated with the at least one type for namespace hierarchy information.
6. The computer-implemented method of claim 1 , the method further comprising receiving a request to search the at least one output metadata file.
7. The computer-implemented method of claim 6 , wherein the received request to search the at least one output metadata file specifies a namespace hierarchy level.
8. The computer-implemented method of claim 1 , the information associated with the at least one type comprising object-oriented associations.
9. The computer-implemented method of claim 1 , the abstract type system being a type system that is independent of a specific programming language.
10. One or more computer-readable hardware storage memories comprising computer readable instructions which, responsive to execution, implement operations comprising:
receiving one or more input criteria associated with generating one or more output files, at least one input criteria specifying a namespace hierarchy;
receiving one or more input files that include information associated with at least one type contained within the namespace hierarchy, the at least one type representing functionality provided by an operating system and the information associated with the at least one type comprising type resolution information described with an abstract type system; and
generating at least one output metadata file configured to include the information associated with the at least one type reorganized based, at least in part, on the one or more input criteria.
11. The one or more computer-readable hardware storage memories of claim 10 , the at least one output metadata file utilizing a naming convention based, at least in part, on the namespace hierarchy.
12. The one or more computer-readable hardware storage memories of claim 10 , the at least one output metadata file containing a description associated with an operating system software interface.
13. The one or more computer-readable hardware storage memories of claim 10 , the at least one input criteria specifying a namespace hierarchy comprising a criteria specifying a level of namespace hierarchy at which to partition the information into the one or more output files.
14. The one or more computer-readable hardware storage memories of claim 10 , the at least one type comprising an object-oriented class.
15. The one or more computer-readable hardware storage memories of claim 10 , the method further comprising analyzing the information associated with the at least one type for namespace hierarchy information.
16. A system, comprising:
one or more processors; and
memory, communicatively coupled to the one or more processors, storing instructions that, responsive to execution, configure the one or more processors to:
receive one or more input criteria associated with generating one or more output files, at least one input criteria associated with a first level of a namespace hierarchy;
receive one or more input metadata files that include information associated with at least one type contained within the namespace hierarchy, the information associated with the at least one type comprising type resolution information described with an abstract type system; and
generate one or more output metadata files configured to include the information associated with the at least one type regrouped based, at least in part, on the one or more input criteria such that the regrouped information includes the first level of the namespace hierarchy and a second level of the namespace hierarchy.
17. The system of claim 16 , the one or more output metadata files configured to describe the at least one type independent of a specific programming language.
18. The system of claim 16 , the one or more processors further configured to search the one or more output metadata files for a file with a filename that matches a namespace of the at least one type.
19. The system of claim 16 , the one or more processors further configured to search the one or more output metadata files without knowledge of a location of where the at least one type resides.
20. The system of claim 16 , the one or more processors further configured to resolve another type system through access to the one or more output metadata files.