Reference
Specification
The normative contract: what a client and a server MUST, SHOULD and MAY do. Generated from SPEC.md in the protocol repository, so this page and the specification never disagree.
Contents
- 1Why MHP
- 2Architecture
- 3Scale: one device among thousands
- 4The device package
- 5Primitives
- 6Lifecycle
- 7Safety model
- 8Notifications
- 9Transports and discovery
- 10Three control surfaces
- 11Authoring descriptors
- 12Error codes
- 13Device classes (initial vocabulary)
- 14Bridging existing ecosystems
- 15Conformance
- 16Not yet specified
- Areference implementation