[OASIS Issue Tracker] (ODATA-933) Allow using instance annotations in $filter

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

    [ https://issues.oasis-open.org/browse/ODATA-933?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=64483#comment-64483 ] 

Ralf Handl commented on ODATA-933:
----------------------------------

Proposal: always treat annotations as a path segment, which matches the path syntax in CSDL:

@Term#Qualifier to address an annotation value on the instance identified by the request pathPropertyName/@Term#Qualifier to address an annotation value on a property
NavigationPropertyName/@Term#Qualifier to address an annotation value on a related entity
... recursively with arbitrarily long path expressions

This simplifies the collision rule to "parameter alias wins over unqualified term"

> Allow using instance annotations in $filter
> -------------------------------------------
>
>                 Key: ODATA-933
>                 URL: https://issues.oasis-open.org/browse/ODATA-933
>             Project: OASIS Open Data Protocol (OData) TC
>          Issue Type: Bug
>          Components: OData URL Conventions
>    Affects Versions: V4.0_ERRATA02
>         Environment: New Query Capabilities
>            Reporter: Ralf Handl
>            Assignee: Ralf Handl
>             Fix For: V4.01_WD01
>
>
> Instance annotations are rather similar to dynamic properties with a pre-known expressive name, i.e. the client can deduce from the name what type the dynamic property has.
> For example: People?$filter=Age@numericValueException eq 'NaN'
> would retrieve all people for which age is not a number.
> If ODATA-735 gets accepted, clients can know up-front which instance annotations to expect, and can use them in filter conditions.
> Open a separate issue (ODATA-97) to consider use in $select,/$expand.



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