Minutes of 2025-12-03 Meeting #535

[HeikoTheissen]

1. Roll call [8:00]
   Meeting link: OASIS Open Data Protocol (OData) TC
   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 (8 out of 9 voting members)

2. Approve agenda [8:05]

   Agenda is approved.

3. Approve minutes from previous meeting(s) [8:10]
   Minutes of 2025-11-19 Meeting #534.pdf

   Minutes are approved.

4. Chair Hand-off

   • OASIS Recurring Meeting
   • Teams invites
   • Sending out Agenda

   Mike will continue to attend the meetings as a Microsoft business guest. Heiko sets up a new recurring Teams meeting, Ralf will update the dial-in information in the OASIS workzone. Heiko will take over sending out the agenda.

5. Aggregation Extension Committee Spec 4 Published
   https://docs.oasis-open.org/odata/odata-data-aggregation-ext/v4.0/cs04/
   Next steps for Approval of an OASIS Standard:

   1. 3 Statements of Use must be approved by the TC
      • Statement of Use from SAP (Heiko)
      • Statement of Use from Microsoft
      • Identify a 3rd statement of use
   2. TC requests a Special Majority Vote to submit as a Candidate OASIS Standard
   3. Candidate Specification undergoes a 60 day public review
   4. After 60 days, Chair notifies the TC Administrator of the results
      • If no comments received, TC starts call for consent for OASIS Standard w/in 7 days of notification
      • If comments are received but no action is taken, TC can request a Special Majority Vote to continue
      • Non-material changes in response to comments may be applied, clearly documented, and approved through a subsequent Special Majority Vote of the TC to continue
      • Material changes require a new CSD/CS.
   5. TC Admin calls for consent for OASIS Standard
      • Min 14 day consent period
      • Each OASIS Organizational Member has the opportunity to object through the voting tool
        • TC has 30 days to respond to valid objections, including making changes
        • Any material changes require a second call for consent

6. Issues [8:15]
   OData TC Github Issues

   Bump several packages, upgrade pandoc #2147
   Will be merged after the meeting.

   OData V2 required continue-on-error style batch responses, V4 makes it optional for servers (due to use of Prefer) #310
   Heiko moves to merge PR Disambiguate ContinueOnErrorSupported odata-vocabularies#306 and close the issue as applied. Stefan seconds. No objections, motion passes.

   OData V2: JSON verbose response format #2145
   Will be followed-up offline (pull request in https://github.com/OData/odataorg.github.io).

   Deep create - all or nothing #2095
   TC agrees to phrase the client expectation as follows: Every entity in the request payload MUST have a corresponding entity in the response. Heiko will update PR Explain intent vs. successful data modification #2099 accordingly and reconsider the usage of the term "intent".

7. Next meetings [9:20]

   • Wednesday, December 10, 2025, during 8-10 PST (17:00-19:00 CET) - Hubert out
   • Wednesday, December 17, 2025, during 8-10 PST (17:00-19:00 CET) -- No Meeting
   • Wednesday, December 24, 2025, during 8-10 PST (17:00-19:00 CET) -- No Meeting (Christmas)
   • Wednesday, December 31, 2025, during 8-10 PST (17:00-19:00 CET) -- No Meeting (New Year)
   • Wednesday, January 7, 2026, during 8-10 PST (17:00-19:00 CET)
   • Wednesday, January 14, 2026, during 8-10 PST (17:00-19:00 CET)

8. AOB and wrap up [9:25]
   Meeting is adjourned.
   Find these minutes also at Minutes of 2025-12-03 Meeting #535 #2148

[HeikoTheissen]

Permalink