[ODATA-755] Construction rule for canonical URL is incomplete - OASIS Technical Committees Issue Tracker

XML

Word

Printable

Proposal:

Hide

For single-part keys the canonical key predicate does not contain the key property name.

For multi-part keys the canonical key predicate lists the key properties in the order they appear in the CSDL.

Fix JSON Schema so that there is an ordering of key properties (i.e., through an array of key/value pairs).

Show
For single-part keys the canonical key predicate does not contain the key property name. For multi-part keys the canonical key predicate lists the key properties in the order they appear in the CSDL. Fix JSON Schema so that there is an ordering of key properties (i.e., through an array of key/value pairs).
Resolution:

Hide

https://www.oasis-open.org/committees/download.php/54713/odata-v4.0-wd08-part2-url-conventions-2014-12-12.docx

Show
https://www.oasis-open.org/committees/download.php/54713/odata-v4.0-wd08-part2-url-conventions-2014-12-12.docx

JSON Format 4.5.7 allows omitting the odata.id if it is identical to the canonical URL of the entity.

URL Conventions 4.3.1 defines how the canonical URL is constructed BUT does not specify how the key predicate is to be constructed canonically.

ABNF allows "synonyms" for the key predicate

for a single key property the key predicate may contain or omit the key property name
for multiple key properties no order is required for the key properties

As a consequence a client cannot know how to construct the canonical URL from the entity set and key properties.