Loading...
Loading...
Every major decision, proposal, and fix that shaped the spec — straight from the working group's resolved discussions on GitHub. Expand any entry to read the original thread.
21
Resolved
8
Shipped
2025–2026
Window
4
Graphics
5
Manifest
4
GDD / Data
3
Bug fixes
5
Other
Graphics can now declare an optional thumbnail image in their manifest, giving controllers and editors a visual preview of each graphic.
Manifests can now declare which rendering engine version they require, letting servers reject graphics that target an incompatible runtime.
Added an optional property-order hint to manifest schemas so UIs can render fields in a predictable, designer-intended order.
Designers can now mark which manifest fields contribute to a graphic's display name — making instances easier to identify in playlists.
The OGraf specification is officially licensed under MIT — clearing up any ambiguity about commercial use, forks, and derivative works.
Manifests can now group related schema properties together, so form UIs can render them under labelled sections instead of a flat list.
Added position metadata to GDD types so layout-sensitive graphics (lower thirds, bugs, tickers) carry their intended screen placement.
Graphics that need internet access (live data, remote fonts, external APIs) now declare it up front — letting operators run them in air-gapped environments safely.
Removed the frame-count return from goToTime(). Graphics just seek to the time and return — less ceremony, fewer edge cases.
GDD gained a masked-text input type for sensitive fields like passwords, API keys, or anything that shouldn't show in plain text in the controller UI.
Graphics Data Definition (GDD), previously a separate spec, was merged into OGraf itself — one spec, one source of truth, one place to look things up.
GDD added a drop-down input type so manifests can constrain fields to a fixed set of choices without custom validation logic.
Clarified exactly when playAction() should resolve its promise — removing ambiguity between 'started playing' and 'finished playing'.
Tightened the spec around how OGraf graphics expose themselves as Web Components — making implementations more consistent across renderers.
Documented the implications of AdditionalProperties: false in schemas — it's strict by design, but it bites if you're not expecting it during validation.
Clarified the distinction between step-based graphics (discrete stages) and updateAction-driven graphics (continuous data updates). Two patterns, two use cases.
Manifest files now use the *.ograf.json extension convention — making OGraf graphics instantly recognisable in a filesystem or repo.
Set the direction for how OGraf graphics should load and reference fonts — recognising fonts as a first-class concern for broadcast-quality typography.
Concluded GDD is still needed — paving the way for its eventual merge into OGraf itself (see #24).
Fixed the sample manifest files to correctly reference their JavaScript implementations — otherwise the examples wouldn't actually run.
Open discussions, proposals, and active work live on the EBU OGraf repository. Anyone can read, comment, and contribute.
Join the discussion on GitHub