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-523) How do clients construct links from the context url for complex types?


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

Ralf Handl updated ODATA-523:
-----------------------------

    Fix Version/s: V4.0_CSD03
                       (was: V4.0_CS02)

> How do clients construct links from the context url for complex types?
> ----------------------------------------------------------------------
>
>                 Key: ODATA-523
>                 URL: http://tools.oasis-open.org/issues/browse/ODATA-523
>             Project: OASIS Open Data Protocol (OData) TC
>          Issue Type: Bug
>          Components: OData Protocol 
>    Affects Versions: V4.0_CS01
>         Environment: [Proposed]
>            Reporter: Michael Pizzo
>             Fix For: V4.0_CSD03
>
>
> Our current pattern for the context for a single complex types looks like this:
> {context-url}#{type-name}
> And a collection of complex types looks like this:
> {context-url}#Collection({type-name})
> However, in V4 we have add the ability for complex types to have relationships.Since one of the roles of the context is to provide the base for clients to construct links, how does the client compute relationship links using these context urls?
> For example, if I do ~Customers(1)/ns.Address, and Address has navigations to Country, how do represent that?
> Option 1: For complex types/collections of complex types, if there are navigation properties, you have to put the navigation links in the payload.
> Option 2: We modify the context url for properties to include the property path from the entity in the entity set:
> {context-url}/{entity-set}/$entity/{propertyName}
> This would be the same pattern for a property that was either single or a collection of primitive/complex types.

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