Model Info

Table of Contents

Contract Overview

Interfaces

Manufacturer Interface
User Interface

Architecture Documents

Data Objects

---

Contract Overview

It is expected that a device query starts with a physical interface, and thus will enter through a protocol compliance contract, such as the Zigbee contract. The compliance organization will convert a device generated ComplianceID to a ModelID. The ModelID shall be used to reference manufacturer supplied data in the ModelInfo, Device Security, and Meta Data contracts. Further, the ModelID may be used to check compliance with other compliance organizations for devices which meet multiple compliance standards.

This data row is indexed by the Model Identifier (a random and unique identifier). Each Model record shall contain a JSON blob for the manufacturer, the manufacturer's ID, and a list of components contained in the device. The components are stored in the same contract as standalone devices.

There are three primary interfaces to the DeviceInfo contract: Manufacturer, Mediator, and Ecosystem Operator. The Manufacturer is the primary owner of the data and administrative rights to the model record, while the Ecosystem Operator shall have read access to all fields. The mediator shall be described in the Mediation section below.