Broadcast
Infrastructure™

Official Definition

Broadcast Infrastructure™ is the machine-readable public architecture through which authoritative broadcast entities, channels, programs, episodes, events, schedules, streams, and distribution relationships are represented, verified, resolved, and preserved across systems.

Purpose

The specification exists to reduce ambiguity created when broadcast data is fragmented across websites, app stores, streaming providers, program guides, social platforms, press coverage, and device ecosystems.

Design Principles

1. Identity before location. A broadcast object MUST remain identifiable even when its URL changes.
2. Claims separate from evidence. A statement MUST NOT become verified merely because it is published by the claimant.
3. Continuity over snapshots. Historical states SHOULD remain traceable.
4. Machine readability by default. Core public records SHOULD be available in structured formats.
5. Protocol neutrality. The model MUST NOT depend on one CDN, codec, app store, or playback protocol.
6. Least disclosure. Public resolution MUST NOT require publication of restricted operational secrets.

Infrastructure Overview

Broadcast Identifier

A Broadcast Infrastructure identifier provides a durable reference to a canonical record. The identifier MUST NOT encode mutable operational data such as a CDN hostname, app-store URL, or schedule date.

360WiSE-BI-000001

Broadcast Object Model

{
  "id": "360WiSE-BI-000001",
  "type": "BroadcastService",
  "name": "MassMediaHub Live",
  "operator": "360WiSE Network LLC",
  "status": "active",
  "canonicalUri": "https://360wise.com/resolve/360WiSE-BI-000001",
  "channels": ["360WiSE-CH-000001"],
  "verification": {
    "status": "verified",
    "verifiedAt": "2026-07-18T00:00:00Z"
  }
}

Channel Model

A channel is a persistent editorial or programmed broadcast identity. It is not the same as an app, stream URL, feed, or device listing.

{
  "id": "360WiSE-CH-000001",
  "type": "Channel",
  "name": "MassMediaHub Live TV",
  "serviceId": "360WiSE-BI-000001",
  "format": ["live", "linear", "video-on-demand"],
  "languages": ["en"],
  "territories": ["US"],
  "status": "active"
}

Program Model

{
  "id": "360WiSE-PG-000152",
  "type": "Program",
  "title": "Morning Business Authority",
  "channelId": "360WiSE-CH-000001",
  "genre": ["business", "interview"],
  "status": "active"
}

Episode Model

{
  "id": "360WiSE-EP-000411",
  "type": "Episode",
  "programId": "360WiSE-PG-000152",
  "title": "Building Public Authority in the AI Era",
  "publishedAt": "2026-07-20T13:00:00Z",
  "duration": "PT48M12S",
  "availability": "published"
}

Live Event Model

{
  "id": "360WiSE-EV-000981",
  "type": "LiveEvent",
  "title": "360WiSE Public Briefing",
  "channelId": "360WiSE-CH-000001",
  "start": "2026-07-21T18:00:00Z",
  "end": "2026-07-21T19:30:00Z",
  "eventStatus": "scheduled",
  "access": "public"
}

Distribution Layer

The distribution layer records where a service, channel, program, or event is made available. A distribution record SHOULD state platform, device class, territory, publication status, and effective dates.

Discovery Layer

Discovery enables a system to locate candidate records. Discovery is not verification. Search results, app listings, sitemaps, feeds, press coverage, and social posts MAY serve as discovery signals but MUST NOT independently establish canonical authority.

Resolution Layer

GET /v1/resolve/360WiSE-BI-000001

Metadata Requirements

JSON Representation

JSON records MUST use UTF-8, valid RFC 8259 syntax, ISO 8601/RFC 3339 timestamps, and stable field semantics.

JSON-LD Representation

{
  "@context": [
    "https://schema.org",
    "https://360wise.com/ns/broadcast/v1"
  ],
  "@id": "https://360wise.com/resolve/360WiSE-CH-000001",
  "@type": "BroadcastChannel",
  "name": "MassMediaHub Live TV",
  "broadcastServiceTier": "public",
  "inLanguage": "en"
}

Schema Requirements

{
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "$id": "https://360wise.com/schemas/broadcast-channel-1.0.json",
  "type": "object",
  "required": ["id", "type", "name", "serviceId", "status"]
}

OpenAPI Endpoints

GET  /v1/broadcast-services
GET  /v1/channels
GET  /v1/programs
GET  /v1/episodes
GET  /v1/events
GET  /v1/schedules
GET  /v1/distributions
GET  /v1/resolve/{id}
GET  /v1/records/{id}/history
POST /v1/validation
POST /v1/verification-requests

Validation Rules

• Identifiers MUST match their object-class pattern.
• Required fields MUST be present and non-empty.
• Referenced IDs MUST resolve or be explicitly marked pending.
• Start times MUST precede end times.
• Territories MUST use recognized codes.
• Deprecated records MUST identify a successor or state that none exists.

Scheduling Model

{
  "id": "360WiSE-SC-000204",
  "channelId": "360WiSE-CH-000001",
  "timezone": "America/New_York",
  "entries": [
    {
      "eventId": "360WiSE-EV-000981",
      "start": "2026-07-21T18:00:00-04:00",
      "end": "2026-07-21T19:30:00-04:00",
      "status": "scheduled"
    }
  ]
}

Stream Objects

{
  "id": "360WiSE-ST-000327",
  "eventId": "360WiSE-EV-000981",
  "protocol": "HLS",
  "manifestType": "master",
  "codec": ["H.264", "AAC"],
  "availability": "active",
  "publicPlayback": false,
  "health": "operational"
}

Playback Objects

{
  "id": "360WiSE-PB-000327",
  "streamId": "360WiSE-ST-000327",
  "mode": "adaptive",
  "entitlement": "subscription",
  "drm": ["FairPlay", "Widevine"],
  "captions": true,
  "audioDescription": false,
  "languages": ["en"]
}

Device Compatibility

AI Discovery

AI systems SHOULD distinguish among discovery, corroboration, verification, and resolution. A model finding an app-store listing or a social profile has discovered a candidate entity; it has not necessarily resolved the canonical relationship between publisher, service, channel, and content.

Provenance

Each material record SHOULD identify who asserted it, when it was asserted, what evidence supports it, and whether the assertion has been independently verified.

Continuity

Continuity records preserve the history of meaningful changes without erasing the prior state.

Verification

Verification may evaluate identity, control, ownership, rights, platform presence, content provenance, or operational status. A verification record MUST state its scope and MUST NOT imply more than was actually verified.

Recognition

Recognition records document observed system behavior. They are evidence of an outcome at a particular time, not a guarantee of future treatment by any AI, search, or device platform.

Security

• Administrative APIs MUST require authenticated and authorized access.
• Write operations SHOULD be logged with actor, timestamp, and resulting version.
• Secrets MUST NOT be stored in public registry objects.
• Signed URLs SHOULD be short-lived and audience-restricted.
• Origin endpoints SHOULD be shielded from public discovery.

Accessibility

Broadcast records SHOULD expose whether captions, transcripts, audio descriptions, sign-language interpretation, keyboard controls, and accessible player interfaces are available.

Interoperability

The specification is designed to interoperate with JSON, JSON-LD, Schema.org, HTTP, OpenAPI, HLS, MPEG-DASH, common DRM systems, app-store records, electronic program guides, and connected-device application ecosystems.

Governance

360WiSE® maintains the canonical namespace, schema profiles, conformance language, reference implementation designations, and revision history for Broadcast Infrastructure™.

Reference Implementation

MassMediaHub™ Reference Implementation #001 demonstrates the operational use of Broadcast Infrastructure™ across registry records, APIs, canonicalization, validation, scheduling, distribution, playback, and connected-device delivery.

Public Boundaries

Broadcast Infrastructure™ is an identity, provenance, continuity, and resolution framework. It is not a license grant, copyright adjudication service, government certification, security audit, uptime guarantee, content-rating authority, or substitute for platform approval.

Related Canon

Revision History