In the meantime, if we wanted to see increased standardisation of this data, we could add 360G's suggestions as an optional feature to allow users to declare the scheme via the closed codelist, while permitting publishers to keep using the current model
Context/360 feedback - We would recommend defining a closed list of schemes and maintaining that list to reflect changing needs, rather than being permissive of any scheme being used, which makes the data harder to map and compare.
Decision to be made here or are we talking 3.1?
In the meantime, if we wanted to see increased standardisation of this data, we could add 360G's suggestions as an optional feature to allow users to declare the scheme via the closed codelist, while permitting publishers to keep using the current model
Context/360 feedback - We would recommend defining a closed list of schemes and maintaining that list to reflect changing needs, rather than being permissive of any scheme being used, which makes the data harder to map and compare.