| CARVIEW |
Navigation Menu
-
Notifications
You must be signed in to change notification settings - Fork 47
GPP Extensions: DE, IA, NE, NH, NJ, TN State Sections #121
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
GPP Extensions: DE, IA, NE, NH, NJ, TN State Sections #121
Conversation
Updates to Section Information and the Section IDs table. Added Section IDs 17-22 for DE, IA, NE, NH, NJ, TN.
Creation of Delaware folder and readme document
Creation of Iowa folder and readme
Creation of Nebraska folder and readme.
Creation of New Hampshire folder and readme.
Creation of New Jersey folder and readme.
Creation of the Tennessee folder and readme.
…ication.md Creation of Delaware technical specification file.
…ion.md Creation of Iowa technical specification file
…ication.md Edited GPC table to have correct formatting.
…ication.md Creation of Nebraska technical specification file.
…pecification.md Creation of New Hampshire technical specification file.
…ification.md Creation of New Jersey technical specification file.
…fication.md Creation of Tennessee technical specification file.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please consider moving transgender to number 9, shifting 6-9 up one each. See the same comment for Delaware for background on why.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please consider moving transgender to number 9, shifting 6-9 up one each.
Background: The way Prebid implements GPP state strings is to normalize from state to national, so by sticking entries randomly in the "normal 8" categories it causes more normalization work than necessary. it would be more convenient for implementation if the first 8 could be left in the same order for every state from here on out. In this case, since 10 (finance) is going to get mapped to SID 7 sensitive data 10, it would be convenient to transgender at 9.
See prebid/Prebid.js#11978 for the most recent 4 normalizations. Oregon would have been easier had the first 8 sensitive data slots at been the same as SID7.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Any feedback from the committee on this suggestion?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@bretg public comment ended last Thursday, 9/5. The Global Privacy Working Group will be addressing comments and working towards finalization in the next few meetings - our next scheduled meeting is this Thursday, 9/12. We'll confirm once this is addressed and what actions are taken. thanks!
…ification.md Revised order of Sensitive Data field to address public comment feedback by moving transgender to number 9, shifting 6-9 up one each.
…ication.md Revised order of Sensitive Data field to address public comment feedback by moving transgender to number 9, shifting 6-9 up one each.
|
@bretg updates have been included for NJ and DE with the commits on this thread |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Excellent - thanks @jaredmoscow - that makes the mapping much cleaner.
lamrowena
changed the title
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@jaredmoscow - this file seems to be missing AdditionalDataProcessingConsent... was that intentional?
Labels
3 participants
Summary
This pull request introduces updates for GPP extensions with new state sections for Delaware, Iowa, Nebraska, New Hampshire, New Jersey, and Tennessee. These additions are essential for accommodating evolving privacy regulations. There are also updates to the Section Information, reflecting the addition of these new States.
Details
Changes Overview
Next Steps
Your feedback and suggestions are highly appreciated during this public comment period. We encourage thorough review and constructive criticism to refine the implementation further. Once public comment is complete and the feedback is incorporated, we will proceed with merging these changes into the main branch.
Public comment closed on September 5th.