From e4c16fa7299252d4dca250cf143fa591c5acfde9 Mon Sep 17 00:00:00 2001 From: Bruno Windels Date: Wed, 30 Jun 2021 15:13:09 +0200 Subject: [PATCH] mention multiple relations per event might be useful, but postpone for a future MSC --- proposals/2674-event-relationships.md | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-) diff --git a/proposals/2674-event-relationships.md b/proposals/2674-event-relationships.md index d0f4a6a7a..768e5a1d3 100644 --- a/proposals/2674-event-relationships.md +++ b/proposals/2674-event-relationships.md @@ -34,9 +34,8 @@ where the subject is the relation event itself; the verb is the `rel_type` field of the `m.relates_to` and the object is the `event_id` field. We consciously do not support multiple different relations within a single event, -in order to keep the API simple, and in the absence of identifiable use cases. -Instead, one would send multiple events, each with its own `m.relates_to` -defined. +in order to keep the API simple. A future MSC can propose a change to add support +for multiple relations if it turns out that this would facilitate certain use cases. A `rel_type` of `m.reference` is defined for future handling replies and threading. This let you define an event which references an existing