[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] (ODATA-811) Define propagation and (partial) overriding of annotations
Ralf Handl created ODATA-811: -------------------------------- Summary: 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 Affects Versions: V4.0_ERRATA02 Reporter: Ralf Handl Fix For: V4.1_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)
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]