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.

Sign up for GitHub

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

Clarify v3 event representation in identifier grammar #1876

Merged
merged 3 commits into from
Mar 27, 2019
Merged

Clarify v3 event representation in identifier grammar #1876

Changes from 1 commit
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
946acbf
Clarify v3 event representation in identifier grammar
turt2live Feb 11, 2019
42cf72c
URL encode matrix.to URIs
turt2live Mar 20, 2019
0ec3403
URL encode all the things
turt2live Mar 20, 2019
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
15 changes: 9 additions & 6 deletions specification/appendices/identifier_grammar.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -19,7 +19,7 @@ Identifier Grammar
Some identifiers are specific to given room versions, please refer to the
`room versions specification`_ for more information.

.. _`room versions specification`: ../index.html#room-versions
.. _`room versions specification`: index.html#room-versions


Server Name
Expand Down Expand Up @@ -234,18 +234,17 @@ A room has exactly one room ID. A room ID has the format::

!opaque_id:domain

An event has exactly one event ID. An event ID has the format::
An event has exactly one event ID. The format of an event ID depends upon the
`room version specification <index.html#room-versions>`_.

$opaque_id:domain

The ``domain`` of a room/event ID is the `server name`_ of the homeserver which
The ``domain`` of a room ID is the `server name`_ of the homeserver which
created the room/event. The domain is used only for namespacing to avoid the
risk of clashes of identifiers between different homeservers. There is no
implication that the room or event in question is still available at the
corresponding homeserver.

Event IDs and Room IDs are case-sensitive. They are not meant to be human
readable.
readable. They are intended to be treated as fully opaque strings by clients.

.. TODO-spec
What is the grammar for the opaque part? https://matrix.org/jira/browse/SPEC-389
Expand Down Expand Up @@ -333,6 +332,10 @@ Examples of matrix.to URIs are:
* User: ``https://matrix.to/#/@alice:example.org``
* Group: ``https://matrix.to/#/+example:example.org``

.. Note::
Event IDs have the potential to contain slashes in some `room versions <index.html#room-versions>`_.
No component of the URI should be URL encoded.
turt2live marked this conversation as resolved.
Show resolved Hide resolved
turt2live marked this conversation as resolved.
Show resolved Hide resolved

.. Note::
Room ID permalinks are unroutable as there is no reliable domain to send requests
to upon receipt of the permalink. Clients should do their best route Room IDs to
Expand Down