[OASIS Issue Tracker] Updated: (ODATA-441) Specify canonical form of entity-id

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

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

Michael Pizzo updated ODATA-441:
--------------------------------

    Proposal: 
By convention, the entity-id does not end with a cast segment even if the entity type is part of an inheritance hierarchy.
The canonical representation of the navigation link is the id plus the navigation property with a possible cast segment as required.
The canonical representation of the association link is to append /$ref to the navigation link.
Clients have to append a cast segment when constructing property/navigation URLs as appropriate.
Clients can always append a single cast segment even if the entity type is not part of an inheritance hierarchy.

  was:
The entity-id does not end with a cast segment even if the entity type is part of an inheritance hierarchy.
Clients have to append a cast segment when constructing property/navigation URLs as appropriate.
Clients can always append a single cast segment even if the entity type is not part of an inheritance hierarchy.


> Specify canonical form of entity-id
> -----------------------------------
>
>                 Key: ODATA-441
>                 URL: http://tools.oasis-open.org/issues/browse/ODATA-441
>             Project: OASIS Open Data Protocol (OData) TC
>          Issue Type: Bug
>          Components: OData Protocol , OData URL Conventions 
>    Affects Versions: V4.0_CSD01
>         Environment: [Proposed]
>            Reporter: Ralf Handl
>             Fix For: V4.0_CSD02
>
>


-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://tools.oasis-open.org/issues/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira