FW: Store parsing scheme in OE file header to avoid hard-coding parsers

[DennisMoschina]

Problem

Currently, parsers for OE (OpenEarable) files appear to be hard-coded, which makes the system less flexible and harder to maintain as data formats evolve or new sensor types are added.

Proposed Solution

Store the parsing scheme directly in the OE file header. This would allow:

• Dynamic parser selection based on file content
• Better version management of data formats
• Easier addition of new sensor types or data structures
• Improved backward compatibility

Benefits

• Flexibility: Files would be self-describing and could use different parsing schemes
• Maintainability: Reduces need for code changes when data formats change
• Extensibility: Easier to add new sensor types or recording formats
• Robustness: Prevents parsing errors from format mismatches

Implementation Considerations

• Define a standard format for the parsing scheme metadata in the header. This could use the already defined parse info service implementation
• Ensure backward compatibility with existing OE files
• Document the header format specification
• Update file writing code to include parsing scheme