Open patmmccann opened 1 year ago
Here (https://github.com/InteractiveAdvertisingBureau/Global-Privacy-Platform/blob/main/Sections/Canada/GPPExtension%3A%20IAB%20Canada%20TCF.md) it is still called "SegmentType" with value 3. I think one of the pull requests was to update all the terms from "segment" to "section/subsection".
What is an example type 0 core subsection as mentioned in the, for example, Colorado section spec ? In the core subsection the subsectiontype is omitted since the core subsection always has to be the first in the string and needs no further explanation. Anyhow, I also think at least in the result of the "getSection" command (or the pingReturn.parsedSections) it would be useful to always add the subsection property even to the core.
Can we get an enumerated list of subsection types and can we assume that is subsectionType is 1 it is always a GPC subsection? Yes please! :-) Since 0, 1 and 3 are used, maybe lets assign 1-10 for "reusable subsections" (make section 3 a generic reusable) and contiue at 11 with the subsections that are specific to any section.
Can we assume that the subsections cannot collide in name? What do you mean with name? E.g. TCF EU and TCF CA will both have a subsection 3 with the same name ("Publisher Purposes Subsection").
subsectionType is mentioned here in the core spec https://github.com/InteractiveAdvertisingBureau/Global-Privacy-Platform/blob/c334e3c860e7edb60a06003288256f81bac9969f/Core/CMP%20API%20Specification.md?plain=1#L623 but is not mentioned in the Canada spec. What is type 3?
What is an example type 0 core subsection as mentioned in the, for example, Colorado section spec ?
Can we get an enumerated list of subsection types and can we assume that is subsectionType is 1 it is always a GPC subsection?
Can we assume that the subsections cannot collide in name?
Can it be in the spec if so?