Link to problem area:
exemplary https://spec.matrix.org/v1.18/client-server-api/#molmv1curve25519-aes-sha2
Issue
Sometimes, the type of fields that are supposed to contain user IDs is given as string, and sometimes as User ID, with a link to https://spec.matrix.org/v1.18/appendices/#user-identifiers.
In the example above, this is especially noticeable, as it is the case for two fields right next to each other, but the issue persists throughout the spec.
This is confusing – is the use of different types intentional, and if so, what's the reason?
Otherwise, all user ID fields should probably have type User ID.
Link to problem area:
exemplary https://spec.matrix.org/v1.18/client-server-api/#molmv1curve25519-aes-sha2
Issue
Sometimes, the
typeof fields that are supposed to contain user IDs is given asstring, and sometimes asUser ID, with a link to https://spec.matrix.org/v1.18/appendices/#user-identifiers.In the example above, this is especially noticeable, as it is the case for two fields right next to each other, but the issue persists throughout the spec.
This is confusing – is the use of different types intentional, and if so, what's the reason?
Otherwise, all user ID fields should probably have type
User ID.