Garrett DeBruin

The `AlternateKeyODataUriResolver` does not always find alternate keys from base types. ### Assemblies affected There may be more, but Core 7.12.2 has this issue. ### Reproduce steps You can find...

The current guidance does not pass the schema validation. I have updated it to reflect what actually passes schema validation (except for a single suppression that is required). You can...

Porting [this](https://dev.azure.com/msazure/One/_git/AD-AggregatorService-Wiki/pullrequest/5809345?_a=files&path=/API/Design/Modeling-patterns/Value-Based-Property-Validity.md) PR from the old repo.

Discussed previously, this PR adds the guidance to avoid the filter-as-segment OData feature and instead use a composable function which accepts an expression parameter for those scenarios where operations on...

Adding the guidance pattern according to [this](https://microsoft.sharepoint.com/teams/APICouncil/_layouts/15/Doc.aspx?sourcedoc=%7B3569deb7-5543-404f-99b0-70554b7f8778%7D&action=edit&wd=target(ADRs.one%7C0edc1435-5069-4f42-8318-bf31c71c4e37%2FADR-024%20Using%20functions%20as%20query%20parameter%20aliases%7Ce157a2d9-7960-4f08-b0da-8e22ac5248c6%2F)&wdorigin=NavigationUrl&share=IgG33mk1Q1VPQJmwcFVLf4d4AQ7bKVE-D30Of6JCTvaTqbc) ADR. The pattern is to use OData functions as "aliases" for the more complicated or common OData query options for robust APIs that...

The [guidance](https://github.com/microsoft/api-guidelines/blob/vNext/Guidelines.md#93-collection-url-patterns) for point queries: > Whenever possible, services MUST support the "/" pattern. For example: is vague. It is unclear "whenever" a service "must" support point queries. We should...

I'm adding guidance to suggest that collections should be entity types instead of complex types because they can be modified piecewise, while collections of complex types must always be replaced,...