Thank you for the clarification. When you guys migrate to OpenRTB 2.3 next year, may I suggest versioning the documentation and making PDFs available as well? If we implement something against the current version of the spec and want to review our logic a month later after the spec changes, we cannot. Reviewing the rationale for the implementation strategy against the version of the spec used (at that time) is not possible with this model.
It looks like your documentation exists on some computer somewhere as an HTML file hooked up in Dropbox, which automatically creates a new version when a change occurs. I’m not being inflammatory - I’m just letting you know your team has the ability to review the history of your HTML documentation.