Deals API 1.0 JSON Schema Unofficial

Decision records ·

D-009 Which codes may pricetype take beyond 0 to 3, when the text says "Exchange-specific auction types can be defined using values 500 and greater"?

Gap Cited on main and at the tag 1.0-202602.

What the schemas do

Any integer of 500 or more, an exchange's own auction type, beside the codes 0 to 3; no code from 4 to 499.

Options

  • vendor-500 Chosen

    Any integer of 500 or more, an exchange's own auction type, beside the codes 0 to 3; no code from 4 to 499.

  • closed

    Only 0 to 3: the sentence permits exchanges to define more but doesn't add them to the list.

Why

The sentence reserves 500 and up for exchanges' own auction types, as AdCOM's lists reserve 500 and up for vendors, so a receiver must accept such a code and may not know it. Codes from 4 to 499 stay unassigned.

What we ask the specification to state

None needed: the range is clear. A list of the codes exchanges use would help a receiver read them.

The specification lines it rests on

Each line is quoted as the record pins it. Expand an item to read the quote.

main

  • Object: Terms, the pricetype row's description: the value list L114 at 3028ddc
    0 (Dynamic (ie. auction type will be provided by request.at attribute in OpenRTB Bid Request)) | 1 (First Price) | 2 (Second Price Plus) | 3 (Fixed Price)

Tag 1.0-202602

  • Object: Terms, the pricetype row's description: the value list L114 at 938a5d1
    0 (Dynamic (ie. auction type will be provided by request.at attribute in OpenRTB Bid Request)) | 1 (First Price) | 2 (Second Price Plus) | 3 (Fixed Price)

What it shapes

main: PriceType, VendorCode

Tag 1.0-202602: PriceType, VendorCode

The record's YAML file