Globodex Specification

Event Data
Standard

A shared language for describing what happens in the world: where, when, and why it matters. EDS gives AI agents and media systems a common way to discover, verify, and reason about real-world events.

Version: V 0.1
Scope: Events · Entities · Media · Trust
Published by: Channel 1

Learn more

Designed for the agentic web

Event data is fragmented, unverifiable, and siloed.

Every newsroom, sensor network, public agency, research organization, and AI agent describes the world differently. EDS provides a portable core for exchanging event intelligence without losing its evidence or usage conditions.

No shared schema

Systems disagree on how to represent time, place, identity, evidence, and relationships.

Trust arrives later

Provenance and verification are bolted on after the data has already changed hands.

Rights disappear

Licenses, consent, and permitted uses rarely remain machine-readable downstream.

Architecture

Four storage layers. One progressive record.

EDS is designed around a layered architecture that preserves raw source assets while adding increasingly useful structure.

Object storage

Original video, audio, images, text, and telemetry.

Source of truth

Metadata storage

Time, place, entities, classification, provenance, trust, and rights.

Structured record

Vector storage

Embeddings for semantic discovery, similarity, and deduplication.

Meaning

Graph storage

Typed relationships between events, entities, places, and assets.

Context

The atomic unit

Anatomy of an event.

An EDS event is a portable record of something that happened. Six layers make it locatable, comparable, verifiable, and safe to use.

01Identityschema · id · status · language · summary

02Timeinterval · lower · upper · uncertainty

03Placegeometry · altitude · CRS · H3 index

04Classificationtype · subtype · taxonomy

05Provenancecreated_at · created_by · collection method

06Trust & rightsverification · license · consent · restrictions

event.jsoneds-0.1

{
  "schema": "eds-0.1",
  "id": "evt_01HZYR4E1K0A3N7A6J3C4KZ9B2",
  "summary": "Large march along Wilshire Boulevard",
  "status": "observed",
  "time": {
    "interval": "2026-08-12T12:05:00Z/2026-08-12T13:40:00Z",
    "uncertainty": { "lower": "PT5M", "upper": "PT2M" }
  },
  "place": {
    "geometry": { "type": "Polygon", "coordinates": [] },
    "spatial_index": { "h3": { "res7": ["87283082affffff"] } }
  },
  "classification": {
    "type": "public_protest",
    "subtype": "march"
  },
  "provenance": {
    "created_by": "org:channel1",
    "collection_method": ["mobile_uploads", "wire_service"],
    "source_confidence": 0.86
  },
  "rights": {
    "license": "CC-BY-4.0",
    "restrictions": ["no_face_recognition"]
  }
}

Progressive data quality

Start with what you know. Make completeness explicit.

Not every source can provide every field on day one. Conformance levels let producers contribute useful event data immediately without overstating what is known.

Minimal

Schema version, event ID, status, and summary.

Something happened

Localized

Adds temporal bounds and a spatial footprint.

Anchored in the world

Complete

Classification, provenance, rights, trust, entities, and assets.

Production ready

Verified

Cryptographic content-authenticity manifests attached.

End-to-end proof

Typed connections

Events become a graph over time.

Relations are directional, weighted, and sourced. They let systems reconstruct sequences, trace causal claims, distinguish duplicates, and preserve contradictions.

Temporal

precedesfollowscoincides_with

Causal

causescaused_bycorrelates_with

Structural

withinpart_ofsuperset_of

Identity

same_assupersedescontradicts

Design principles

Small core. Verifiable by default.

Small core, rich extensions

Keep the portable event object readable. Put domain-specific complexity in governed extensions.

Standards-native interoperability

Use JSON, GeoJSON, ISO 8601, H3, JSON-LD hooks, and established content-authenticity systems.

Verifiability by default

Treat provenance, hashing, corroboration, and verification as part of the record—not optional decoration.

Safety and rights first

Keep licenses, consent, restrictions, and sensitivity machine-readable at every downstream use.

Predictable evolution

Version explicitly, publish migrations, and give integrations time to adapt to breaking changes.

The standard

One shape for what just happened.

EDS gives agents and media systems a common, verifiable way to describe real-world events, so intelligence moves between them without losing its sources. If your systems move event data, we want to hear from you.

Talk to us

Event DataStandard