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] (ODATA-516) Add super type Edm.AnyPath for Edm.PropertyPath, Edm.NavigationPropertyPath, and Edm.AnnotationPath


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

Ralf Handl updated ODATA-516:
-----------------------------

    Labels: AdoptionBlocker  (was: )

> Add super type Edm.AnyPath for Edm.PropertyPath, Edm.NavigationPropertyPath, and Edm.AnnotationPath
> ---------------------------------------------------------------------------------------------------
>
>                 Key: ODATA-516
>                 URL: https://issues.oasis-open.org/browse/ODATA-516
>             Project: OASIS Open Data Protocol (OData) TC
>          Issue Type: Improvement
>          Components: OData CSDL
>    Affects Versions: V4.0_CS01
>         Environment: [Proposed]
>            Reporter: Ralf Handl
>              Labels: AdoptionBlocker
>             Fix For: V4.1_WD01
>
>
> The three types Edm.PropertyPath, Edm.NavigationPropertyPath, and Edm.AnnotationPath take valid path expressions that end in a structural property, a navigation property, or an annotation.
> In some cases we don't need to restrict the last path segment, we just want to be sure that the path is valid in its context, so we don't want to use Edm.String.



--
This message was sent by Atlassian JIRA
(v6.2.2#6258)


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