Roberto Polli

Support for eref + section references

16

## I wish To define keywords that reference specification sections. ``` normative: SEMANTICS: I-D.ietf-httpbis-semantics ... ## Notational Conventions {::boilerplate bcp14-tagged} The definitions of "representation", "selected representation", "representation data" are to...

## This PR clarifies language

Relationship with cache: are warnings returned in subsequent requests?

2

## I expect The spec to mention whether and how the "warning" attribute is part of the representation. Is that supposed to be returned even by subsequent GET requests? How...

## I expect more security considerations, eg. An intermediary could alter by chance or purpose a `Content-Warning` header. Implementors SHOULD validate the payload body to avoid that this results in:...

content-warning: add header considerations

4

# I expect to have header considerations https://tools.ietf.org/html/rfc7231#section-8.3.1 in content-warning spec ## Further questions - [x] which is the behavior of Content-Warning in case of no-content responses eg. HEAD? -...

## This PR Removes a normative part from the examples. This part contains a normative statement into an example. In RFC2119 [`SHOULD` is similar to `RECOMMENDED`](https://tools.ietf.org/html/rfc2119) while iiuc it's not...

content-warning: do we need to limit `warnings` semantic?

1

## Note The spec says ``` When an condition occurs that can not be defined as a "hard error" (i.e., that allows clients to continue treating the resulting response as...

Improve description of current API rate-limiting landscape.

7

## I expect The introduction on the current throttling landscape to be more comprehensive and detailed.

## This PR Adds the RateLimit-Scope field, sending an URI-reference. ## Note This PR lacks examples: do we need them? I leave this in Draft because I want to take...

[WIP] 70 throttling scope

1

## This PR Defines a throttling scope using parameters.