← Back to the chapter · Next detail →
Technical detail · IoT Interoperability Challenges
A precise identity for the camera concept
A compact way to make shared meaning reviewable is to represent each collaborative concept as a four-part tuple:
The fields have separate jobs. is the internal identifier used to refer to the concept without relying on its display name. identifies the natural language used for human-facing labels and definitions. names the context or namespace in which the identifier is interpreted. defines the object and its properties precisely enough for another system to map it. Modern implementations should make a language tag such as en-GB, make a resolvable URI or versioned namespace, and encode as a structured definition rather than an unparsed sentence where possible.
RTSP (Real Time Streaming Protocol) controls media streams, such as a camera video feed. The record below names it as one capability of the camera.
| Tuple field | CCTV security-camera example | Why it cannot be omitted |
|---|---|---|
| : internal identifier | urn:building-a:camera:17 | “Camera 17” may collide with another site’s identifier. |
| : natural language | en-GB | Labels and terms can change meaning across languages and locales. |
| : context | https://example.org/security-video/v2 | “CCTV” could mean a security endpoint, a traffic camera, or a television service. |
| : object definition | {kind: bullet-camera, transport: IP, stream: RTSP, maxPixels: [2048,1536], location: loading-bay} | A name alone does not define capabilities, units, protocol, or place. |
So the worked record is not merely CCTV = camera. It is
Walk the exchange step by step. The source publishes identifier rather than a local screen label. The receiver resolves context and learns that this namespace describes security-video devices. It uses to choose the correct human label, then validates the message against : a streamState event is meaningful for this IP camera, while a broadcastChannel command from a television-domain system is not. Two messages can therefore share valid JSON syntax and even the word “CCTV” while failing semantic interoperability because their and fields disagree.