Roberto Polli
Roberto Polli
@rob-metalinkage > . I'm also looking into this in the context of a community with a series of JSON schemas Interesting! Could you share more details about your goals (e.g....
Related to #386
@michaelcpuckett ~if you reflect in this use case too, I can close #386 and continue under this issue.~ re-reading this issue I understand it's only related to `integer` values, sorry...
Ottimo, ovviamente si potrebbe fare un discorso analogo per le API dell'app android.
It is fair to adopt the ratelimit model without referencing the I-D too :)
@wurstbrot MITRE is following the URI road here https://d3fend.mitre.org/technique/d3f:FileAnalysis/ Following this too allows us to integrate with them... I'll PR an hypothesis, but the webapp should be updated then...
@wurstbrot We could just reference a threat / risk taxonomy and generate risk description from there.
@tkrop @whiskeysierra the I-D proposal is essentially the result of this discussion https://github.com/zalando/restful-api-guidelines/issues/379#issuecomment-392705421 It's fine to stick with the `X-` for now :) OTOH it would be great if Zalando...
Update: the draft is now under the ietf umbrella, yet not RFC... draft-ietf-httpapi-ratelimit-headers feel free to review and support it to finalize the standardization https://twitter.com/ioggstream/status/1340038502529024000?s=19
@kingthorin great! Once the two base PRs are merged I'll start working on that #6408 #6406