Uploaded image for project: 'OASIS Open Data Protocol (OData) TC'
  1. OASIS Open Data Protocol (OData) TC
  2. ODATA-409

11.3.3.1 conflicts with conformance for intermediate and advanced OData

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Minor
    • Resolution: Fixed
    • Affects Version/s: V4.0_CSD01
    • Fix Version/s: V4.0_CSD02
    • Component/s: Protocol
    • Labels:
      None
    • Environment:

      [Applied]

      Description

      11.3.3.1 reads in part: "A service SHOULD support retrieving the raw value of a primitive type property."

      13.1.1 OData Minimal Conformance Level does not mention this capability.

      13.1.2 OData Intermediate Conformance Level reads in part: "MUST support /$value on media entities and individual properties (section Requesting a Property's Raw Value using $value)" contradicting 11.3.3.1.

      13.1.3 OData Advanced Conformance Level incorporates 13.1.2 by reference and so also contradicts 11.3.3.1.

      Part of the issue may lie in the use of may, should, must in the normative prose.

      For example: "A service SHOULD support retrieving the raw value of a primitive type property."

      Could be expressed:

      "The $value operator in a property value URL retrieves the raw value of a primitive type property."

      Organizationally, I would follow that with the rules for Edm.Binary, other properties and NULLs.

      For example, a client using a GET request with $value:

      http://host/service/Products(1)/Name/$value

        Attachments

          Activity

            People

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

              Dates

              • Created:
                Updated:
                Resolved: