[OASIS Issue Tracker] (ODATA-755) Construction rule for canonical URL is incomplete

[OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org>]

     [ https://issues.oasis-open.org/browse/ODATA-755?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Michael Pizzo updated ODATA-755:
--------------------------------

    Proposal: 
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).

  was:
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 lexicographical order.

Rationale for lexicographical order: in JSON CSDL the key properties are represented as a "hash map" object, and JSON (de)serializers may not preserve the order of the key properties.


Proposal refined in 2014-12-11 meeting.

> Construction rule for canonical URL is incomplete
> -------------------------------------------------
>
>                 Key: ODATA-755
>                 URL: https://issues.oasis-open.org/browse/ODATA-755
>             Project: OASIS Open Data Protocol (OData) TC
>          Issue Type: Bug
>          Components: OData ABNF Construction Rules, OData CSDL, OData JSON Format, OData URL Conventions 
>    Affects Versions: V4.0_ERRATA02
>            Reporter: Ralf Handl
>             Fix For: V4.0_ERRATA03
>
>
> 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.



--
This message was sent by Atlassian JIRA
(v6.2.2#6258)