resource-republish
A provisional HM26 schema for review, with unresolved semantics recorded in the overview.
Fetching schema…

DRAFT — not a shipped protocol. See design notes.

DRAFT HM26 republish resource. Inherits BaseResource only; payload and prior-link semantics are unresolved. This placeholder is not a usable republish protocol.

BaseResource extends the existing signed Blob envelope; all six resource variants extend BaseResource. BaseResource owns optional resource identity, parent placement and relative name. It has no stored type override or fixed resource type tag. The inherited Blob envelope still requires a stored string type; arbitrary strings satisfy that structural constraint. Whether HM26 should eliminate the inherited field is an open envelope-design question. No replacement dispatch mechanism is introduced. Required kind selects the six closed resource variants.

{ "type": "hm://z6MkiAKDcRSzQ4zPZfnJcS5HYx5MwgN6MU9foHihJGrhqNBj/hm26/base-resource", "properties": { "kind": { "value": "republish", "required": true, "description": "Closed resource-variant discriminator." } }, "description": "DRAFT HM26 republish resource. Inherits BaseResource only; payload and prior-link semantics are unresolved. This placeholder is not a usable republish protocol." }


Learn this in the sync playground

Sync playground extension · 2026-10-23. Teaching prototype; no production protocol or schema adoption.

Deduplicating a chunk across resources does not itself republish content or expand its audience. An admitted publication needs provenance and destination authority. The existing native republish placeholder remains unresolved; the sync experiment does not invent its wire payload.

Do you like what you are reading? Subscribe to receive updates.

Unsubscribe anytime

Comments