XMLWordPrintable

    Details

    • Type: Sub-task
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: V4.01_CS01
    • Fix Version/s: V4.01_CS02
    • Component/s: JSON Format
    • Labels:
      None
    • Environment:

      Applied

    • Proposal:
      Hide

      Same rules for JSON Batch message bodies and inlined/expanded streams:

      • Streams of media type application/json and subtypes are represented as "inlined JSON".
      • Streams of media type text/* are represented as JSON strings (quoted/escaped accordingly.
      • Streams of all other content types are base64url-encoded and represented as JSON strings. 

      Control information mediaContentType MUST be present for inlined streams.

      Show
      Same rules for JSON Batch message bodies and inlined/expanded streams: Streams of media type application/json and subtypes are represented as "inlined JSON". Streams of media type text/* are represented as JSON strings (quoted/escaped accordingly. Streams of all other content types are base64url-encoded and represented as JSON strings.  Control information mediaContentType MUST be present for inlined streams.
    • Resolution:
      Show
      https://www.oasis-open.org/committees/download.php/65505/odata-json-format-v4.01-wd06-2019-06-20.docx  

      Description

      JSON Batch represents JSON message bodies as "inlined JSON" and textual media types as JSON strings (with JSON string quoting/escaping), everything else is base64url-encoded and then packed into a JSON string.

      The rules for expanded/inlined stream properties are slightly different, which is inconsistent.

        Attachments

          Activity

            People

            • Assignee:
              handl Ralf Handl
              Reporter:
              handl Ralf Handl
            • Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: