Consider making odata- prefix optional in headers, preference values, format parameters

    • Type: Bug
    • Resolution: Fixed
    • Priority: Major
    • V4.01_WD01
    • Affects Version/s: V4.0_ERRATA03
    • Component/s: Protocol
    • None
    • Environment:

      [Propose]

      We defined our own namespacing mechanism for things like preferences and headers by prefixing with odata. Specifically:

      OData Headers:
      OData-Version
      OData-MaxVersion
      OData-Isolation
      OData-EntityId
      OData-SchemaVersion

      OData Preferences:
      odata.allow-entityreferences
      odata.callback
      odata.continue-on-error
      odata.include-annotations
      odata.maxpagesize
      odata.track-changes
      odata.omit-values

      OData format parameters:
      odata.metadata
      odata.streaming

      In the interest of making some of these conventions and behaviors more broadly adopted, should we consider supporting some of them without the "odata" prefix?

            Assignee:
            Michael Pizzo (Inactive)
            Reporter:
            Michael Pizzo (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: