XSD Schema versioning

What is the requested feature?
Add versioning to the XSD schema.
There are few ways to do it (summary), more or less standard.
So I would like to open the discussion.

I put aside the result of the simulation as out of scope.
I only want to be sure that the objects and their parameters are valid to start a simulation.

Is your request related to a specific problem?
I want to identify a revision of GEOS' code corresponding to the xsd schema I have used to validate a deck
My point is: given a deck and the xsd schema validating it, I should be able to retrieve the code that runs this simulation to compile it and run it again.
I am also wondering:

• Should the deck be sufficient ?
• Should the xsd allow evolving: if v0 of the schema validates my deck and v0 is a valid subset of v10 of the schema, should I be able to start the simulation only by schema validation ?

Describe the solution you'd like
I am open to discussions. Each solution has its pros and cons.

Describe alternatives you've considered
save the commit hash somewhere (?)

Additional context
n.a.