Hey @j---
Looks good mostly. Only question I have is on the language issue. JSON format allows for UTF-8 representation of each of "keys" and "values" in both the Provision and Computed schema. So, what should happen if language is say Japanese in UTF-8, do they pick equivalent English letters? Is SSVC vector only is limited to POSIX locale - basically US-ASCII chars only? Maybe a short note of this would be good to clarify how short notation handles languages.

Vijay

Looks good mostly. Only question I have is on the language issue. JSON format allows for UTF-8 representation of each of "keys" and "values" in both the Provision and Computed schema. So, what should happen if language is say Japanese in UTF-8, do they pick equivalent English letters? Is SSVC vector only is limited to POSIX locale - basically US-ASCII chars only? Maybe a short note of this would be good to clarify how short notation handles languages.

While I agree that i18n of the vector is an issue we should address eventually, it seems like a gap we might note in future work (i.e., #38) for now and then revisit it once we have some engagement from folks who need it. I'm in favor of cutting a new issue for internationalization of SSVC and appending this as one of the items for that issue to address.

Looks good mostly. Only question I have is on the language issue. JSON format allows for UTF-8 representation of each of "keys" and "values" in both the Provision and Computed schema. So, what should happen if language is say Japanese in UTF-8, do they pick equivalent English letters? Is SSVC vector only is limited to POSIX locale - basically US-ASCII chars only? Maybe a short note of this would be good to clarify how short notation handles languages.

While I agree that i18n of the vector is an issue we should address eventually, it seems like a gap we might note in future work (i.e., #38) for now and then revisit it once we have some engagement from folks who need it. I'm in favor of cutting a new issue for internationalization of SSVC and appending this as one of the items for that issue to address.

Cool - we can track it in the "internationalization" bucket.