Filip/matrix-spec
1
0
Fork 0
mirror of https://github.com/matrix-org/matrix-spec synced 2026-03-23 19:44:09 +01:00
Code Issues Actions 1 Packages Projects Releases Wiki Activity

appendices.md: expand URI scheme by actions to include knock

Browse source 
Resolves: #1015

Signed-off-by: Aminda Suomalainen <suomalainen+git@mikaela.info>
This commit is contained in:
Aminda Suomalainen 2022-04-17 08:34:16 +03:00
parent b9500a7548
commit d3530bcb63
No known key found for this signature in database
2 changed files with 6 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

1
changelogs/appendices/newsfragments/1030.clarification Normal file
View file

@ -0,0 +1 @@
Clarify that URI scheme actions may include `knock`

6
content/appendices.md
View file

@ -691,7 +691,7 @@ type-qualifier = segment-nz "/" ; as defined in RFC 3986
id-without-sigil = string ; as defined in Matrix identifier spec above
query = query-element *( "&" query-item )
query-item = action / routing / custom-query-item
action = "action=" ( "join" / "chat" )
action = "action=" ( "join" / "chat" / "knock" )
routing = "via=” authority
custom-query-item = custom-item-name "=" custom-item-value
custom-item-name = 1*unreserved ; reverse-DNS name
@ -745,6 +745,10 @@ this specification are the following:
form of Canonical DMs should reuse existing DMs instead of creating new ones
if available. The client should prompt for confirmation prior to creating the
DM, if the user isn't being redirected to an existing canonical DM.
* `action=knock` - Describes an intent for the client to knock the room described
by the URI and thus is only valid on URIs which are referring to a room (it
has no meaning and is ignored otherwise). The client should prompt for confirmation
prior to knocking the room, if the user isn't already part of the room.
* `via` - Can be used to denote which servers (`authority` grammar) to attempt to resolve
the resource through, or take `action` through. An example of using `via` for
routing Room IDs is described [below](#routing), and is encouraged for use in