OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

odata message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


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


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

Ralf Handl updated ODATA-407:
-----------------------------

       Proposal:   (was: Allow declaration of navigation properties in metadata inside(?) complex types and check if the sample complex type (Address) used throughout the documents is realistic, if so state the reasoning somewhere, else modify or exchange the sample used.)
    Environment:     (was: [Proposed])
    Component/s: OData ATOM Format 
                     (was: OData CSDL)

Already allowed in CSDL, rephrased chapter 9 to make that more explicit.

What's missing is a representation in Atom (JSON already has one)

> 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 ATOM Format 
>    Affects Versions: V4.0_CSD01
>            Reporter: Stefan Drees
>            Priority: Minor
>             Fix For: V4.0_CSD02
>
>
> 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

        


[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]