Reconsider guidance on odata.count position (public comment c201512e00001)

    • Type: Bug
    • Resolution: Fixed
    • Priority: Minor
    • V4.0_ERRATA03
    • Affects Version/s: V4.0_ERRATA02
    • Component/s: JSON Format
    • None
    • Environment:

      [Applied]

    • Hide

      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).

      Show
      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).
    • Show
      https://www.oasis-open.org/committees/download.php/57551/odata-json-format-v4.0-wd08-2016-02-17.docx

      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.

            Assignee:
            Unassigned
            Reporter:
            markdstafford
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: