Minutes of 2026-02-11 Meeting #541

[HeikoTheissen]

1. Roll call [8:00]
   Meeting link
   Meeting ID: 337 385 595 564 22
   Attendees:

   • George Ericson (Dell)
   • Stefan Hagen (Individual)
   • Ralf Handl (SAP)
   • Hubert Heijkers (IBM)
   • Ling Jin (IBM)
   • Gerald Krause (SAP)
   • Mike Pizzo (Microsoft)
   • Christof Sprenger (Microsoft)
   • Heiko Theißen (SAP)

   Quorum is achieved (7 out of 9 voting members)

2. Approve agenda [8:05]

   Agenda is approved.

3. Approve minutes from previous meeting(s) [8:10]
   Minutes of 2026-01-28 Meeting #540

   Minutes are approved.

4. Issues [8:15]
   Issues - OData TC

   Access a property of the result of a non-composable function #400
   Mike moves to merge PR Define Composability and use of query options for actions/functions (Fixes OData-400) #2158 and close the issue as applied. Heiko seconds. Ralf advises to go ahead with the unexpected removal of a peer dependency in package-lock.json. No objections, motion passes.

   It is not clear if the entities in a collection returned by a function always have an entity-id #376
   TC reviews PR Define behavior for computed entities returned by actions and functions (Fixes OData-376) #2169 and corrects a typo. Mike moves to merge the PR and close the issue as applied. Hubert seconds. No objections, motion passes.

   OData V2 clarification requested: Is Property Name a SimpleIdentifier? #2168
   TC agrees that Name is always a simple identifier in OData V2. To correct the text, Christof would have to reach out to his V2 contacts. The issue is assigned to him.

   Clarification requested: Omit deprecated properties from a Record #2166
   Outcome of the discussion: Strictly speaking, deprecation of a property is an early warning of its upcoming incompatible removal, which is only allowed in a new major service version (with a different service URL). Omitting a deprecated property is therefore only allowed if it is nullable, with default value, an empty collection or can be computed. The last two alternatives, however, are not spelled out in the text. Omission of computed properties in records merits consideration as a separate question, for which Mike will create an issue.

   Heiko will clarify what this rule means for the annotations used at SAP, where certain complex-valued properties are deprecated. Depending on the outcome, this issue could be closed without action.

   Clarification requested: JSON $batch response status 200 OK even for malformed JSON requests? #2163
   In general (and not only for batch requests) services should be allowed to choose between

   • payload parsing followed by payload processing, in which case parsing errors lead to a 400 Bad Request error
   • chunk-by-chunk payload parsing, processing and response creation, in which case a 200 OK status must be sent before the first response chunk and later errors must be handled as in-stream errors [OData-Protocol, section 9.5].

   Heiko will create a pull request to clarify this.

   Distinguish expandability for a collection vs expandability for an item within a collection #399
   Mike will create a pull request for this.

   Interdependent DELETE requests in a change set #2103
   Mike will create a pull request for this.

5. Next meetings [9:50]

   • Wednesday, February 18, 2026, during 8-10 PST (17:00-19:00 CET)
   • Wednesday, February 25, 2026, during 8-10 PST (17:00-19:00 CET) - Hubert and Mike out
   • Wednesday, March 4, 2026, during 8-10 PST (17:00-19:00 CET)
   • Wednesday, March 11, 2026, during 8-10 PDT (16:00-18:00 CET)

6. AOB and wrap up [9:55]
   Meeting is adjourned.
   Find these minutes also at Minutes of 2026-02-11 Meeting #541 #2170

[HeikoTheissen]

Permalink