What's on this page
A topic is one Zenoh key expression a vendor publishes under — for example,
homemade-sensors/garage/temperature/v1. Registering it here tells the portal +
inspector what to expect: which serialization the bytes use, which schema describes them,
and a human description. The router doesn't enforce registration today; declaration is a
polite contract that makes the inspector useful and the registry browseable.
Look at the seeded homemade-sensors rows below for a working example. Full
namespace governance + version-bump rules at Docs → Namespace.
Bulk import
Paste a YAML or JSON file matching the export shape. Hit Preview to see the diff (create / update / unchanged / retire) before applying. Mode: additive leaves topics absent from the file alone; replace also retires unlisted ones.
Current topics
| Key pattern ⓘ | Format ⓘ | Schema ⓘ | Storage ⓘ | Last seen | Publishes | Actions |
|---|
Register a new topic
The router doesn't require this — anyone with the per-vendor cert can publish under their prefix regardless of what's in the registry. But declaring a topic here turns the inspector from "raw hex" into a readable decode + makes your namespace browsable to other vendors on the fabric.