[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] (ODATA-642) $select wording clarification; specify, rather than restrict, set of properties
[ https://tools.oasis-open.org/issues/browse/ODATA-642?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Pizzo updated ODATA-642: -------------------------------- Environment: [Applied] (was: [Proposed]) > $select wording clarification; specify, rather than restrict, set of properties > ------------------------------------------------------------------------------- > > Key: ODATA-642 > URL: https://tools.oasis-open.org/issues/browse/ODATA-642 > Project: OASIS Open Data Protocol (OData) TC > Issue Type: Bug > Components: OData URL Conventions > Affects Versions: V4.0_OS > Environment: [Applied] > Reporter: Michael Pizzo > Priority: Minor > Fix For: V4.0_ERRATA01 > > > http://docs.oasis-open.org/odata/odata/v4.0/os/part2-url-conventions/odata-v4.0-os-part2-url-conventions.html#_Toc372793861 > specifies that: "The $select system query option allows clients to requests a limited set of properties for each entity or complex type." > Since, in the absence of a $select, we allow the service to choose a default set of properties to return, $select can be used not only to restrict but also to expand the set of properties to be selected. > Some readers have been concerned that "limited" corresponds to the default set, as opposed to the available properties. -- 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]