From 30152520cb909aaed40bb4ddd5688e6dad5ae5f5 Mon Sep 17 00:00:00 2001 From: Gareth Sylvester-Bradley <31761158+garethsb@users.noreply.github.com> Date: Wed, 25 Sep 2024 09:37:13 +0100 Subject: [PATCH 1/2] Clarify that API reflects underlying Device always, not just at start-up --- docs/Behaviour.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/Behaviour.md b/docs/Behaviour.md index fb87323..7bd6851 100644 --- a/docs/Behaviour.md +++ b/docs/Behaviour.md @@ -8,7 +8,7 @@ _(c) AMWA 2018, CC Attribution-NoDerivatives 4.0 International (CC BY-ND 4.0)_ ## Start-Up Behaviour -This specification does not define the channel mapping behaviour at start-up, as this may depend on the nature of the Device the API is controlling. However, it is important that the channel mapping behaviour of the underlying Device is reflected in the API at start-up. +This specification does not define the channel mapping behaviour at start-up, as this may depend on the nature of the Device the API is controlling. It is important that the API always reflects the current channel mapping behaviour of the underlying Device. ## Interaction with Other Protocols From bfb45ad6afae0a391bef962c04bce02ce56ec7c4 Mon Sep 17 00:00:00 2001 From: Gareth Sylvester-Bradley <31761158+garethsb@users.noreply.github.com> Date: Wed, 25 Sep 2024 09:42:24 +0100 Subject: [PATCH 2/2] Explain current channel mapping behaviour vs. activation --- docs/Behaviour.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/docs/Behaviour.md b/docs/Behaviour.md index 7bd6851..4e6d302 100644 --- a/docs/Behaviour.md +++ b/docs/Behaviour.md @@ -228,6 +228,8 @@ See the [Timestamps](#Timestamps) section for more details on the required inter Once an activation has been completed the resulting changes to the map MUST be reflected in the `active` endpoint. The `activation` object in the `active` endpoint MUST contain the details of the last activation to have taken place. +Changes to the underlying Device's channel mapping behaviour (whether initiated by IS-08 or not) are reflected immediately into the Active Map `map`. Therefore the action of the most recent `activation` (or any previous activation) can have been overwritten. The only certain way to determine if the current behaviour is what the Client requires is to examine the `map`. + #### Activation Responses Each successful activation request is allocated a unique identifier by the API. This identifier MUST be unique within an API instance and for all time.