[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:
-----------------------------

    Environment: Proposed  (was:   )
       Proposal: 
Allow external targeting for

- Action via MySchema.MyAction, annotation applies to all overloads
- Annotation via MyTargetPath/@MySchema.MyTerm#MyQualifier
- Function via MySchema.MyFunction, annotation applies to all overloads
- Parameter via MySchema.MyActionOrFunction/MyParameter, annotation applies to parameter of this name across all overloads
- ReturnType via MySchema.MyActionOrFunction/$returntype, applies to all overloads

> 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: Proposed
>            Reporter: Martin Zurmuehl
>              Labels: AdoptionBlocker, Usability
>             Fix For: V4.01_WD01
>
>
> Some model elements can only be annotated via inline annotations but not targeted via the edm:Annotations element. As annotation documents and service metadata may have different owners or life-cycles this restricts authors of annotation documents.
> 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 all other CSDL elements how the path expression could be extended to allow external targeting, e.g. if we target an edm:FunctionImport we can use the parameter names as path segments (which would be consistent with the syntax of the EntitySetPath attribute), and have a special path segment to address the ReturnType, e.g. $ReturnType or $out, treating it as an implicitly named "return parameter".
> 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)