Region Attributes within Geo Object

[chompi]

Original author: [email protected] (July 22, 2011 21:27:01)

The FIPS 10-4 region codes were withdrawn by NIST as a FIPS (Federal Info Processing Standard) in September 2008. Thus the geo.regionfips104 attribute should be dropped. If it’s still in use by some exchanges, it should be sent within bidextensions. Also, what is the standard behind the geo.metro attribute? The sources “Metro Marketing Area” and “MetroCode” are referenced, but I couldn’t find official references to these. If these are vendor specific codes, I don’t think they should be explicitly called out in the standard. If that is the case, they too could be passed within “bidextensions”.

Original issue: http://code.google.com/p/openrtb/issues/detail?id=30