GPP Extensions: FL, MT, OR, TX State Sections for Public Comment

jaredmoscow commented 4 months ago

Summary

This pull request introduces updates for GPP extensions with new state sections for Florida, Montana, Oregon, and Texas. These additions are essential for accommodating evolving privacy regulations. Additionally, there are updates to the Section Information, reflecting the addition of these new States.

Details

GPP Extensions & New State Sections: This PR includes the creation of dedicated folders and README files for each of the mentioned states. The technical specifications for each state aim to aid with GPP support and help implementers stay ahead of regulatory requirements.
Public Comment Period: It's important to note that this PR is open for public comment until Monday, June 10th. Feedback can be provided either by directly adding comments to this PR or by sending an email to support@iabtechlab.com.
Commit Overview: The PR comprises a total of 9 commits, each focusing on specific tasks. Commit messages provide insight into each change noted in this review process.

Changes Overview

Florida: Creation of the FL State Section folder along with its README file and Florida technical specification.
Montana: Introduction of the MT State Section Folder and README.md for Montana, along with the GPP extension based on Montana's privacy technical specification.
Oregon: Similar to Montana, the creation of the Oregon folder and its respective README file, accompanied by the GPP extension for Oregon's technical specification.
Texas: Creation of the TX State Section folder, including its README.md, and the GPP extension adhering to Texas's technical specification.
Section Information Update: In addition to state-specific section updates, additions have been made to the Section Information.md file, including new rows for these four States to ensure coverage.

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 Monday, June 10th.

Mokujinn commented 3 months ago

Is this using the wrong GPP Type field for the bitfields? Previously they were N-Bitfield(2, x), because they were using two bits for each data activity.

Ran through the state strings, can you confirm that there will be no changes to the US National string given there aren't any new fields or options (or options added to existing fields).

jaredmoscow commented 2 months ago

Public Comment closed on Monday, June 10th. Updates have been made accordingly to the four state sections incorporating feedback from the period. Each state commit update includes the following:

Consent Field Order Updates for Sensitive Data and Known Child Consents:
- 0 = N/A
- 1 = No Consent
- 2 = Consent
- This matches the existing state structure.
Updated N-Bitfield Range for Sensitive Data and Known Child Consents.
Removed 'N/A' from the MSPA Covered Transaction field.
Revised Text in 'About this document'.

Additionally, the Florida section received one more update:

Revised Text in 'Section Information'.

Each comment has been addressed and resolved to prepare the PR for merge.

jaredmoscow commented 2 months ago

On Thursday, 6/20, the Global Privacy Working Group voted unanimously to finalize these commits with the addition of a single edit to each State section. This edit added the language "of the spec" to the Section Information are in each distinct State Section.

kyleaedwards commented 2 months ago

@jaredmoscow Is the documentation correct that the Consent and No Consent values are reversed for the new AdditionalDataProcessingConsent fields?

jaredmoscow commented 2 months ago

@kyleaedwards good catch! this was not discussed during working group review and public comment. However, it does make sense to switch for consistency. Here is the PR to track: https://github.com/InteractiveAdvertisingBureau/Global-Privacy-Platform/pull/114

We'll merge to main ASAP. Thanks!

kyleaedwards commented 2 months ago

@kyleaedwards good catch! this was not discussed during working group review and public comment. However, it does make sense to switch for consistency. Here is the PR to track: #114

We'll merge to main ASAP. Thanks!

Thanks for clarifying and jumping on this so fast!

InteractiveAdvertisingBureau / Global-Privacy-Platform