Johan Stenberg (MSFT)

It is perfectly fine for us to provide guidance that disallows such use in Azure services. Which would make it more of a theoretical problem than a real one.

The [OData v4](http://docs.oasis-open.org/odata/odata-json-format/v4.0/os/odata-json-format-v4.0-os.html#_Toc372793091) specification says: > The value for the code name/value pair is a language-independent string. Its value is a service-defined error code. This code serves as a sub-status...

- Services *should* use a checksum of the representation of a resource rather than a last modified/version number if at all possible/computationally feasible. > While it may be tempting to...

@JeffreyRichter, `PATCH` is missing from your list of idempotent methods above - I assume that this was an oversight? I'd be fine with limiting the usage to methods that are...

Regarding the time limit, I'd like to specify a minimum value at least across Azure. And, yes, I picked 24 hours somewhat on random - it's long enough that the...

>> A client MUST NOT change request (query, body or header) parameters between requests using the same Idempotency-Token value. > If we're using Shared Key for Storage, we'll sign for...

@garethj-msft, agreed - if it is feasible for the service to determine changes by the client, returning a 400 response if the client changed values would indeed be preferable. Also...

Are we ever silently generating broken code as a result of lack of validation here?

Not even for a format change from vanilla string to date time?

The example above is, in fact, trying to explore what the correct way (in swagger 2.0) is to add an actual `any` type. `additionalProperties` only applies if the type is...