4.5.3: use $schemaversion query option instead of SchemaVersion header

    • Type: Bug
    • Resolution: Fixed
    • Priority: Major
    • V4.01_CS02
    • Affects Version/s: V4.01_CS01
    • Component/s: JSON Format
    • None
    • Environment:

      Applied

    • Hide

      Current text:


      If the URI references a metadata document (that is, it’s not just a fragment), and refers to a specific version of that metadata, then the object or name/value pair MUST also be annotated with the Core.SchemaVersion annotation, defined in [OData-VocCore], to indicate the version of the metadata document containing the corresponding version of the type. For streamed JSON responses, this annotation MUST immediately follow the type annotation. If the Core.SchemaVersion annotation is present, the Core.SchemaVersion header, defined in [OData-Protocol], SHOULD be used when retrieving the referenced metadata document.


      Change to


      If the URI references a metadata document (that is, it’s not just a fragment), it MAY refer to a specific version of that metadata document using the $schemaversion system query option defined in [OData-Protocol].


      That is: no need for an additional annotation with Core.SchemaVersion, just follow the @odata.type URL.

      Show
      Current text: If the URI references a metadata document (that is, it’s not just a fragment), and refers to a specific version of that metadata, then the object or name/value pair MUST also be annotated with the Core.SchemaVersion annotation, defined in [OData-VocCore] , to indicate the version of the metadata document containing the corresponding version of the type. For streamed JSON responses, this annotation MUST immediately follow the type annotation. If the Core.SchemaVersion annotation is present, the Core.SchemaVersion header, defined in [OData-Protocol] , SHOULD be used when retrieving the referenced metadata document. Change to If the URI references a metadata document (that is, it’s not just a fragment), it MAY refer to a specific version of that metadata document using the $schemaversion system query option defined in [OData-Protocol] . That is: no need for an additional annotation with Core.SchemaVersion, just follow the @odata.type URL.
    • Show
      https://www.oasis-open.org/committees/download.php/64120/odata-json-format-v4.01-wd06-2018-10-19.docx  

      Section 4.5.3 Control Information: type (odata.type) still refers to the SchemaVersion request header that has been replaced with a $schemaversion system query option with ODATA-994.

            Assignee:
            Unassigned
            Reporter:
            handl
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: