Supported encoding for string values

[erikbosch]

VSS does not rely specify what character encodings we support like UTF-8, UTF-16, ASCII, ...

We need to discuss:

• What shall we specify in VSS, what do we leave for APIs
• AUTOSAR use UTF-8
• We say in *.vspec files that we support what is allowed by Yaml

[erikbosch]

MoM:

• Sebastian: Sounds more like an API topic
• Erik: But COVESA could have recommendations on what to use in APIs
• Erik: What does OpenAPI/AsyncAPI propose/recommended
• Adnan: UTF-8 and UTF-16. What is allowed as VSS names is more important
• Nick: If everything can be expressed in UTF-8 , shall that be minimum req for interoperability