← Back to the chapter · Previous detail

Technical detail · IoT Glossary: A

How vocabulary errors become design errors

5.4.2 Glossary Precision Prevents Design Errors

Small vocabulary errors become implementation errors. Confusing authentication with authorization can produce accounts that prove identity but receive the wrong permissions. Confusing encryption with certificate validation can protect data in transit while still accepting the wrong endpoint. Confusing aggregation with raw telemetry can hide outliers that a device-health workflow needs.

The same is true for protocol semantics. MQTT QoS 1, AMQP acknowledgements, CoAP confirmable messages, and stream-processing exactly-once claims do not all mean the same thing. Each defines a scope: packet receipt, broker acceptance, application processing, storage commit, or downstream consumer state. Read glossary terms with that scope in mind.

Underneath the vocabulary, every term is tied to a state transition or contract. An ACK may confirm that a TCP segment arrived, that a CoAP confirmable message was received, that an AMQP broker accepted a delivery, or that application code processed a command. Those are different guarantees. Encryption may protect bytes on the wire, while certificate validation decides whether the endpoint is trusted. A firewall may filter at an address, port, or protocol boundary, while an application authorization rule may decide whether a device can write to a specific topic or API route.

Data terms have the same hidden scope. CBOR, JSON, compression, aggregation, ETL, and data lake are not interchangeable labels for “data handling.” They describe representation, size trade-offs, transformation, storage, retention, and later interpretation. A frame may include link-layer headers and checksums, while an application record may include stable field names, units, timestamps, schema version, and device identity. If the report says “the broker received the frame,” the wording is probably mixing layers; the gateway or radio stack sees the frame, while the broker sees a message or application payload.

A good capstone explanation should use these terms to identify responsibility: which device, broker, gateway, cloud service, dashboard, or human operator owns the next state transition.

← Back to the chapter · Previous detail