[ https://issues.oasis-open.org/browse/ODATA-811?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=62968#comment-62968 ]
Michael Pizzo commented on ODATA-811:
-------------------------------------
Proposal:
-Annotations are applied wherever the type is used.
-Annotations are propagated along inheritance
-Annotations defined in a derived type take precedence over the same type defined in the base type.
-For structured annotations, should we apply merge (PATCH) semantics or replace (PUT) semantics?
-For collection-valued annotations, should it replace or append?
--probably replace, since there's no good way to remove...
> Define propagation and (partial) overriding of annotations
> ----------------------------------------------------------
>
> Key: ODATA-811
> URL: https://issues.oasis-open.org/browse/ODATA-811
> Project: OASIS Open Data Protocol (OData) TC
> Issue Type: Improvement
> Components: OData CSDL, Vocabularies
> Affects Versions: V4.0_ERRATA02
> Environment: Annotations
> Reporter: Ralf Handl
> Assignee: Ralf Handl
> Labels: Clarification
> Fix For: V4.01_WD01
>
>
> We regularly face situations where we want to "propagate" annotations on a model element to all places where this model element is used/referenced, e.g. annotate an entity type and then have that annotation apply to all entity sets, or annotate a type definition and have that annotation apply to all properties or action parameters of that type.
> An explicit annotation on one of the usage/reference points would then overrule/modify the annotation on the used/referenced construct.
> The current specification text seems to implicitly assume this behavior, but doesn't explicitly state rules on
> - where do annotations propagate to?
> - how are structured annotations modified? PATCH semantics if only partially specified?
--
This message was sent by Atlassian JIRA
(v6.2.2#6258)
