[OASIS Issue Tracker] (ODATA-1016) 11.2.9: clarify /$count segment and system query options

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

Michael Pizzo updated ODATA-1016:
---------------------------------

    Proposal: 
Replace

The returned count MUST NOT be affected by $top, $skip, $orderby, or $expand. Content negotiation using the Accept request header or the $format system query option is not allowed with the path segment /$count.

with

Clients SHOULD NOT combine system query options $top, $skip, $orderby, $expand, and $format with the path segment /$count. The result of such a request is undefined.

  was:
Replace

The returned count MUST NOT be affected by $top, $skip, $orderby, or $expand. Content negotiation using the Accept request header or the $format system query option is not allowed with the path segment /$count.

with

The system query options $top, $skip, $orderby, $expand, and $format as well as content negotiation using the Accept request header are not allowed with the path segment /$count.


> 11.2.9: clarify /$count segment and system query options
> --------------------------------------------------------
>
>                 Key: ODATA-1016
>                 URL: https://issues.oasis-open.org/browse/ODATA-1016
>             Project: OASIS Open Data Protocol (OData) TC
>          Issue Type: Improvement
>          Components: OData Protocol
>    Affects Versions: V4.0_ERRATA03
>            Reporter: Ralf Handl
>            Priority: Minor
>             Fix For: V4.01_CSD02, V4.0_ERRATA04
>
>
> Part 1, section 11.2.9 on the /$count path segment states:
> The returned count MUST NOT be affected by $top, $skip, $orderby, or $expand. 
> Part 2, section 5.1 states that only $filter and $search are allowed for paths ending in /$count.
> "Not allowed" is clearer than "must not be affected by", so rephrase part 1.



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