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

Use RFC 2119 keywords across the content repository spec

Browse source
This commit is contained in:
Travis Ralston 2024-06-11 16:27:56 -06:00
parent 7a51ae879c
commit 4ed8f53968
3 changed files with 9 additions and 9 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

6
data/api/client-server/authed-content-repo.yaml
View file

@ -200,7 +200,7 @@ paths:
Servers SHOULD prefer to return `image/webp` thumbnails when supporting animation. Servers SHOULD prefer to return `image/webp` thumbnails when supporting animation.
When `true` and the media cannot be animated, such as in the case of a JPEG or PDF, the When `true` and the media cannot be animated, such as in the case of a JPEG or PDF, the
server should behave as though `animated` is `false`. server SHOULD behave as though `animated` is `false`.
example: false example: false
schema: schema:
type: boolean type: boolean
@ -454,8 +454,8 @@ components:
The maximum number of milliseconds that the client is willing to wait to The maximum number of milliseconds that the client is willing to wait to
start receiving data, in the case that the content has not yet been start receiving data, in the case that the content has not yet been
uploaded. The default value is 20000 (20 seconds). The content uploaded. The default value is 20000 (20 seconds). The content
repository can and should impose a maximum value for this parameter. The repository SHOULD impose a maximum value for this parameter. The
content repository may also choose to respond before the timeout. content repository MAY respond before the timeout.
example: 5000 example: 5000
schema: schema:
type: integer type: integer

6
data/api/client-server/content-repo.yaml
View file

@ -401,7 +401,7 @@ paths:
Servers SHOULD prefer to return `image/webp` thumbnails when supporting animation. Servers SHOULD prefer to return `image/webp` thumbnails when supporting animation.
When `true` and the media cannot be animated, such as in the case of a JPEG or PDF, the When `true` and the media cannot be animated, such as in the case of a JPEG or PDF, the
server should behave as though `animated` is `false`. server SHOULD behave as though `animated` is `false`.
example: false example: false
schema: schema:
type: boolean type: boolean
@ -688,8 +688,8 @@ components:
The maximum number of milliseconds that the client is willing to wait to The maximum number of milliseconds that the client is willing to wait to
start receiving data, in the case that the content has not yet been start receiving data, in the case that the content has not yet been
uploaded. The default value is 20000 (20 seconds). The content uploaded. The default value is 20000 (20 seconds). The content
repository can and should impose a maximum value for this parameter. The repository SHOULD impose a maximum value for this parameter. The
content repository may also choose to respond before the timeout. content repository MAY respond before the timeout.
example: 5000 example: 5000
schema: schema:
type: integer type: integer

6
data/api/server-server/content_repository.yaml
View file

@ -137,7 +137,7 @@ paths:
Servers SHOULD prefer to return `image/webp` thumbnails when supporting animation. Servers SHOULD prefer to return `image/webp` thumbnails when supporting animation.
When `true` and the media cannot be animated, such as in the case of a JPEG or PDF, the When `true` and the media cannot be animated, such as in the case of a JPEG or PDF, the
server should behave as though `animated` is `false`. server SHOULD behave as though `animated` is `false`.
example: false example: false
schema: schema:
type: boolean type: boolean
@ -265,8 +265,8 @@ components:
The maximum number of milliseconds that the client is willing to wait to The maximum number of milliseconds that the client is willing to wait to
start receiving data, in the case that the content has not yet been start receiving data, in the case that the content has not yet been
uploaded. The default value is 20000 (20 seconds). The content uploaded. The default value is 20000 (20 seconds). The content
repository can and should impose a maximum value for this parameter. The repository SHOULD impose a maximum value for this parameter. The
content repository may also choose to respond before the timeout. content repository MAY respond before the timeout.
example: 5000 example: 5000
schema: schema:
type: integer type: integer