[Simplification] Convert the static definitions for type definitions into Enums

[mandy-chessell]

Existing/related issue?

No response

Please describe the new behavior that that will improve Egeria

This change aims to simplify the way that new Open Metadata Types are defined and ensure that associated reference data is generated in the code content packs.

The plan is to ensure all Open Metadata Types are defined as Enum entries in OpenMetadataType.java. Once they are in place, the enum definitions can be used to drive the definition of the types in the Open Metadata Type Archive and wherever the type is used - core runtime, connectors etc.

Similarly, the properties for the open types are being defined as Enum entries in OpenMetadataProperty.java.

These files are found in the Open Metadata Framework (OMF) that supplied the core definitions of the open metadata standard.

How is the work being performed

This is a big change. Types and properties are changed in small increments as the community has time. So far, subject areas 0-2 are complete and some progress has been made on the othere (3-7). When new types are converted to enums, they are updated in the archi definitions, and wherever the type is used. Then the content packs are updated by running each of the archive writers. This refreshed the reference data used in the core runtime.

Alternatives

Continue as we are.

Any Further Information?

As the types are converted, links to their documentation page are display in the brain explorer.
https://app.thebrain.com/brain/60bb4cf5-1ec7-4ee2-b169-9aba1202cacb

Would you be prepared to be assigned this issue to work on?

No response