Investigate converting XTCE to Electronic Data Sheets format

[medley56]

Summary

EDS are used by some missions to describe packet structures. EDS is advertised as a similar configuration mechanism to XTCE in that it describes packet structures (confirm this understanding).

Driving Requirements

1. Build an example of converting an XTCE document to EDS, similar to our CSV to XTCE converter but the other direction. This should demonstrate at a basic level what is required to map between these two formats (XTCE and EDS).
2. Build an example of starting from an EDS file and building an XTCE definition from it to parse packets. This can be a contrived, simple example to demonstrate the pattern for creating a packet definition in memory from an EDS file.
3. Analyze and produce a summary report on the feasibility and complexity of building a conversion system between EDS and XTCE into the Space Packet Parser library and supporting EDS-based configuration (via parsing EDS to an XTCE definition in memory). Consider the scope of each data model and the fidelity of mapping between the two.

Resources

https://ccsds.org/Pubs/876x0b1.pdf

[medley56]

@ivanperez-keera It looks like there is a potential to map between XTCE and EDS. From our conversation, it sounds like much of your tooling uses EDS, but missions provide XTCE, so you would like to convert from mission-provided XTCE to EDS that you can use.

I think my preferred solution is to provide an example of parsing an XTCE document and serializing EDS, but to refrain from adding full EDS support to Space Packet Parser.