[OASIS Issue Tracker] Commented: (ODATA-188) Use <Property> element also for NavigationProperty

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

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

Michael Pizzo commented on ODATA-188:
-------------------------------------

Although Properties and Navigation Properties share some of the same attributes (there are attributes like Partner and ContainsTarget that only apply to NavigationProperty, and facets that only apply to properties), Properties and Navigation Properties are conceptually very different. Where/how they are used in the URI and payload are different, the annotations applied to each are likely to be very different, etc. 

Rather than simplifying the model, in this case trying to use a single element to represent these two very different things obscures those differences, making the model harder to understand. 

> Use <Property> element also for NavigationProperty
> --------------------------------------------------
>
>                 Key: ODATA-188
>                 URL: http://tools.oasis-open.org/issues/browse/ODATA-188
>             Project: OASIS Open Data Protocol (OData) TC
>          Issue Type: Improvement
>          Components: OData CSDL v1.0
>         Environment: [Proposed]
>            Reporter: Ralf Handl
>
> The syntax of the Property and the NavigationProperty element is almost identical. The only difference is that the Type attribute of a Property MUST NOT specify an entity type, while the NavigationProperty MUST specify an entity type (or a collection of...).

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