Idea: what about proto de/ser?

Disclaimer: Sorry if this is not how you want ideas/challenges to be communicated, if this is wrong then how would I propose an idea? I couldn't find anything about this in your contributing guidelines.

Hey, I love your contributions to the open-source world. We're adopting wasmcloud in our organization but we have a problem.

We have to model for both external users and internal users, i.e., internal = WIT, external = proto. And modelling two places doesn't scale well, version-wise.

My wish would be:

1. Model in proto / wit
2. -> wit + proto
3. git push to "A"
4. world.wit (uses A.wit record through deps.toml)
5. further define wit with dependency to the generated records from 2 and 3
6. De/ser thought "A". proto but able to somehow convert to Wit records.
7. Push to some stream as proto

Do you guys see any solutions you know, or is this thought of and avoided? If so, why?

Non sono indicati file, test o punti di ingresso. Inizia trasformando il workflow proto/WIT proposto in un design circoscritto, includendo quale modello è autorevole e quali comportamenti di serializzazione/deserializzazione e degli stream devono essere supportati; il lavoro è completato quando esistono un piano di implementazione concordato e criteri di accettazione.

Scritto dal modello di indicizzazione a partire dal testo della issue.