[OASIS Issue Tracker] (ODATA-975) Consider allowing usie of instance annotations in $select and $expand

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

     [ https://issues.oasis-open.org/browse/ODATA-975?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Michael Pizzo updated ODATA-975:
--------------------------------

    Description: 
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.

In OData-933 we added use of instance annotations to $filter.  It seems consistent to support in $select (and $expand), but we don't have a use case.

Opening this issue to track the fact that we considered, and are open, to adding support to $select (and perhaps $expand) if we come up with some interesting use cases.

If supported, make sure we consider contextUrl, etc.

  was:
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.

Consider this also for $select, would be more explicit than in an odata.include-annotations preference.


> Consider allowing usie of instance annotations in $select and $expand
> ---------------------------------------------------------------------
>
>                 Key: ODATA-975
>                 URL: https://issues.oasis-open.org/browse/ODATA-975
>             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
>             Fix For: V5.0_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.
> In OData-933 we added use of instance annotations to $filter.  It seems consistent to support in $select (and $expand), but we don't have a use case.
> Opening this issue to track the fact that we considered, and are open, to adding support to $select (and perhaps $expand) if we come up with some interesting use cases.
> If supported, make sure we consider contextUrl, etc.



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