[OASIS Issue Tracker] (ODATA-1065) Generalize Edm.AnyPath to be a path to any model element and rename it to Edm.ModelElementPath

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

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

Ralf Handl updated ODATA-1065:
------------------------------

    Proposal: 
Rename Edm.AnyPath (added in 4.01, so no incompatibility) to Edm.ModelElementPath

(The suffix Path is somewhat superfluous but consistent with the existing AnnotationPath, AnyPropertyPath, PropertyPath, and NavigationPropertyPath.)

  was:See summary


> Generalize Edm.AnyPath to be a path to any model element and rename it to Edm.ModelElementPath
> ----------------------------------------------------------------------------------------------
>
>                 Key: ODATA-1065
>                 URL: https://issues.oasis-open.org/browse/ODATA-1065
>             Project: OASIS Open Data Protocol (OData) TC
>          Issue Type: Improvement
>          Components: CSDL JSON , CSDL XML
>    Affects Versions: V4.01_CSD01
>         Environment: Proposed
>            Reporter: Ralf Handl
>             Fix For: V4.01_CSD02
>
>
> With ODATA-516 we introduced the abstract type Edm.AnyPath as an abstraction of Edm.AnnotationPath, Edm.PropertyPath, and Edm.NavigationPropertyPath.
> We now face situations where we want to reference other types of model elements, e.g. bound actions or functions.
> It seems wise to use the rather generic name "AnyPath" really for any path to any type of model element, which would
> a) postpone the need for actually adding specific types Edm.ActionPath, Edm.FunctionPath, Edm.EntityTypePath, ...
> b) allow us to later add these more specific types for the more common cases



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