There should be a way to specify that the support of things like top/skip are unspecified at the navigationpropertyrestrictions, in which case the specification on the entity set (if any) applies -- and if not, the default is taken (as specified on the entityset).

This could be facilitated by making top/skip (etc.) nullable, and with no default, in the navigation property restrictions.

In the example, the absence of TopSupported and SkipSupported in step 1 leads to omission of the parameters top and skip only because they are unsupported on the bound entity set in step 2:

OData services generated by SAP omit TopSupported or SkipSupported not just in step 1 but also on the bound entity set in step 2. Parameters top and skip are therefore included in the OpenAPI description.

SAP has entity set and entity type in 1:1 correspondence and capabilities are maintained per "entity". It is therefore not possible to support top and skip via navigation property (in step 1) but reject them when directly accessing the entity set (in step 2).