From 25ea0df0d1ace1ac97ae69aefda6134d7fe42792 Mon Sep 17 00:00:00 2001 From: David Baker Date: Wed, 17 May 2023 10:10:45 +0100 Subject: [PATCH] Remove reference to 'this MSC'. --- data/event-schemas/schema/m.call.negotiate.yaml | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/data/event-schemas/schema/m.call.negotiate.yaml b/data/event-schemas/schema/m.call.negotiate.yaml index ca3e4d0d..83012966 100644 --- a/data/event-schemas/schema/m.call.negotiate.yaml +++ b/data/event-schemas/schema/m.call.negotiate.yaml @@ -27,12 +27,12 @@ description: | another `m.call.negotiate` event, with the SDP answer (with `"type": "answer"`) in the `description` property. - This MSC also proposes clarifying the `m.call.invite` and `m.call.answer` - events to state that the `offer` and `answer` fields respectively are objects - of type `RTCSessionDescriptionInit`. Hence the `type` field, whilst - redundant in these events, is included for ease of working with the WebRTC - API and is mandatory. Receiving clients should not attempt to validate the - `type` field, but simply pass the object into the WebRTC API. + In the `m.call.invite` and `m.call.answer` events, the `offer` and `answer` + fields respectively are objects of type `RTCSessionDescriptionInit`. Hence + the `type` field, whilst redundant in these events, is included for ease of + working with the WebRTC API and is mandatory. Receiving clients should not + attempt to validate the `type` field, but simply pass the object into the + WebRTC API. allOf: - "$ref": core-event-schema/room_event.yaml properties: