d26794ee90
I've done my best to remove the word "bundle", because I feel like it causes more confusion than it provides. Instead I have favoured "aggregated child events" which I think is clearer. Some general clarification around these parts of the spec.
1.5 KiB
Reference relations
{{% added-in v="1.5" %}}
Generically referencing another event can be done with a rel_type of m.reference
as a form of relationship. There is no
implied meaning behind the reference, and is usually context-dependent. One
example is the key verification framework which uses
reference relations to associate distinct events with a specific verification attempt.
{{% boxes/note %}} Clients which wish to use threads or replies are expected to use other relationship types than references. References are typically used to associate data rather than messages. {{% /boxes/note %}}
Server behaviour
Server-side aggregation of m.reference
The aggregation format of m.reference
relations consists of a single chunk property, which lists all the events
which m.reference the event (the parent). Currently, only a single event_id
field is present on the events in the chunk.
For example, given an event with the following m.reference relationship:
{
"content": {
"m.relates_to": {
"rel_type": "m.reference",
"event_id": "$another_event"
}
// other content fields as required
}
// other fields as required by events
}
The aggregation would appear similar to the following:
{
"m.reference": {
"chunk": [
{ "event_id": "$one" },
{ "event_id": "$two" }
]
}
}