C2PA specification (Coalition for Content Provenance and Authenticity) and the missing web standards listed on iOS404.com.
🔑 What C2PA RequiresC2PA defines a framework for embedding cryptographically signed provenance metadata into digital assets (images, video, audio, documents). To support this in browsers, the spec relies on:
🚫 Missing Standards in Safari (from iOS404.com) that Block C2PAHere are the specific gaps:
| C2PA Requirement | Missing Standard in Safari (iOS404) | Impact |
|---|---|---|
| Signed asset delivery | Signed HTTP Exchanges (SXG) | Prevents verifiable delivery of provenance metadata with content |
| Metadata enforcement | Document Policy, Permissions Policy | Makes it harder to guarantee provenance data isn’t stripped |
| Secure storage | File System Access API | Limits ability to store provenance manifests locally |
| Reliable sync | Background Sync API, Push API | Breaks offline/async provenance updates and notifications |
| Compression | Zstandard (zstd) encoding | Less efficient delivery of provenance manifests |
| Media provenance | ImageCapture API, Media Capture from DOM Elements API | Prevents embedding provenance at capture time |
| Transparency UI | Web Notifications API, Fullscreen API | Restricts user-facing provenance alerts and overlays |
📌 TakeawayFor C2PA to work fully in Safari, the most critical missing standards are: