AdCOM 1.0 JSON Schema Unofficial

Decision records ·

D-005 What do the statements in AdCOM's list sections become, when they say what a code means or how a list is used?

Gap Cited on main and at the tag AdCOM1.0-202607.

What the schemas do

Informative: each says what a code means, which the code's label carries, or how a list is used, which no value of the list can show.

Options

  • informative Chosen

    Informative: each says what a code means, which the code's label carries, or how a list is used, which no value of the list can show.

  • obligations

    An obligation on the party that sends or renders a code, such as the player that plays an instream placement with its sound on.

  • rules

    A rule per statement, checked on payloads.

Why

A value of a list is one code, and none of these statements constrains which code a sender writes. Most say what a code means, such as how an instream placement plays its sound, and that sentence is part of the code's label, which the vocabulary's description keeps. The rest say how a list is used, such as which attribute carries it, or describe the list itself, as "required by an ad" does in its ordinary sense. None of them can be checked on a code alone, so none becomes a rule. Several bind a party, as "Instream video must be set to sound on" binds the player, and several constrain an object's attribute, as the native assets' recommended lengths do; each such obligation or rule belongs to the attribute that carries the code, which the objects phase maps, and that phase revisits these statements. In a registry of codes, they are what the codes mean.

What we ask the specification to state

Keep each code's definition to what the code means, and move a requirement on the party that sends or renders it, such as "Instream video must be set to sound on by default", to the attribute that carries the code, where an implementation can check it.

The specification lines it rests on

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

main

  • List: API Frameworks, a requirement L2841 at 26c59ba
    The following table is a list of API frameworks either supported by a placement or required by an ad.
  • List: Audit Status Codes, a requirement L2902 at 26c59ba
    A recommendation cannot be made to use this ad, but vendors' policies may override.
  • List: Audit Status Codes, a requirement L2906 at 26c59ba
    Subject to vendors' policies, it can be recommended for use.
  • List: Audit Status Codes, a requirement L2906 at 26c59ba
    However, once the audit has been completed, its status will change and it may or may not be approved for continued use.
  • List: Audit Status Codes, a requirement L2910 at 26c59ba
    Note, however, that some attributes (e.g., adomain, cat, attr, etc.) may have been changed in the process by the auditor.
  • List: Audit Status Codes, a requirement L2918 at 26c59ba
    Changed; Resubmission Requested: A version of the ad has been detected in use that is materially different from the version that was previously audited, which may result in rejection during use until the ad is resubmitted for audit and approved.
  • List: Content Contexts, a requirement L3110 at 26c59ba
    The following table lists the various options for indicating the type of content being used or consumed by the user in which ads may appear.
  • List: Display Context Types, a requirement L3430 at 26c59ba
    The following table lists the types of context in which a native ad may appear (i.e., the type of content surrounding the ad on the page).
  • List: Display Context Types, a requirement L3430 at 26c59ba
    This is intended to denote primary content although other content may also appear on the page.
  • List: Display Context Types, a requirement L3483 at 26c59ba
    - Product reviews site primarily, which may sell product secondarily.
  • List: Display Placement Types, a requirement L3494 at 26c59ba
    The following table lists the general types of display placements; the locations where a native ad may be shown in relationship to the surrounding content.
  • List: DOOH Venue Taxonomies, a requirement L3554 at 26c59ba
    The following table contains a list of supported taxonomies describing the locations and contexts in which Out-Of-Home media may be experienced.
  • List: Event Tracking Methods, a requirement L3598 at 26c59ba
    Vendor specific codes may include custom measurement companies (e.g., Moat, Doubleverify, IAS, etc.).
  • List: Event Types, a requirement L3622 at 26c59ba
    Scripts that are performing measurement should be deployed at the "loaded" event.
  • List: Event Types, a requirement L3631 at 26c59ba
    Creative may be pre-cached or pre-loaded; prior to initial rendering.
  • List: Expandable Directions, a requirement L3658 at 26c59ba
    The following table lists the directions in which an expandable ad may expand, given the positioning of the ad unit on the page and constraints imposed by the content.
  • List: ID Match Methods, a requirement L3746 at 26c59ba
    It should be used on conjunction with the mm attribute in Object: EID of OpenRTB 2.x.
  • List: Linearity Modes, a requirement L3827 at 26c59ba
    This corresponds to the required type of VAST response, where a linear response is VAST containing video assets, and non-linear is a VAST response (typically) containing a banner/overlay.
  • List: Native Data Asset Types, a requirement L3895 at 26c59ba
    Size recommendations are noted as "maximum length of at least", which means the publisher or supply platform should support a maximum length of at least this value and the buying platform knows that a string of this size should be accepted.
  • List: Native Data Asset Types, a requirement L3904 at 26c59ba
    sponsored: "Sponsored By" message which should contain the brand name of the sponsor.
  • List: Native Data Asset Types, a requirement L3904 at 26c59ba
    Recommended maximum length of at least 25 characters.
  • List: Native Data Asset Types, a requirement L3908 at 26c59ba
    Long text lengths may be truncated or ellipsed when rendered.
  • List: Native Data Asset Types, a requirement L3908 at 26c59ba
    Recommended maximum length of at least 140 characters.
  • List: Native Data Asset Types, a requirement L3912 at 26c59ba
    Recommended integer range of 0-5.
  • List: Native Data Asset Types, a requirement L3924 at 26c59ba
    Value should include currency symbol in localized format (e.g., "$10").
  • List: Native Data Asset Types, a requirement L3928 at 26c59ba
    Value should include currency symbol in localized format (e.g., "$8.50").
  • List: Native Data Asset Types, a requirement L3948 at 26c59ba
    Recommended maximum length of at least 15 characters.
  • List: Native Image Asset Types, a requirement L3959 at 26c59ba
    Size recommendations are noted as "maximum height or width of at least", which means the publisher or supply platform should support a maximum height or width of at least this value and the buying platform knows that an image of this size should be accepted.
  • List: Native Image Asset Types, a requirement L3974 at 26c59ba
    At least one of 2 size variants required: Small: Maximum height at least 200 DIPS; maximum width at least 200, 267, or 382 DIPS (i.e., aspect ratios of 1:1, 4:3, or 1.91:1, respectively).
  • List: Plcmt Subtypes - Video, a requirement L4213 at 26c59ba
    Instream video must be set to “sound on” by default at player start, or have explicitly clear user intent to watch the video content.
  • List: Plcmt Subtypes - Video, a requirement L4213 at 26c59ba
    While there may be other content surrounding the player, the video content must be the focus of the user’s visit.
  • List: Plcmt Subtypes - Video, a requirement L4213 at 26c59ba
    It should remain the primary content on the page and the only video player in-view capable of audio when playing.
  • List: Plcmt Subtypes - Video, a requirement L4213 at 26c59ba
    If the player converts to floating/sticky subsequent ad calls should accurately convey the updated player size.
  • List: Plcmt Subtypes - Video, a requirement L4217 at 26c59ba
    Accompanying content should only start playback upon entering the viewport.
  • List: Plcmt Subtypes - Video, a requirement L4217 at 26c59ba
    It may convert to a floating/sticky player as it scrolls off the page.
  • List: Plcmt Subtypes - Video, a requirement L4221 at 26c59ba
    During playback, it must be the primary focus of the page and take up the majority of the viewport and cannot be scrolled out of view.
  • List: Plcmt Subtypes - Video, a requirement L4229 at 26c59ba
    While there may be other content surrounding the player, the video content must be the focus of the user’s visit.
  • List: Plcmt Subtypes - Video, a requirement L4229 at 26c59ba
    It should remain the primary content on the page and the only video player in-view.
  • List: Plcmt Subtypes - Video, a requirement L4237 at 26c59ba
    While there may be other content surrounding the player with the overlay, the player with the overlay must be the focus of the user’s visit.
  • List: Plcmt Subtypes - Video, a requirement L4237 at 26c59ba
    It should remain the primary content on the page and the primary video player in-view.
  • List: Plcmt Subtypes - Video, a requirement L4241 at 26c59ba
    While there may be other content surrounding the player with the squeezeback, the player with the squeezeback must be the focus of the user’s visit.
  • List: Plcmt Subtypes - Video, a requirement L4241 at 26c59ba
    It should remain the primary content on the page and the primary video player in-view.
  • List: Plcmt Subtypes - Video, a requirement L4245 at 26c59ba
    While there may be other content surrounding the player with the in-scene ad, the player with the in-scene ad must be the focus of the user’s visit.
  • List: Plcmt Subtypes - Video, a requirement L4245 at 26c59ba
    It should remain the primary content on the page and the primary video player in-view.

Tag AdCOM1.0-202607

  • List: API Frameworks, a requirement L2841 at d67a6a8
    The following table is a list of API frameworks either supported by a placement or required by an ad.
  • List: Audit Status Codes, a requirement L2902 at d67a6a8
    A recommendation cannot be made to use this ad, but vendors' policies may override.
  • List: Audit Status Codes, a requirement L2906 at d67a6a8
    Subject to vendors' policies, it can be recommended for use.
  • List: Audit Status Codes, a requirement L2906 at d67a6a8
    However, once the audit has been completed, its status will change and it may or may not be approved for continued use.
  • List: Audit Status Codes, a requirement L2910 at d67a6a8
    Note, however, that some attributes (e.g., adomain, cat, attr, etc.) may have been changed in the process by the auditor.
  • List: Audit Status Codes, a requirement L2918 at d67a6a8
    Changed; Resubmission Requested: A version of the ad has been detected in use that is materially different from the version that was previously audited, which may result in rejection during use until the ad is resubmitted for audit and approved.
  • List: Content Contexts, a requirement L3110 at d67a6a8
    The following table lists the various options for indicating the type of content being used or consumed by the user in which ads may appear.
  • List: Display Context Types, a requirement L3430 at d67a6a8
    The following table lists the types of context in which a native ad may appear (i.e., the type of content surrounding the ad on the page).
  • List: Display Context Types, a requirement L3430 at d67a6a8
    This is intended to denote primary content although other content may also appear on the page.
  • List: Display Context Types, a requirement L3483 at d67a6a8
    - Product reviews site primarily, which may sell product secondarily.
  • List: Display Placement Types, a requirement L3494 at d67a6a8
    The following table lists the general types of display placements; the locations where a native ad may be shown in relationship to the surrounding content.
  • List: DOOH Venue Taxonomies, a requirement L3554 at d67a6a8
    The following table contains a list of supported taxonomies describing the locations and contexts in which Out-Of-Home media may be experienced.
  • List: Event Tracking Methods, a requirement L3598 at d67a6a8
    Vendor specific codes may include custom measurement companies (e.g., Moat, Doubleverify, IAS, etc.).
  • List: Event Types, a requirement L3622 at d67a6a8
    Scripts that are performing measurement should be deployed at the "loaded" event.
  • List: Event Types, a requirement L3631 at d67a6a8
    Creative may be pre-cached or pre-loaded; prior to initial rendering.
  • List: Expandable Directions, a requirement L3658 at d67a6a8
    The following table lists the directions in which an expandable ad may expand, given the positioning of the ad unit on the page and constraints imposed by the content.
  • List: ID Match Methods, a requirement L3746 at d67a6a8
    It should be used on conjunction with the mm attribute in Object: EID of OpenRTB 2.x.
  • List: Linearity Modes, a requirement L3827 at d67a6a8
    This corresponds to the required type of VAST response, where a linear response is VAST containing video assets, and non-linear is a VAST response (typically) containing a banner/overlay.
  • List: Native Data Asset Types, a requirement L3895 at d67a6a8
    Size recommendations are noted as "maximum length of at least", which means the publisher or supply platform should support a maximum length of at least this value and the buying platform knows that a string of this size should be accepted.
  • List: Native Data Asset Types, a requirement L3904 at d67a6a8
    sponsored: "Sponsored By" message which should contain the brand name of the sponsor.
  • List: Native Data Asset Types, a requirement L3904 at d67a6a8
    Recommended maximum length of at least 25 characters.
  • List: Native Data Asset Types, a requirement L3908 at d67a6a8
    Long text lengths may be truncated or ellipsed when rendered.
  • List: Native Data Asset Types, a requirement L3908 at d67a6a8
    Recommended maximum length of at least 140 characters.
  • List: Native Data Asset Types, a requirement L3912 at d67a6a8
    Recommended integer range of 0-5.
  • List: Native Data Asset Types, a requirement L3924 at d67a6a8
    Value should include currency symbol in localized format (e.g., "$10").
  • List: Native Data Asset Types, a requirement L3928 at d67a6a8
    Value should include currency symbol in localized format (e.g., "$8.50").
  • List: Native Data Asset Types, a requirement L3948 at d67a6a8
    Recommended maximum length of at least 15 characters.
  • List: Native Image Asset Types, a requirement L3959 at d67a6a8
    Size recommendations are noted as "maximum height or width of at least", which means the publisher or supply platform should support a maximum height or width of at least this value and the buying platform knows that an image of this size should be accepted.
  • List: Native Image Asset Types, a requirement L3974 at d67a6a8
    At least one of 2 size variants required: Small: Maximum height at least 200 DIPS; maximum width at least 200, 267, or 382 DIPS (i.e., aspect ratios of 1:1, 4:3, or 1.91:1, respectively).
  • List: Plcmt Subtypes - Video, a requirement L4213 at d67a6a8
    Instream video must be set to “sound on” by default at player start, or have explicitly clear user intent to watch the video content.
  • List: Plcmt Subtypes - Video, a requirement L4213 at d67a6a8
    While there may be other content surrounding the player, the video content must be the focus of the user’s visit.
  • List: Plcmt Subtypes - Video, a requirement L4213 at d67a6a8
    It should remain the primary content on the page and the only video player in-view capable of audio when playing.
  • List: Plcmt Subtypes - Video, a requirement L4213 at d67a6a8
    If the player converts to floating/sticky subsequent ad calls should accurately convey the updated player size.
  • List: Plcmt Subtypes - Video, a requirement L4217 at d67a6a8
    Accompanying content should only start playback upon entering the viewport.
  • List: Plcmt Subtypes - Video, a requirement L4217 at d67a6a8
    It may convert to a floating/sticky player as it scrolls off the page.
  • List: Plcmt Subtypes - Video, a requirement L4221 at d67a6a8
    During playback, it must be the primary focus of the page and take up the majority of the viewport and cannot be scrolled out of view.
  • List: Plcmt Subtypes - Video, a requirement L4229 at d67a6a8
    While there may be other content surrounding the player, the video content must be the focus of the user’s visit.
  • List: Plcmt Subtypes - Video, a requirement L4229 at d67a6a8
    It should remain the primary content on the page and the only video player in-view.
  • List: Plcmt Subtypes - Video, a requirement L4237 at d67a6a8
    While there may be other content surrounding the player with the overlay, the player with the overlay must be the focus of the user’s visit.
  • List: Plcmt Subtypes - Video, a requirement L4237 at d67a6a8
    It should remain the primary content on the page and the primary video player in-view.
  • List: Plcmt Subtypes - Video, a requirement L4241 at d67a6a8
    While there may be other content surrounding the player with the squeezeback, the player with the squeezeback must be the focus of the user’s visit.
  • List: Plcmt Subtypes - Video, a requirement L4241 at d67a6a8
    It should remain the primary content on the page and the primary video player in-view.
  • List: Plcmt Subtypes - Video, a requirement L4245 at d67a6a8
    While there may be other content surrounding the player with the in-scene ad, the player with the in-scene ad must be the focus of the user’s visit.
  • List: Plcmt Subtypes - Video, a requirement L4245 at d67a6a8
    It should remain the primary content on the page and the primary video player in-view.

The record's YAML file