Original author: jim.but...@nexage.com (July 22, 2011 21:31:59)
Referring to the reference data for Ad Position (Section 6.4) and No-Bid Reason (Section 6.6), each has a value 0 that means “unknown”. However, a broad concept throughout OpenRTB attributes, other than block or white lists, is that an omitted optional attribute means “unknown”. For this reason, other attributes do not have an explicit value to mean “unknown”. For consistency, these should be removed as well.
The 0 = unknown value existed in the OpenRTB Mobile specification for No-Bid reason, but since an exchange would likely also interpret an undefined value as “unknown”, this should not cause a backward compatibility issue.
Original issue: http://code.google.com/p/openrtb/issues/detail?id=35
Original author: jim.but...@nexage.com (July 22, 2011 21:31:59)
Referring to the reference data for Ad Position (Section 6.4) and No-Bid Reason (Section 6.6), each has a value 0 that means “unknown”. However, a broad concept throughout OpenRTB attributes, other than block or white lists, is that an omitted optional attribute means “unknown”. For this reason, other attributes do not have an explicit value to mean “unknown”. For consistency, these should be removed as well.
The 0 = unknown value existed in the OpenRTB Mobile specification for No-Bid reason, but since an exchange would likely also interpret an undefined value as “unknown”, this should not cause a backward compatibility issue.
Original issue: http://code.google.com/p/openrtb/issues/detail?id=35