DAXP Dynamic Dictionary

The DAXP Dynamic Dictionary is a central, extensible structure that defines all data elements, message types, and logical relations within the DAXP ecosystem.
It enables applications and microservices to interpret messages dynamically — without recompilation or predefined schemas — ensuring complete interoperability and flexibility.

1. Attribute and Tag Definitions

Each piece of data in a DAXP message is represented by a tag, which uniquely identifies a value or attribute  within the application domain.
Tags are stored in the dictionary along with their metadata and attributes that describe how they should be interpreted, validated, and presented.

Parameter Attributes

• Value type (mandatory) — defines the data type (e.g., INT, DECIMAL, CHAR, BOOLEAN, etc.)
• Range — defines minimum and/or maximum value limits (for numeric parameters)
• Step size — specifies the increment used when changing a numeric value
• Precision — defines the number of decimal places for decimal values
• List of values — enumerates allowed options for discrete parameters
• UI Label - Defines the display name for graphical interfaces.
• UI Description - Provides a short description or tooltip text for the UI element.

2. Groups and Dependencies

Tags can be organized into groups, which represent logical or functional structures (e.g., “Customer”, “Order”, “Instrument”, “MarketData”).
Groups may contain nested groups or tags and can define dependencies between elements — for example, visibility or activation rules in a user interface.

Each group entry typically contains:

• Group ID
• Parent Group ID (for hierarchical structures)
• Name and Description
• List of Member Tags
• Dependency Rules (e.g., conditional visibility or validation)

3. Message Types

DAXP defines multiple message types used to represent various kinds of communication between components or services.
Message types can be predefined or dynamically added to the dictionary.

Each message type describes:

• Message Symbol / Identifier
• Message Role (e.g., REQ, RSP, EVT)
• Associated Group(s) of parameters
• Direction and purpose (e.g., request, response, event notification)

4. Actions

An Action represents an executable operation or command — effectively a message type associated with a specific group of parameters.
Actions are used to define interactive behaviors (for example, GUI buttons, API calls, or service triggers).

.....