From 138ca8ce9b8268f86ff83bb1619e24d9abba10e6 Mon Sep 17 00:00:00 2001 From: Bruno Windels Date: Wed, 25 Aug 2021 15:49:42 +0200 Subject: [PATCH] add example of event shape --- proposals/2674-event-relationships.md | 13 +++++++++++++ 1 file changed, 13 insertions(+) diff --git a/proposals/2674-event-relationships.md b/proposals/2674-event-relationships.md index 8a909efc0..e55e6d66d 100644 --- a/proposals/2674-event-relationships.md +++ b/proposals/2674-event-relationships.md @@ -31,6 +31,19 @@ Both of those fields are required. An event is said to contain a relationship if a relationship with all the required fields under the `m.relates_to` key. If any of these conditions is not met, clients and servers should treat the event as if it does not contain a relationship. +Here's a (partial) example of an event relating to another event: + +```json +{ + "content": { + "m.relates_to": { + "rel_type": "m.replace", + "event_id": "$abc:server.tld" + } + } +} +``` + All the information about the relationship lives under the `m.relates_to` key. If it helps, you can think of relations as a "subject verb object" triple,