OASIS Open Data Protocol (OData) TCIcon indicating the project type

OASIS Open Data Protocol (OData) TC

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

Represent all type references as JSON Schema types/references

    Details

    • Type: Improvement
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: V4.0_WD01
    • Fix Version/s: V4.0_WD01
    • Component/s: CSDL JSON
    • Labels:
      None
    • Environment:

      Applied

      Description

      The value of the "type" keyword should always be a JSON Schema (reference) instead of a qualified type name.

      This affects term definitions, parameters, return types, entity sets, singletons

        Attachments

          Activity

          Ascending order - Click to sort in descending order
          Hide
          Permalink
          handl Ralf Handl added a comment -

          This change shows that many of the terms in our standard vocabularies are nullable: we should check whether this makes sense for the term semantics, especially for all of the tagging terms using type Core.Tag.

          Show
          handl Ralf Handl added a comment - This change shows that many of the terms in our standard vocabularies are nullable: we should check whether this makes sense for the term semantics, especially for all of the tagging terms using type Core.Tag.
          Hide
          Permalink
          handl Ralf Handl added a comment -

          Using $ref to reference functions from function imports and actions from action imports required restructuring actions and functions: these are now objects with one property per function (resp. action) name, and if the function (or action) has overloads, the value is an array of function definitions, otherwise it's a single function definition. See second change to Aggregation vocab for the difference.

          Show
          handl Ralf Handl added a comment - Using $ref to reference functions from function imports and actions from action imports required restructuring actions and functions: these are now objects with one property per function (resp. action) name, and if the function (or action) has overloads, the value is an array of function definitions, otherwise it's a single function definition. See second change to Aggregation vocab for the difference.

            People

            • Assignee:
              mikep Michael Pizzo (Inactive)
              Reporter:
              handl Ralf Handl
            • Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: