Merge branch 'statuses-columns' into 'master'

List columns names in reference implementation db table

See merge request !2

protocols/BSP.md

@@ -112,17 +112,17 @@ A device should reject any record with an unsupported protocol version and ignor
 
 A device stores the following synchronisation state for each message it is sharing with a peer:
 
-- **Seen flag** - Raised if the peer is known to have seen the message, otherwise lowered
+- **Seen flag** - Raised if the peer is known to have seen the message, otherwise lowered (column `seen` in `statuses` table, Bramble database)
 
-- **Ack flag** - Raised if the peer has offered or sent the message since the device last acknowledged it, otherwise lowered
+- **Ack flag** - Raised if the peer has offered or sent the message since the device last acknowledged it, otherwise lowered (column `ack`)
 
-- **Request flag** - Raised if the peer has requested the message since the device last offered or sent it, otherwise lowered
+- **Request flag** - Raised if the peer has requested the message since the device last offered or sent it, otherwise lowered (`requested`)
 
-- **Send count** - The number of times the message has been offered or sent to the peer
+- **Send count** - The number of times the message has been offered or sent to the peer (`txCount`)
 
-- **Send time** - The time at which the message can next be offered or sent to the peer, or zero if the message has never been offered or sent to the peer
+- **Send time** - The time at which the message can next be offered or sent to the peer, or zero if the message has never been offered or sent to the peer (`expiry`)
 
-- **Expected arrival time** - The time at which the offer or message is expected to arrive at the peer, or zero if the message has never been offered or sent to the peer
+- **Expected arrival time** - The time at which the offer or message is expected to arrive at the peer, or zero if the message has never been offered or sent to the peer (`eta`)
 
 The device may also store a list of message identifiers that have been offered by the peer and not yet requested by the device. This list allows requests to be sent asynchronously. The length of the list may be bounded and the peer may discard offered message identifiers when the list is full.