From 45b2262d0fd9a4ab8a323b8379357ebf9dbd8bf7 Mon Sep 17 00:00:00 2001 From: Gareth Sylvester-Bradley <31761158+garethsb@users.noreply.github.com> Date: Wed, 31 Aug 2022 18:10:16 +0100 Subject: [PATCH] Fix links for patch release (#160) --- docs/Controllers.md | 2 +- docs/Interoperability - IS-04.md | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/Controllers.md b/docs/Controllers.md index e101dad..a53a6de 100644 --- a/docs/Controllers.md +++ b/docs/Controllers.md @@ -81,7 +81,7 @@ Controllers MUST adhere to the [APIs: Client Side Implementation Notes](APIs%20- #### API Common Keys -Controllers MUST follow the requirements for common API keys specified in the [IS-04 APIs: Common Keys](https://specs.amwa.tv/is-04/releases/v1.3.1/docs/2.1._APIs_-_Common_Keys.html) document including the requirements regarding [use of URNs](https://specs.amwa.tv/is-04/releases/v1.3.1/docs/2.1._APIs_-_Common_Keys.html#use-of-urns). +Controllers MUST follow the requirements for common API keys specified in the [IS-04 APIs: Common Keys](https://specs.amwa.tv/is-04/releases/v1.3.2/docs/APIs_-_Common_Keys.html) document including the requirements regarding [use of URNs](https://specs.amwa.tv/is-04/releases/v1.3.2/docs/APIs_-_Common_Keys.html#use-of-urns). ### Interacting with Non-NMOS Devices diff --git a/docs/Interoperability - IS-04.md b/docs/Interoperability - IS-04.md index dd8973b..38a0089 100644 --- a/docs/Interoperability - IS-04.md +++ b/docs/Interoperability - IS-04.md @@ -47,7 +47,7 @@ The Connection API includes a `master_enable` parameter in the `/active` endpoin The Receiver endpoint also includes a `sender_id` parameter that can be used to indicate that the Receiver is connected to a specific NMOS Sender, for example, via unicast RTP or source-specific multicast. Similarly, the Sender endpoint includes a `receiver_id` parameter that can be used to indicate that the Sender is connected to a specific NMOS Receiver, for example, via unicast RTP. -The API implementation MUST use these parameters to populate the `subscription` attribute of the corresponding IS-04 Sender or Receiver, according to the [Behaviour: Nodes](https://specs.amwa.tv/is-04/releases/v1.3.1/docs/4.3._Behaviour_-_Nodes.html) section of the IS-04 specification. +The API implementation MUST use these parameters to populate the `subscription` attribute of the corresponding IS-04 Sender or Receiver, according to the [Behaviour: Nodes](https://specs.amwa.tv/is-04/releases/v1.3.2/docs/Behaviour_-_Nodes.html) section of the IS-04 specification. It is the client's responsibility to set or unset (using `null`) the `sender_id` or `receiver_id` parameters when modifying the `transport_params` or `transport_file`. ## Support For Legacy IS-04 Connection Management