Filip/matrix-spec
1
0
Fork 0
mirror of https://github.com/matrix-org/matrix-spec synced 2026-02-04 13:23:43 +01:00
Code Issues Actions 3 Packages Projects Releases Wiki Activity

Remove reference to 'this MSC'.

Browse source
This commit is contained in:
David Baker 2023-05-17 10:10:45 +01:00
parent 18552057c0
commit 25ea0df0d1
1 changed files with 6 additions and 6 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

12
data/event-schemas/schema/m.call.negotiate.yaml
View file

@ -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: