OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

odata message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: [OASIS Issue Tracker] (ODATA-896) Reconsider guidance on odata.count position (public comment c201512e00001)


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

Michael Pizzo updated ODATA-896:
--------------------------------

    Proposal: 
For Errata 3: clarify that ordering constraint is only enforced for odata.streaming=true.

For server-driven paging, for odata.streaming=false, the odata.count must appear on at least the first page and may appear on subsequent pages (in which case it may vary from page to page).

  was:Make position of odata.count optional.


For Errata, all we can do is clarify that the restriction is only valid for odata.streaming=true responses.

For 4.01 we could consider allowing to be at the end, but in that case there is very little use as the client could simply count themselves.

Note that count is allowed to be approximate.

> Reconsider guidance on odata.count position (public comment c201512e00001)
> --------------------------------------------------------------------------
>
>                 Key: ODATA-896
>                 URL: https://issues.oasis-open.org/browse/ODATA-896
>             Project: OASIS Open Data Protocol (OData) TC
>          Issue Type: Bug
>          Components: OData JSON Format
>    Affects Versions: V4.0_ERRATA02
>            Reporter: Mark Stafford
>            Priority: Minor
>             Fix For: V4.0_ERRATA03
>
>
> In the JSON format, we say in section 12: "The odata.count name/value pair represents the number of entities in the collection. If present, it MUST come before the value name/value pair. "
> Per public feedback - https://lists.oasis-open.org/archives/odata-comment/201512/msg00001.html - we should consider softening this statement to SHOULD, and perhaps clarify which page(s) it should appear on.



--
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]