[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] (ODATA-788) Clarify precidence rules for odata.include-annotations preference
Michael Pizzo created ODATA-788: ----------------------------------- Summary: Clarify precidence rules for odata.include-annotations preference Key: ODATA-788 URL: https://issues.oasis-open.org/browse/ODATA-788 Project: OASIS Open Data Protocol (OData) TC Issue Type: Bug Components: OData Protocol Affects Versions: V4.0_ERRATA02 Environment: [Proposed] Reporter: Michael Pizzo Priority: Minor Fix For: V4.0_ERRATA03 In the description for precedence of terms in the odata.include-annotations preference we say "The most specific identifier always takes precedence." This was intended to imply that, if you have two rules (Foo.* and Foo.Bar.*)that can match a particular annotation (Foo.Bar.blah), the most specific match wins (Foo.Bar). I recently got a question whether the wording implies that, if you have "Foo.*" and "Foo.Bar.*", then it's the same as "Foo.Bar.*" -- i.e., that adding the more specific identifier makes it as if the former was not specified. I don't think this will be a common misinterpretation, but perhaps we should clarify just in case. -- 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]