- From: Karol Szczepański via GitHub <sysbot+gh@w3.org>
- Date: Wed, 27 May 2020 21:20:21 +0000
- To: public-hydra-logs@w3.org
>You miss the point. Not really - if a profile can be expressed in multiple places (API Documentation, inlined, headers), it may happen that the declared profile may change. What then? Understanding all of them is one approach. Visibility and hiding would be another. Don't know which one is better/worse. >So what should happen now? 429 Precondition Failed? It depend on how we would specify the mechanism, but 412 Precondition Failed is not in scope (it is applicable to `If-Unmodified-Since` or `If-None-Match`). I was thinking about `Prefer` header, but it's just a hint. >Is it possible that you're overly complicating the proposal? I'd rather that the levels were unnecessary and that the core semantics are uniform. I just have to care about backward compatibility - introducing levels could save us from tampering with ranges as the interpretation of `hydra:Resource` may vary between levels. -- GitHub Notification of comment by alien-mcl Please view or discuss this issue at https://github.com/HydraCG/Specifications/issues/216#issuecomment-634946965 using your GitHub account
Received on Wednesday, 27 May 2020 21:20:22 UTC