Wrong example for TC String Format(Canada)

[barbosamarco4]

https://github.com/InteractiveAdvertisingBureau/Global-Privacy-Platform/blame/95afd796ab2cf32bd99b4b6ae1748702fc051c6e/Sections/Canada/TCF%20EU%20TCF%20CA%20Comparison.md#L1347
Because the Version in the Core String should always be 1 for Canada strings, these example strings should start with a 'B' instead of 'C'

[HeinzBaumann]

The version encoding in the string reflects the TCF version used. Canada is using TCF version 2. Hence the string is correct. The policy version for Canada is version 2.

[barbosamarco4]

I'm talking about the "Version" in the Core String, not the policy version. In the documentation, just below the line where I left my comment it is stated that the version for Canada is 1.

This value is represented by the first letter in the string, hence me saying that it should be a "B" instead of a "C".
Besides this, when creating TCF Canada strings in the IAB Encoder/Decoder the strings always start with a "B", and the Version is locked to 1.

[HeinzBaumann]

This is wrong. The TCF string that Canada is using is TCF format 2 not 1. This is a bug in GPP. Canada never used format version 1 for that matter. @lamrowena please take note!

[barbosamarco4]

This is getting really confusing. My understanding follows what you just stated, but then the documentation contradicts that. Just to make things more clear for me: were you involved with IAB on these standards?

[HeinzBaumann]

Yes, I was the initial author of the TCF v1. Canada joined the TCF when TCF format was at version 2. GPP embeds the Canadian TCF string. Hence the format version should be 2.