Universal binary specification model

1. A method comprising:

creating a normalized binary specification model, including:

receiving existing binary descriptions corresponding to documents that describe aspects of respective binary communication protocols, binary data storage formats, or binary data processing architectures;

identifying description type of each of the existing binary descriptions;

based on the description type, assign each of the existing binary descriptions to a respective loader from a plurality of loaders;

wherein each loader from the plurality of loaders performs the following steps:

ingesting corresponding one or more descriptions from the existing binary descriptions;

discerning relevant binary information items from within the corresponding one or more descriptions;

converting the relevant binary information items into normalized binary specification components, wherein the normalized binary specification components include:

(a) normalized binary specification types,

(b) normalized binary specification groups,

(c) normalized binary specification rules,

(d) normalized binary specification values, and

(e) normalized binary specification actions;

generating identifiers and assigning a respective identifier to each of the normalized binary specification components to produce identified normalized binary specification components; and

creating a respective ordered list for each of the normalized binary specification components.

2. The method of claim 1 , wherein the identifying the description type includes:

identifying the relevant binary information items within each of the existing binary descriptions and comparing the relevant binary information items within the existing binary descriptions to known description formats;

based on the comparison, assign a description type to each of the existing binary descriptions.

3. The method of claim 1 , wherein the converting includes:

normalizing semantics of names in the relevant binary information items into names of the normalized binary specification components.

4. The method of claim 1 , wherein the converting includes: deconstructing binary types of existing elementary binary components into lists of elementary type traits.

5. The method of claim 1 , wherein the converting includes: deconstructing binary rules of existing elementary binary components into lists of ordered extensible parameters.

6. The method of claim 1 , wherein the normalized binary specification components include:

(f) details including organization, version, date, and active/inactive status.

7. The method of claim 1 , wherein the generating identifiers includes:

obtaining information from the normalized binary specification components; and

generating the identifiers from the obtained information.

8. The method of claim 1 , wherein the generating identifiers includes:

obtaining information from the normalized binary specification components;

generating a first iteration of identifiers from the obtained information;

checking whether each of the identifiers in the first iteration is unique and, if not, generating a second iteration of identifiers in which the non-unique identifiers from the first iteration are made more complex.

9. The method of claim 1 , comprising:

providing a domain specific normalized binary specification editing language for a user to edit content of the identified normalized binary specification components.

10. The method of claim 1 , comprising:

providing a domain specific normalized binary specification editing language for a user to edit content of the identified normalized binary specification components, wherein the domain specific normalized binary specification editing language searches for the identifiers and changes component information.

11. A system comprising:

a machine or group of machines, each including respective one or more processors, for creating a normalized binary specification model, including:

a receiver configured to receive existing binary descriptions, wherein each binary description is a document that describes aspects of a respective binary communication protocol, binary data storage format, or binary data processing architecture;

an identifier configured to identify description type of each of the existing binary descriptions;

a categorizer configured to, based on the description type, assign each of the existing binary descriptions to a respective loader from a plurality of loaders;

each loader from the plurality of loaders configured to:

ingest corresponding one or more descriptions from the existing binary descriptions;

discern relevant binary information items from within the corresponding one or more descriptions;

convert the relevant binary information items into normalized binary specification components, wherein the normalized binary specification components include:

(a) normalized binary specification types,

(b) normalized binary specification groups,

(c) normalized binary specification rules,

(d) normalized binary specification values, and

(e) normalized binary specification actions;

generate identifiers and assigning a respective identifier to each of the normalized binary specification components to produce identified normalized binary specification components; and

create a respective ordered list for each of the normalized binary specification components.

12. The system of claim 11 , wherein the identifier is configured to:

identify the relevant binary information items within each of the existing binary descriptions and compare the relevant binary information items within existing binary descriptions to known description formats;

based on the comparison, assign a description type to each of the existing binary descriptions.

13. The system of claim 11 , each loader from the plurality of loaders configured to:

normalize semantics of names in the relevant binary information items into names of the normalized binary specification components.

14. The system of claim 11 , each loader from the plurality of loaders configured to:

deconstruct binary types of existing elementary binary components into lists of elementary type traits.

15. The system of claim 11 , each loader from the plurality of loaders configured to:

deconstruct binary rules of the existing elementary binary components into lists of ordered extensible parameters.

16. The system of claim 11 , wherein the normalized binary specification components include:

(f) details including organization, version, date, and active/inactive status.

17. The system of claim 11 , each loader from the plurality of loaders configured to:

obtain information from the normalized binary specification components; and

generate the identifiers from the obtained information.

18. The system of claim 11 , each loader from the plurality of loaders configured to:

obtain information from the normalized binary specification components;

generate a first iteration of identifiers from the obtained information;

check whether each of the identifiers in the first iteration is unique and, if not, generate a second iteration of identifiers in which the non-unique identifiers from the first iteration are made more complex.

19. The system of claim 11 , comprising:

a manipulator including a domain specific normalized binary specification editing language for a user to edit content of the identified normalized binary specification components.

20. The system of claim 11 , comprising:

a manipulator including a domain specific normalized binary specification editing language for a user to edit content of the identified normalized binary specification components, wherein the domain specific normalized binary specification editing language searches for the identifiers and changes component information.

21. A method comprising:

creating a normalized binary specification model, including:

receiving existing binary descriptions, each of the existing binary descriptions describing at least one of a binary communication protocol, a binary data storage format, or a binary data processing architecture,

identifying a respective type of binary information described in each of the existing binary descriptions;

based on the respective type, assign each of the existing binary descriptions to a respective loader from a plurality of loaders;

wherein each loader from the plurality performs the following steps:

ingesting one or more corresponding binary descriptions from the

existing binary descriptions;

discerning relevant binary information items from within the one or more corresponding binary descriptions;

converting the relevant binary information items into normalized binary specification components, wherein the normalized binary specification components include:

(a) normalized binary specification types,

(b) normalized binary specification groups,

(c) normalized binary specification rules,

(d) normalized binary specification values, and

(e) normalized binary specification actions;

generating identifiers and assigning a respective identifier to each of the normalized binary specification components to produce identified normalized binary specification components; and

creating a respective ordered list for each of the normalized binary specification components.

22. The method of claim 21 , wherein identifying the respective type includes:

identifying the relevant binary information items within each of the existing binary descriptions and comparing the relevant binary information items within the existing binary descriptions to known formats;

based on the comparison, assign the respective type to the binary information.

23. The method of claim 21 , wherein the converting includes:

normalizing semantics of names in the relevant binary information items into names of normalized binary specification components.

24. The method of claim 21 , wherein the converting includes:

deconstructing binary types of existing elementary binary components into lists of elementary type traits.

25. The method of claim 21 , wherein the converting includes:

deconstructing binary rules of existing elementary binary components into lists of ordered extensible parameters.

26. The method of claim 21 , wherein the normalized binary specification components include:

(f) details including organization, version, date, and active/inactive status.

27. The method of claim 21 , wherein the generating identifiers includes:

obtaining information from the normalized binary specification components; and

generating the identifiers from the obtained information.

28. The method of claim 21 , wherein the generating identifiers includes:

obtaining information from the normalized binary specification components; generating a first iteration of identifiers from the obtained information;

checking whether each of the identifiers in the first iteration is unique and, if not, generating a second iteration of identifiers in which the non-unique identifiers from the first iteration are made more complex.

29. The method of claim 21 , comprising:

providing a domain specific normalized binary specification editing language for a user to edit content of the identified normalized binary specification components, wherein the domain specific normalized binary specification editing language searches for the identifiers and changes component information.