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

Chapter 3: remove restriction for input type of bound functions

    XMLWordPrintable

    Details

    • Type: Improvement
    • Status: Resolved
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: V4.0_CSD03
    • Fix Version/s: V4.0_CSD04
    • Component/s: Data Aggregation
    • Labels:
      None
    • Environment:

      Applied

    • Proposal:
      Hide

      Prose spec chapter 3, second-to-last paragraph new:

      Service-defined bound functions that take a collection as their binding parameter MAY be used as set transformations within $apply if the type of the binding parameter matches the type of the result set of the preceding transformation. If it returns a collection, further transformations can follow the bound function. The parameter syntax for bound function segments is identical to the parameter syntax for bound functions in resource path segments or $filter expressions. See section 7.6 for an example.

      old:

      Service-defined bound functions that take an entity set as their binding parameter MAY be used as set transformations within $apply if the type of the binding parameter matches the type of the result set of the preceding transformation. If it returns an entity set, further transformations can follow the bound function. The parameter syntax for bound function segments is identical to the parameter syntax for bound functions in resource path segments or $filter expressions. See section 7.6 for an example.

      ABNF new:

      customFunction = namespace "." ( entityColFunction / complexColFunction / primitiveColFunction ) functionExprParameters

      old:

      customFunction = namespace "." entityColFunction functionExprParameters

      Show
      Prose spec chapter 3, second-to-last paragraph new: Service-defined bound functions that take a collection as their binding parameter MAY be used as set transformations within $apply if the type of the binding parameter matches the type of the result set of the preceding transformation. If it returns a collection, further transformations can follow the bound function. The parameter syntax for bound function segments is identical to the parameter syntax for bound functions in resource path segments or $filter expressions. See section 7.6 for an example. old: Service-defined bound functions that take an entity set as their binding parameter MAY be used as set transformations within $apply if the type of the binding parameter matches the type of the result set of the preceding transformation. If it returns an entity set, further transformations can follow the bound function. The parameter syntax for bound function segments is identical to the parameter syntax for bound functions in resource path segments or $filter expressions. See section 7.6 for an example. ABNF new: customFunction = namespace "." ( entityColFunction / complexColFunction / primitiveColFunction ) functionExprParameters old: customFunction = namespace "." entityColFunction functionExprParameters
    • Resolution:
      Show
      https://github.com/oasis-tcs/odata-abnf/blob/master/abnf/odata-aggregation-abnf.txt already updated; no PR

      Description

      When generalizing $apply from "entities" to "instances" of any type we forgot to reformulate the paragraph on service defined "custom functions".

       

      And better use "structured values" instead of "instances".

        Attachments

          Activity

            People

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

              Dates

              • Created:
                Updated:
                Resolved: