Resolves Issue 126 #127
Resolves Issue 126 #127
Conversation
| </tr> | ||
| <tr> | ||
| <td>NumPubRestrictions</td> | ||
| <td>Int(12)</td> | ||
| <td>Number of restriction records to follow.<br></br>Value is required even if it is <code>0</code></td> | ||
| <td>Number of restriction records to follow.<br>Value is required even if it is <code>0</code></td> |
There was a problem hiding this comment.
needs to be removed and replaced with one field of type ArrayOfRanges (replaces NumPubRestrictions, PurposeID, RestrictionType, PubRestrictionEntry)
There was a problem hiding this comment.
Fixed, @janwinkler please take a look as the new section.
There was a problem hiding this comment.
@HeinzBaumann maybe just clarification on the last line:
"A single or range of Vendor ID(s) who the publisher has designated as restricted under the purpose id."
--> "A list of Vendor ID(s) who the publisher has designated as restricted under the purpose id encoded as bitmask or ranges."
There was a problem hiding this comment.
Maybe one thing to highlight to implementers (implementers guide?) is that the output of the JS API for the restrictions field is not exactly the same as what they know from the __tcfapi output for the restrictions.
There was a problem hiding this comment.
Thanks! I made this modification.
There was a problem hiding this comment.
@janwinkler if this is now okay from your end, please approve this PR.
This PR addresses several issues found in the EEA Section spec and brings this spec to date with the latest TCF 2.2 specification.