Canada section libarary (OptimizedIntRange) does not match the spec (OptimizedRange)

[TheloniousSF]

The Canada section specification says to use OptimizedRange but the actual library is using OptimizedIntRange. The library should be updated to match specification.

Specification

The Javascript library uses the same encoding as the Java one.

[noirotm]

If both libraries are indeed fixed, what will happen to existing GPP strings in the wild?
Decoding those will most likely fail, meaning that consent checking will be generally broken for code using the fixed version until all wrong GPP strings are organically replaced with correct ones through CMPs.

IMHO a sensible migration plan needs to be implemented:

1. Fix the spec to retroactively acknowledge the difference with the reference implementations
2. Create a TCF CA v2 section which makes it clear the underlying type needs to be updated to the "correct" one, and will unfortunately break compatibility with v1. This will be a similar situation with what happened with the USNAT section.
3. Implementers must now support v1 and v2 until it's safe to deprecate v1.

Thoughts?