[OASIS Issue Tracker] Created: (ODATA-407) Navigation Properties in Complex Types (public comment c201305e00012)

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

Navigation Properties in Complex Types (public comment c201305e00012)
---------------------------------------------------------------------

                 Key: ODATA-407
                 URL: http://tools.oasis-open.org/issues/browse/ODATA-407
             Project: OASIS Open Data Protocol (OData) TC
          Issue Type: Improvement
          Components: OData CSDL
    Affects Versions: V4.0_CSD01
         Environment: [Proposed]
            Reporter: Stefan Drees
            Priority: Minor


The public comment [c201305e00012](https://lists.oasis-open.org/archives/odata-comment/201305/msg00012.html) with title "Navigation Properties in Complex Types" states:


"""
[OData-Part3] (CSDL Defintion) states:

As structural and navigation properties MAY be returned by the service on instances of any structured type, whether or not the type is marked as open. Clients MUST always be prepared to deal with additional properties on instances of any structured type, see [OData-Protocol].

In this light, I wonder, what is the reason tat complex types cannot declare navigation properties in metadata? I would serve a lot of real -life cases
For example, the Address complex type used throughout the documents is a bit unrealistic, as in most real cases it should contain a navigation property "Country", referencing another enitity, not just text representaion
"""

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