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

Document that the spec uses RFC 2119 (#1928)

Browse source 
Signed-off-by: HarHarLinks <2803622+HarHarLinks@users.noreply.github.com>
This commit is contained in:
Kim Brose 2024-08-15 11:31:50 +02:00 • committed by GitHub
parent 87de68c35e
commit dc017c2dd3
No known key found for this signature in database
GPG key ID: B5690EEEBB952194
9 changed files with 22 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

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

@ -0,0 +1 @@
Document that the spec uses RFC 2119. Contributed by @HarHarLinks.

1
changelogs/application_service/newsfragments/1928.clarification Normal file
View file

@ -0,0 +1 @@
Document that the spec uses RFC 2119. Contributed by @HarHarLinks.

1
changelogs/client_server/newsfragments/1928.clarification Normal file
View file

@ -0,0 +1 @@
Document that the spec uses RFC 2119. Contributed by @HarHarLinks.

1
changelogs/identity_service/newsfragments/1928.clarification Normal file
View file

@ -0,0 +1 @@
Document that the spec uses RFC 2119. Contributed by @HarHarLinks.

1
changelogs/internal/newsfragments/1928.clarification Normal file
View file

@ -0,0 +1 @@
Document that the spec uses RFC 2119. Contributed by @HarHarLinks.

1
changelogs/push_gateway/newsfragments/1928.clarification Normal file
View file

@ -0,0 +1 @@
Document that the spec uses RFC 2119. Contributed by @HarHarLinks.

1
changelogs/room_versions/newsfragments/1928.clarification Normal file
View file

@ -0,0 +1 @@
Document that the spec uses RFC 2119. Contributed by @HarHarLinks.

1
changelogs/server_server/newsfragments/1928.clarification Normal file
View file

@ -0,0 +1 @@
Document that the spec uses RFC 2119. Contributed by @HarHarLinks.

14
content/_index.md
View file

@ -99,6 +99,20 @@ services - be that for instant messages, VoIP call setups, or any other
objects that need to be reliably and persistently pushed from A to B in
an interoperable and federated manner.
### Requirement levels
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD",
"SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" across all parts of the
specification are to be interpreted as described in
[RFC 2119](https://datatracker.ietf.org/doc/html/rfc2119).
Some entire sections of the specification might be optional depending on the
circumstances. For example, the
[modules of the client-server API](/client-server-api/#modules)
apply depending on the use case. The requirement level expressed by the above
key words appearing in such a section is only relevant if the section itself is
applicable.
### Spec Change Proposals
To propose a change to the Matrix Spec, see the explanations at