Skip to content
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

Common section on namespacing #1528

Closed
uhoreg opened this issue Aug 17, 2018 · 0 comments · Fixed by #2097
Closed

Common section on namespacing #1528

uhoreg opened this issue Aug 17, 2018 · 0 comments · Fixed by #2097
Assignees
Labels
clarification An area where the spec could do with being more explicit client-server Client-Server API

Comments

@uhoreg
Copy link
Member

uhoreg commented Aug 17, 2018

There are several parts of the spec that refer to namespacing of names that end up being essentially the same ("m.* is reserved, and if you want to create your own use Java-style namespacing"). For example, event types, encryption algorithms, .well-known, etc. It would be nice to have a common section in the intro to refer to, rather than repeating the same thing over again.

@turt2live turt2live added the clarification An area where the spec could do with being more explicit label Aug 17, 2018
@turt2live turt2live added the client-server Client-Server API label Sep 6, 2018
@turt2live turt2live self-assigned this Jun 6, 2019
turt2live added a commit that referenced this issue Jun 6, 2019
See #2061
Fixes #1468
Fixes #1528

The section is not referenced by the specifications yet - they do a fairly good job of explaining it over and over. In future, it would be good to point all the references to the index.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
clarification An area where the spec could do with being more explicit client-server Client-Server API
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants