Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

subsectionType definition #93

Open
patmmccann opened this issue Jul 25, 2023 · 2 comments
Open

subsectionType definition #93

patmmccann opened this issue Jul 25, 2023 · 2 comments

Comments

@patmmccann
Copy link
Contributor

patmmccann commented Jul 25, 2023

subsectionType is mentioned here in the core spec

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?

@janwinkler
Copy link

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".

@janwinkler
Copy link

janwinkler commented Nov 3, 2023

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").

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants