Do Open-Source Video Ad Clients Follow VAST 4.3? An Empirical Study of Player Conformance

Prashant Chaudhary. Online Resources to the paper, October 2026.

Resources

• Resource 1
  Client survey and selection record

  How the clients were chosen: the 16 npm queries, the package counts from 267 down to the tested set, the four-condition rule, and every candidate with its decision and reason.

  Tables R1.1, R1.2, R1.3, R1.4, R1.5, R1.6, R1.7, R1.8, R1.9, R1.10, R1.11, R1.12, R1.13, R1.14, R1.15

• Resource 2
  Validity checks

  The five evidence checks and three automated consistency audits of Section 4.6, one by one, and the mutation-fuzzing method with its seed and replay commands.

• Resource 3
  Shaka Player 5.3.0 compared with 5.2.12

  The Shaka Player 5.3.0 run: totals, the 11 verdict changes with their causes in source, same-verdict wire changes, rechecks, and which findings still hold.

  Tables R3.1, R3.2

• Resource 4
  Google IMA HTML5 SDK, operational setup

  How the closed IMA SDK was pinned, archived (hashes only), contained and driven, and the black-box evidence behind each of its eight findings.

  Tables R4.1, R4.2

• Resource 5
  Full results

  The catalog with the specification sentence behind every requirement, the full macro grid by macro set, and the strength-label sensitivity per configuration.

  Tables R5.1, R5.2, R5.3

• Appendix A
  Requirement catalog

  Appendix A as one wide table: all 108 requirements with duty group, strength as written and graded, obligation text, script, vector, deviating cells and the findings that cite each one.

  Tables A1, T3

• Appendix B
  Findings

  Appendix B as one wide table: all 86 findings with requirements, symptom, source location or black-box evidence, release range and platform scope.

  Tables B

• Resource 5
  Full results grid

  Every verdict for 108 requirements across 29 configuration and engine columns, Table 5, Appendix C, every deviating cell with its detail, the engine differences and the error grid.

  Tables R5.4, T5, C1, R5.5, T6, T8, R5.6

• Resource 5
  Every verdict by client

  One row per requirement and configuration (1,404 rows, Node.js layer and Chromium 141) with the oracle detail of every deviating or n/a cell.

  Tables R5.7

Citing a table or a row

Every table has a stable identifier and anchor, cited as, for example, "Online Resource 5, Table R5.1" (or5-full-results.html#R5.1). Tables R1.n to R5.n belong to Online Resources 1 to 5; A1, B, T3, T5, T6, T8 and C1 are the paper's tables of the same number in full. Rows have anchors too: requirement IDs on the catalog (requirements.html#W01), finding IDs on the findings page (findings.html#F23), and table id plus row key elsewhere (for example results.html#R5.4-M12).

Using these pages

Click a column header to sort (numbers sort by value); type in a table's filter box to keep the rows that contain every word; the drop-down filters narrow by client, duty group, strength or verdict, and the count above each table says how many rows are shown. Wide tables scroll sideways inside their frame, with the header row and first column held in place. Verdicts are always written out (conforms, deviates, delegated, n/a, or conf, DEV, deleg in the grid), never shown by color alone. Each table links its data as CSV. Every page is a single file that works offline; the same pages are in the Zenodo archive.