Loop/Architecture/Data Channels: Difference between revisions

Loop/Architecture/Data Channels (view source)

158 bytes added , 25 August 2015

Restructure for allowing different data types on different channels.

canmove, Confirmed users, Bureaucrats and Sysops emeriti

3,628

edits

@@ Line 20: / Line 20: @@
 == Format of Data ==
-Data sent across the data channel should be encoded in standard JSON format. Implementations should not fail if additional fields are sent within a message.
+The format of the data will vary for different channels, according to the requirements for data across that channel.
-It is envisioned that all Loop messages for a data channel will have a contentType field specifying the type of message. Hence the message may be ignored if the contentType is not supported. ''It may be necessary in future to add a feature detection capability.''
+== "Text" Data Channel ==
-Individual data types have their own structures.
+Data sent across the "text" data channel should be encoded in standard JSON format.
+Individual data types shall have their own defined structures, with contentType being the type of message.
+Notes:
+* Implementations should ignore messages with an unknown contentType, this is for forward compatibility.
+** ''It may be necessary in furture to have a capability detection system.''
+* Implementations should not fail if additional fields are sent within an known message content type.
 === Text Messages ===