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

Document that the spec uses RFC 2119

Browse source 
Signed-off-by: HarHarLinks <2803622+HarHarLinks@users.noreply.github.com>
This commit is contained in:
HarHarLinks 2024-08-12 18:27:25 +02:00
parent f06ffc8176
commit 9b2a09ffce
1 changed files with 16 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

16
content/_index.md
View file

@ -99,6 +99,22 @@ 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 objects that need to be reliably and persistently pushed from A to B in
an interoperable and federated manner. an interoperable and federated manner.
### Bindingness of requirements
As a standards document, the Matrix Spec needs to signify the bindingness of the
individual features, APIs, procedures, or other requirements it describes.
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 bindingness of the above key words appearing in such a
section is only relevant if the section itself is applicable.
### Spec Change Proposals ### Spec Change Proposals
To propose a change to the Matrix Spec, see the explanations at To propose a change to the Matrix Spec, see the explanations at