[ODATA-1388] Make key aliases optional, clarify multiple to-one navigation hops - OASIS Technical Committees Issue Tracker

XML

Word

Printable

Proposal:
Hide

CSDL:

Make key aliases optional for keys with a path.

Clarify that multiple non-nullable to-one navigation hops can occur if the referenced key property of the directly related entity type itself is referenced from a directly related entity type etc.

URL Conventions:

If no key alias is provided for a related/nested primitive property, use the dash-separated path in parentheses-style keys, e.g. /something(foo-bar-id='abc')
Show
CSDL: Make key aliases optional for keys with a path. Clarify that multiple non-nullable to-one navigation hops can occur if the referenced key property of the directly related entity type itself is referenced from a directly related entity type etc. URL Conventions: If no key alias is provided for a related/nested primitive property, use the dash-separated path in parentheses-style keys, e.g. /something(foo-bar-id='abc')

When using an "association to one" as a key component, it is currently required to provide an alias for use in parentheses-style key syntax.

This can lead to "funny" aliases when the OData model is automatically derived from a conceptual model that does not know about OData key syntax.