Mark Weitzel
Mark Weitzel
**From convo w/Jeffrey Richter** > I don't think we ever created a document on this (but we should update our guidelines). A client should apply its desired api-version to the...
Initial starting point: https://microsoft-my.sharepoint.com/:w:/p/jeffreyr/EYEA2y7OZ_VDmiV_9y1ctdcB6CZ5b38QuFw3WYu5lRK_Ng?e=6PH8YZ&isSPOFile=1
In Azure, we have additionalProperties that in swagger is just a free-form JSON object. While the free-form object allow greater expression, it also forces customer off a cliff where they...
Based on a [review comment](https://github.com/microsoft/api-guidelines/pull/264/files#r673477335) from Krzysztof: "It's possible that I missed it, but I think we should have a section on granularity of service operations. From time to time...
Sometimes, service teams need to implement the API for another service to be conformant, interoperability, etc. An example of this is mongo.db, [Apache Atlas](http://atlas.apache.org/api/v2/index.html) (e.g. for Purview), etc. We should...
8Mb was traditionally the size beyond which network hickups started to become problematic. However, we should confirm this is still a valid size or if changes in the network infrastructure...
We have encountered few situations where a "look before you leap" request pattern has been used. This can be useful for requests that are expected to return a large payload....
Similarly to above, links to example hypothesis would be good. _Originally posted by @KrzysztofCwalina in https://github.com/microsoft/api-guidelines/pull/264#r673322759_
The following rules need to be captured, either in a section on JSON models OR in a complementary document on OpenAPI. If you also support PUT then, then model depends...
In the LRO meeting, we realized during the `operation-id` discussion on #353 that how GUIDs are handled varies and could present some challenges. This issue isn't isolated to `operation-id` but...