Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

buyeruid name confusing in section "3.2.13: Object: User" (at least in version 2.3) #19

Open
tjk opened this issue Aug 12, 2015 · 3 comments

Comments

@tjk
Copy link

tjk commented Aug 12, 2015

Haven't checked the other specs, but at least in 2.3 FINAL, there seems to be a typo -- it is unclear whether the User object contains a buyerid or buyeruid field (examples say one thing, table says another).

I've been told the actual field is buyeruid, but it would be nice to clean up the specification.

@MelissaIAB
Copy link

This was fixed in OpenRTB 2.3.1. http://www.iab.net/media/file/OpenRTB_API_Specification_Version_2_3_1.pdf

From: TJ Koblentz [mailto:notifications@github.com]
Sent: Wednesday, August 12, 2015 1:51 PM
To: openrtb/OpenRTB OpenRTB@noreply.github.com
Subject: [OpenRTB] buyeruid name confusing in section "3.2.13: Object: User" (at least in version 2.3) (#19)

Haven't checked the other specs, but at least in 2.3 FINAL, there seems to be a typo -- it is unclear whether the User object contains a buyerid or buyeruid field (examples say one thing, table says another).

I've been told the actual field is buyeruid, but it would be nice to clean up the specification.


Reply to this email directly or view it on GitHubhttps://github.com//issues/19.

@tjk
Copy link
Author

tjk commented Aug 12, 2015

Go figure (might make sense to retroactively fix old spec documents?)! Thanks for the quick reply.

@tjk
Copy link
Author

tjk commented Aug 12, 2015

(I'm leaving this issue open only because I think old specifications should be correct, but feel free to close if you disagree)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants