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-517) Allow NavigationPropertyPath and PropertyPath expressions to end in annotations of appropriate type


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

Ralf Handl updated ODATA-517:
-----------------------------

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

> Allow NavigationPropertyPath and PropertyPath expressions to end in annotations of appropriate type
> ---------------------------------------------------------------------------------------------------
>
>                 Key: ODATA-517
>                 URL: http://tools.oasis-open.org/issues/browse/ODATA-517
>             Project: OASIS Open Data Protocol (OData) TC
>          Issue Type: Improvement
>          Components: OData CSDL
>    Affects Versions: V4.0_WD01
>         Environment: [Proposed][CS02]
>            Reporter: Ralf Handl
>             Fix For: V4.0_CSD03
>
>
> Currently NavigationPropertyPath expressions must end with a navigation property name, and PropertyPath expressions must end with the name of a structural property.
> On the other hand annotations add "virtual (navigation)properties", so a NavigationPropertyPath expression could as well end with an annotation of type Edm.EntityType or any concrete entity type (or a collection of these), and a PropertyPath expression could end with an annotation of types Edm.ComplexType, Edm.PrimitiveType, or a concrete primitive, enumeration, or complex type, or a type definition.
> An example for  "virtual navigation properties" is given in https://tools.oasis-open.org/issues/browse/ODATA-278 . The aim was that we can use  "virtual navigation properties" (and  "virtual properties") also as a NavigationPropertyPath (and as a PropertyPath ).  Currently  the expressions
>            <PropertyValue Property="NavigationPath" NavigationPropertyPath="@ACR.Supplier" /> and 
>            <PropertyValue Property="NavigationPath" NavigationPropertyPath="@ACR.PurchaseOrders" />
> in the example are invalid, because the  NavigationPropertyPath expressions must end with a navigation property name.

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