Confirmed users
632
edits
Loop/Architecture/Data Channels: Difference between revisions
no edit summary
(Restructure for allowing different data types on different channels.) |
No edit summary |
||
| Line 22: | Line 22: | ||
The format of the data will vary for different channels, according to the requirements for data across that channel. | The format of the data will vary for different channels, according to the requirements for data across that channel. | ||
== "Text" Data Channel == | === "Text" Data Channel === | ||
Data sent across the "text" data channel should be encoded in standard JSON format. | Data sent across the "text" data channel should be encoded in standard JSON format. | ||
| Line 34: | Line 34: | ||
* Implementations should not fail if additional fields are sent within an known message content type. | * Implementations should not fail if additional fields are sent within an known message content type. | ||
=== Text Messages === | ==== Text Messages ==== | ||
{ | { | ||