[ https://issues.oasis-open.org/browse/ODATA-786?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ralf Handl updated ODATA-786:
-----------------------------
Description:
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 define specific path segments ($parameters, $returnType) 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.
was:
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 define specific path segments ($parameters, $returnType) 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.
> 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
>
>
> 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 define specific path segments ($parameters, $returnType) 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)
