You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In the OpenRTB Mobile specification, we followed an informal convention of prepending “b” or “w” to attribute names to indicate that they are block lists or white lists, respectively, (i.e., restrictions rather than just informative data). For the most part, those names are carried over into this spec. However, there are several new block or white list attributes in this spec and I recommend that they follow the same convention.
The ones that jump out at me are as follows with the proposed names in parentheses: banner.atype (wtype), banner.expandable (wexpandable or perhaps just wexpand), banner.format (wformat), video.format (wformat), video.playbackmethod (wplaybackmethod), and video.delivery (wdelivery).
Original author: [email protected] (July 22, 2011 21:08:38)
In the OpenRTB Mobile specification, we followed an informal convention of prepending “b” or “w” to attribute names to indicate that they are block lists or white lists, respectively, (i.e., restrictions rather than just informative data). For the most part, those names are carried over into this spec. However, there are several new block or white list attributes in this spec and I recommend that they follow the same convention.
The ones that jump out at me are as follows with the proposed names in parentheses: banner.atype (wtype), banner.expandable (wexpandable or perhaps just wexpand), banner.format (wformat), video.format (wformat), video.playbackmethod (wplaybackmethod), and video.delivery (wdelivery).
Original issue: http://code.google.com/p/openrtb/issues/detail?id=22
The text was updated successfully, but these errors were encountered: