2.13 Naming Conventions for URLs

Resource kinds take the plural form in SData URLs. For example, accounts, contacts and salesOrders.

SData uses camel case as its standard for various components in a URL. This is where the first letter of a word is lower case. Where words are combined, each word that follows starts with a capital letter. For example, myApp.

As a general rule, SData URLs are case sensitive. SData providers MUST format all the URLs that they return to their consumers with consistent casing, and they SHOULD use camel case for the URL components.

SData providers SHOULD NOT use case-only differences to differentiate between resources. For example, an SData provider is not allowed to expose salesOrders and salesorders as two different resource kinds.

SData providers MAY accepts URLs that have case differences, but consumers SHOULD NOT rely on this feature being generally supported. On the other hand, as stated above, SData providers MUST format all their URLs with consistent casing.

The above rules do not apply to the data components contained in URLs. For example, if an application has case sensitive primary keys, it may very well treat accounts(‘a0’) and accounts(‘A0’) as two different resources. Case sensitivity on the data components is handled by application specific rules.

SData providers MUST comply with the above rules.