-
Notifications
You must be signed in to change notification settings - Fork 379
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
MSC3267: Reference relations #3267
Conversation
Tagged as needs-implementation even though the verification use-case in implemented, since the non-verification use-case is not yet implemented |
Given that |
(please use threads to receive in-depth/any replies) The way |
going to use the key verification framework as an implementation proof for this - https://spec.matrix.org/v1.2/client-server-api/#key-verification-framework |
@bwindels apologies, I've taken this over in an effort to get it through (finally). |
for events to make a reference to another event. | ||
|
||
A `rel_type` of `m.reference` is defined as a generic way to associate an | ||
event with another event. As a bundle, `m.reference` relations appear as |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It would be useful to link to MSC2675 here, which defines bundling related events.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Actually, we can probably just remove the sentences about server-side aggregation given the information is repeated below under the "Server aggregation" header?
A `rel_type` of `m.reference` is defined as a generic way to associate an | ||
event with another event. As a bundle, `m.reference` relations appear as | ||
an object with a single `chunk` field. The `chunk` is an array of objects | ||
with a single `event_id` field for all the child events which `m.reference` | ||
the parent. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Perhaps we can just remove the word "all" in this sentence to eliminate any subtle confusion.
|
||
## Server aggregation | ||
|
||
[MSC2674](https://github.com/matrix-org/matrix-doc/pull/2674) states |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think this is MSC2675 now?
🔔 This is now entering its final comment period, as per the review above. 🔔 |
The final comment period, with a disposition to merge, as per the review above, is now complete. |
* initial draft of reference relations msc * change MSC number * Apply formatting * Convert to point at present rather than ideal * Clarify that multiple relations is a thing we don't have and won't fix here * Fix wording to match reality, again * fix a typo Co-authored-by: Travis Ralston <[email protected]> Co-authored-by: Andrew Morgan <[email protected]>
Spec PR: matrix-org/matrix-spec#1206 |
* Spec reference relationships MSC: matrix-org/matrix-spec-proposals#3267 * Apply suggestions from code review Co-authored-by: Richard van der Hoff <[email protected]> * Edits per code review Co-authored-by: Richard van der Hoff <[email protected]>
Merged 🎉 |
* Spec reference relationships MSC: matrix-org/matrix-spec-proposals#3267 * Apply suggestions from code review Co-authored-by: Richard van der Hoff <[email protected]> * Edits per code review Co-authored-by: Richard van der Hoff <[email protected]>
Rendered
Implementation: The key verification framework
FCP: #3267 (comment)