Clarify scope of property paths in transformations

XMLWordPrintable

    • Type: Improvement
    • Resolution: Fixed
    • Priority: Minor
    • V4.0_CSD04
    • Affects Version/s: V4.0_CS02
    • Component/s: Data Aggregation
    • None
    • Environment:

      Applied

    • Hide

      Add another sentence to section 3, at the end of the third para (enclosed with *):
      "So the actual (or relevant) structure of each intermediary result will resemble a projection of the original data model that could also have been formed using the standard system query options $expand and $select defined in [OData-Protocol], with dynamic properties representing the aggregate values. The parameters of set transformations allow specifying how the result instances are constructed from the input instances. *This especially means that all property paths relate to the structure of the immediate input set.*"

      Show
      Add another sentence to section 3, at the end of the third para (enclosed with *): "So the actual (or relevant) structure of each intermediary result will resemble a projection of the original data model that could also have been formed using the standard system query options $expand and $select defined in [OData-Protocol] , with dynamic properties representing the aggregate values. The parameters of set transformations allow specifying how the result instances are constructed from the input instances. *This especially means that all property paths relate to the structure of the immediate input set.*"

      Property paths in transformations always relate to the structure of the immediate input set, which is either the collection identified by the request resource path or the output of the preceding transformation.
      For some transformations, this has been specified explicitly, e.g. in section 3.1 for the aggregate transformation: “an expression valid in a $filter system query option on the input set”. But not for all, e.g. section 3.12 does not make a statement for the expand transformation. In order to avoid any possible misinterpretation or confusion, the document should spell this out clearly.

            Assignee:
            Unassigned
            Reporter:
            gerald.krause1
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: