Implement each tag as a class, with operations as methods

[Bombardier-C-Kram]

Problem

Currently, each operation in the API is represented as an individual namespace. This results in a fragmented and less organized structure, especially as the number of operations grows. Additionally, there is an inconsistency since there is a main class and operations use namespaces.

Proposed Solution

• Refactor code so that each tag is implemented as a class.
• The operations associated with a tag should be implemented as functions (methods) within the relevant class, rather than as individual namespaces.
• This structure maintains organizational consistency and prevents mixing classes and namespaces.

Rationale

• Improves code organization and readability by grouping related operations logically.
• Avoids mixing object-oriented (class-based) and namespace-based approaches.
• Makes maintenance and navigation easier as the API surface area grows.

Additional Notes

• Documentation and examples should be updated to reflect the new structure.