Urgent.News

What's breaking now, across hundreds of outlets.

Tech

OpenRTB 2.6 leaves about half of its conformance statements unlintable.

OpenRTB 2.6 leaves about half of its conformance statements outside a static lint. On the instance count, 53.5 percent are statically checkable, 20.5 percent need a runtime context, and 26.0 percent have no machine-decidable criterion. The checkable share is a little over half. The unlintable half is those last two columns, and they are not the same gap. The figures are Table 1 of my July 2026…

The OpenRTB 2.6 specification leaves around half of its conformance statements unlintable, according to research published in July 2026. Of the 288 conformance statements, 53.5% are statically checkable, 20.5% need a runtime context, and 26.0% have no machine-decidable criterion. The statically checkable statements account for just over half, while the remaining unlintable statements are split between needing a runtime context and having no observable criterion.

The study classifies the conformance statements into four categories: Class A (expressible in JSON Schema), Class B (decidable from a single message), Class C (requiring additional messages or interactions), and Class D (having no observable criterion). The majority of the statically checkable statements fall into Class A, while Class C and D contribute to the unlintable portion.

The research also highlights that the repetition of boilerplate clauses across objects in the specification can impact the statically checkable share. OpenRTB 3.0 has a smaller conformance text with only 88 statements, and a different distribution of conformance constraints. While OpenRTB 3.0 is more rigorous in certain aspects (such as HTTPS and TLS mandates), it is less lintable since many of its requirements are defined outside of the JSON schema.

Rewritten by urgent.news; may contain errors — check the original.

Source: dev.to

Read the original at dev.to →

Report a problem with this story

More in Tech

Building a Business Website That Actually Works: 7 Things Developers Should Get Right

Building a Business Website That Actually Works: 7 Things Developers Should Get Right A business website is often treated as a relatively straightforward development project.

  • Start with clear requirements to avoid unnecessary features
  • Prioritize performance through image optimization and caching
  • Incorporate accessibility and technical SEO into HTML structure

More from Sunday 22 November →