[OASIS Issue Tracker] Commented: (ODATA-338) Representation of entity references in odata.metadata annotation

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

    [ http://tools.oasis-open.org/issues/browse/ODATA-338?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=33052#action_33052 ] 

Michael Pizzo commented on ODATA-338:
-------------------------------------

Agreed, it should be valid to refer directly to the entityset where the entityset is known.

For things like containment we may need to specify a navigation path, but this applies to the general cases of returning contained entities, whether as entities or as entity references.

In general, rules for $ref should be same as rules w/o $ref, except that "/$ref" follows the {entity-set} (we should be able to think of /$ref as a "cast" to a ref.)

> Representation of entity references in odata.metadata annotation
> ----------------------------------------------------------------
>
>                 Key: ODATA-338
>                 URL: http://tools.oasis-open.org/issues/browse/ODATA-338
>             Project: OASIS Open Data Protocol (OData) TC
>          Issue Type: Improvement
>          Components: OData ATOM Format , OData JSON Format
>         Environment: [Proposed]
>            Reporter: Hubert Heijkers
>
> The proposed representation of an entity reference in section 4.4.1 of the JSON Format includes a navigation property in the path. Entity references can also be taken directly from entities in entity sets, and therefore not have a navigation property to be used, but I also believe that the referenced entity, or set thereof, was the result of referring to a navigation property that the result still would simply be an entity reference, or a set thereof, and that therefore the navigation property path is not required (read: has no particular function) in identifying the type of entity reference.
> My proposal would be to remove the navigation property in this context.

-- 
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