added version field as optional to track file/design version tags

[fzahle]

I've made the field optional to avoid making a backward incompatible change.

[ptrbortolotti]

what about the entry windIO_version?

[fzahle]

what about the entry windIO_version?

Maybe the description is misleading. the intention is to allow tagging the version of the turbine design.

[ptrbortolotti]

that was the intention of windIO_version, or am I missing something?

[fzahle]

that was the intention of windIO_version, or am I missing something?

windIO_version would be 2.1 for example, referring to what version of the windIO schema the file uses, making it easier to convert yaml older yaml files.

[ptrbortolotti]

and what would version do then?

[fzahle]

I can see this field may not be super intuitive to understand. There's also the issue that if a user splits the yaml sub sections into other files, they won't strictly be versioned anyway. Use case is that we for example in the windIO repo maintain copies of the IEA RWTs and that it's error prone and difficult to check what version of the turbine design the file has.

We could also call it turbine_version or model_version or something else to make it more clear that it's the version of the turbine and not windIO the tag is used for.