[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=31895#action_31895 ] 

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

I'm not in favor of making things implicit; i.e., of having to understand and look at the type of the property in order to figure out that it is a navigation property (and can be used in things like $select) versus a simple property. Since there are real differences between how and where properties versus navigation properties are used, it is simpler to make it explicit by having separate elements.

Also, note that the partner attribute is optional for navigation properties (i.e., a property may be unidirectional).

> 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
>    Affects Versions: WD01
>         Environment: [Proposed]
>            Reporter: Ralf Handl
>             Fix For: WD01
>
>
> 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