search

matrix-org / matrix-spec

The Matrix protocol specification
Apache License 2.0
195 stars 97 forks source link

Should we version per-event event schemas? (SPEC-338) #151

Open matrixbot opened 8 years ago

matrixbot commented 8 years ago

Currently we have no way of adding fields into something like m.room.message in a client-friendly way, short of the client looking at what fields are present and guessing wildly as to what 'version' of the event schema the event was actually meant to represent. We should presumably encourage or even mandate that all events have a v:1 style key to help for disambiguation like this. We could add these incrementally as required, perhaps.

(Imported from https://matrix.org/jira/browse/SPEC-338)

(Reported by @ara4n)

matrixbot commented 8 years ago

Jira watchers: @ara4n

richvdh commented 8 years ago

as you say, versions can be added incrementally. What does adding versions proactively buy?

turt2live commented 6 years ago

We can achieve this with room versions now, where v2 rooms can (for example) dictate that events look completely different. This would require a lot of supporting documentation in the spec, but it could be done.

richvdh commented 5 years ago

It's presumably somewhat related to extensible events