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] Commented: (ODATA-481) Annotation/Navigation/Path expressions: allow paths to continue after multi-valued navigation to e.g. drill into complex properties


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

Michael Pizzo commented on ODATA-481:
-------------------------------------

I'm not a fan of saying multiple multi-valued navigations define the union of all targeted collections. Do we need to do this?

Note that <PropertyPath> references <Path> for rules, so we need to make sure the rules we define make sense for <PropertyPath> or break that reference. For <PropertyPath> we clearly need to support traversing multi-valued collections for containment.

i.e., if Orders contains Details, and I want to specify about Discount property on Detail (i.e., that it's not sortable, since sortability is defined on the entity set level) I need to specify the property path from the Order as:

<PropertyPath>Details/Amount<PropertyPath>

> Annotation/Navigation/Path expressions: allow paths to continue after multi-valued navigation to e.g. drill into complex properties
> -----------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: ODATA-481
>                 URL: http://tools.oasis-open.org/issues/browse/ODATA-481
>             Project: OASIS Open Data Protocol (OData) TC
>          Issue Type: Improvement
>          Components: OData CSDL
>    Affects Versions: V4.0_CS01
>         Environment: [Proposed][CS02]
>            Reporter: Ralf Handl
>             Fix For: V4.0_CSD03
>
>
> CSDL 14.5.12 restricts path expressions to contain at most one multi-valued navigation property which can only be followed by a single type cast or term cast.
> This is overly restrictive: drilling into a complex type path after a navigation is straight-forward, and even multiple multi-valued navigations could be resolved by building the union of all targeted collections.

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