[OASIS Issue Tracker] (ODATA-786) Extend definition of edm:path expression

[OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org>]

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

Ralf Handl updated ODATA-786:
-----------------------------

    Labels: Gap Usability  (was: Usability)

> Extend definition of edm:path expression
> ----------------------------------------
>
>                 Key: ODATA-786
>                 URL: https://issues.oasis-open.org/browse/ODATA-786
>             Project: OASIS Open Data Protocol (OData) TC
>          Issue Type: Improvement
>          Components: OData CSDL
>    Affects Versions: V4.0_ERRATA02
>         Environment:   
>            Reporter: Martin Zurmuehl
>              Labels: Gap, Usability
>             Fix For: V4.1_WD01
>
>
> Currently we can annotated many csdl elements via embedded annotations or via the edm:Annotations element. 
> In the edm:path expression definition we had specified how a path expression is evaluated, if the annotation targets a entity container, entity set, entity type, complex type, navigation property of a structured type, or a property of a structured type.
> We should check for any other csdl element how the path expression could be evaluated, if an annotation targets it (if it make sense); e.g. if we target an edm:FunctionImport we can define specific path segments to fork to the parameters or to the ReturnType.
> With the extension of the edm:path we will automatically extend the definitions of the csdl elements based on edm:path like edm:propertypath.



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