wholetrans/docs-matrix-spec
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity

Apply suggestions from code review

Browse source
This commit is contained in:
Kitsune Ral 2021-01-19 19:44:15 +01:00
parent 11d2529a5e
commit a32d7f5027
1 changed files with 6 additions and 5 deletions
Download patch file Download diff file Expand all files Collapse all files

11
proposals/2312-matrix-uri.md
View file

@ -220,7 +220,7 @@ of a given Matrix entity:
```text
path = entity-descriptor ["/" entity-descriptor]
entity-descriptor = nonid-segment / type-qualifier id-without-sigil
non-id-segment = segment-nz ; as defined in RFC 3986, see also below
nonid-segment = segment-nz ; as defined in RFC 3986, see also below
type-qualifier = segment-nz "/" ; as defined in RFC 3986, see also below
id-without-sigil = string ; as defined in Matrix identifier spec, see below
```
@ -310,10 +310,11 @@ it is not proposed here to generate or read the authority part of the URI.
Clients MAY introduce and recognise custom query items, according to
the following rules:
- the name of the item MUST follow the reverse-DNS (aka "Java package")
naming convention - e.g., a custom action item for Element clients would be
named `io.element.action`, for Quaternion - `com.github.quaternion.action`,
etc.
- the name of a custom item MUST follow the reverse-DNS (aka "Java package")
naming convention, as per
[MSC2758](https://github.com/matrix-org/matrix-doc/pull/2758) - e.g.,
a custom action item for Element clients would be named `io.element.action`,
for Quaternion - `com.github.quaternion.action`, etc.
- the value of the item can be any content but its representation in the URI
MUST follow the general RFC requirements for the query part; on top of that,
if the raw value contains `&` it MUST be percent-encoded.