D-016 "1.0" covers nearly eight years of changes, the tags are named three ways, and the last tag isn't `main`. Which revision of AdCOM does the registry rest on?

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

What the schemas do

main at a pinned commit by default, and the last tag as a second input; every release names its commit, and a comparison of the two shows how they differ.

Options

main-and-tag Chosen
main at a pinned commit by default, and the last tag as a second input; every release names its commit, and a comparison of the two shows how they differ.
tag-only
The last tag alone.
main-only
main alone.

Why

The last change log entry and the document date are March 2022, while the text has changed many times since, and nothing in the text names a release. main is what GitHub shows and what other specifications link, and the last tag is the last revision AdCOM itself marked. Building both, and naming the commit in every release, makes the choice visible instead of silent. Their lists are the same; they differ only in the Content object's table, whose renamed attributes the tag still carries and main reverted, with three rows in another order and int where main writes integer. AdCOM's develop branch holds further list changes that neither carries.

What we ask the specification to state

Name every release one way, as 1.0-YYYYMM, tag every change to a list, and keep the change log current, so that an implementation can say which revision of the lists it holds. Today domainver: "1.0" can't tell a receiver which codes the sender knows, and OpenRTB 2.6 links plcmt to the develop branch, which no release names.

The specification lines it rests on

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

main

Appendix B: Change Log, concept row 1 L4596 at 26c59ba
1.0 | March 2022 | Updates to support OpenRTB 2.6 release and keep 2.x/AdCOM in sync Added Pod Bidding features, rqddurs, poddur, podid, podseq, mincmppersec, slotinpod to AudioPlacement and VideoPlacement objects. Added Device.langb and Content.langb to support IETF BCP 47 Fixed eids typo so that it is an object array instead of object Added network and channel objects Deprecated yob and gender Added kwarray as preferred format to keywords Added new playback method, continuousplayback Added device type ooh Added new lists to support pod bidding; Ad Sequence and Pod Sequence Added new list to support User-Agent Source Added UserAgent and BrandVersion objects to support User Agent Client Hints
Appendix B: Change Log, concept row 2 L4613 at 26c59ba
1.0 | August 2021 | Added expdir to VideoPlacement: Support for indicating permitted expansion direction for video ads. Added overlaydir to VideoPlacement and AudioPlacement: Support for indicating permitted expansion direction for video and audio ads overlays. SIMID 1.1: SIMID 1.1 has been added to the API frameworks list. Expansion directions: "Resize/Minimize (make smaller)" has been added to the list of expanding directions. Definition of linearity: In the linearity modes list and the linear field in the VideoPlacement object, text has been revised to clarify that linearity corresponds to expected VAST response and is not an indication of in-stream vs out-stream. Category taxonomies list updated: The category taxonomies list was updated with the latest IAB taxonomies. The description of the list was expanded to note that it includes taxonomies for describing content, ads, and audiences. Old versions of taxonomies have been marked deprecated. <>
Appendix B: Change Log, concept row 3 L4625 at 26c59ba
1.0 | June 2020 | Added extended IDs object: Support for passing of multiple IDs of varying types.
Appendix B: Change Log, concept row 4 L4630 at 26c59ba
1.0 | February 2020 | Regulatory guidance: A section has been added to call attention to the expectation that implementers comply with applicable laws or regulations. Fields and objects which may be impacted have had text added.
Appendix B: Change Log, concept row 5 L4635 at 26c59ba
1.0 | November 2019 | Added VAST 4.2 and SIMID 1.0: API frameworks and video/audio subtypes lists have been updated to include VAST 4.2 and SIMID 1.0. Versioning policy: Elaborated on the versioning of this specification.
Appendix B: Change Log, concept row 6 L4641 at 26c59ba
1.0 | November 2018 | Initial release.

Tag AdCOM1.0-202607

Appendix B: Change Log, concept row 1 L4596 at d67a6a8
1.0 | March 2022 | Updates to support OpenRTB 2.6 release and keep 2.x/AdCOM in sync Added Pod Bidding features, rqddurs, poddur, podid, podseq, mincmppersec, slotinpod to AudioPlacement and VideoPlacement objects. Added Device.langb and Content.langb to support IETF BCP 47 Fixed eids typo so that it is an object array instead of object Added network and channel objects Deprecated yob and gender Added kwarray as preferred format to keywords Added new playback method, continuousplayback Added device type ooh Added new lists to support pod bidding; Ad Sequence and Pod Sequence Added new list to support User-Agent Source Added UserAgent and BrandVersion objects to support User Agent Client Hints
Appendix B: Change Log, concept row 2 L4613 at d67a6a8
1.0 | August 2021 | Added expdir to VideoPlacement: Support for indicating permitted expansion direction for video ads. Added overlaydir to VideoPlacement and AudioPlacement: Support for indicating permitted expansion direction for video and audio ads overlays. SIMID 1.1: SIMID 1.1 has been added to the API frameworks list. Expansion directions: "Resize/Minimize (make smaller)" has been added to the list of expanding directions. Definition of linearity: In the linearity modes list and the linear field in the VideoPlacement object, text has been revised to clarify that linearity corresponds to expected VAST response and is not an indication of in-stream vs out-stream. Category taxonomies list updated: The category taxonomies list was updated with the latest IAB taxonomies. The description of the list was expanded to note that it includes taxonomies for describing content, ads, and audiences. Old versions of taxonomies have been marked deprecated. <>
Appendix B: Change Log, concept row 3 L4625 at d67a6a8
1.0 | June 2020 | Added extended IDs object: Support for passing of multiple IDs of varying types.
Appendix B: Change Log, concept row 4 L4630 at d67a6a8
1.0 | February 2020 | Regulatory guidance: A section has been added to call attention to the expectation that implementers comply with applicable laws or regulations. Fields and objects which may be impacted have had text added.
Appendix B: Change Log, concept row 5 L4635 at d67a6a8
1.0 | November 2019 | Added VAST 4.2 and SIMID 1.0: API frameworks and video/audio subtypes lists have been updated to include VAST 4.2 and SIMID 1.0. Versioning policy: Elaborated on the versioning of this specification.
Appendix B: Change Log, concept row 6 L4641 at d67a6a8
1.0 | November 2018 | Initial release.

The record's YAML file

D-016 "1.0" covers nearly eight years of changes, the tags are named three ways, and the last tag isn't main. Which revision of AdCOM does the registry rest on?