[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] (ODATA-975) Consider allowing usie of instance annotations in $select and $expand
Michael Pizzo created ODATA-975: ----------------------------------- Summary: 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: 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. Consider this also for $select, would be more explicit than in an odata.include-annotations preference. -- 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]