Minutes of 2025-07-30 Meeting #521

[HeikoTheissen]

1. Roll call [8:00]
   Meeting link: OASIS Open Data Protocol (OData) TC
   Attendees:

   • George Ericson (Dell) is on leave until end of July
   • 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 achieved (6 out of 8 voting members)

2. Approve agenda [8:05]

   Christof wants to discuss Formally define OData Metamodel  #288 during topic 4. Agenda is approved.

3. Approve minutes from previous meeting(s) [8:10]
   Minutes of 2025-07-23 Meeting #520.pdf

   Minutes are approved.

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

   Formally define OData Metamodel  #288
   Christof presents a Markdown document that describes the EDM metamodel and was generated from a JSON file. Feedback from TC:

   • References are special cases of paths.
   • The attribute EntitySet of edm:ActionImport is not a relative reference but an absolute reference. It is just a notational convenience that the entity container can be omitted from the path if it is the parent of the action import.
   • There should be separate attributes Type and Collection.
   • The metamodel does not contain cardinalities and uniqueness constraints. It does not aim to specify how resource paths in URLs are parsed.
   • The metamodel does not contain the model elements needed for dynamic expressions (such as in "[email protected]": {"$Path": "Currency"}).

   Christof will prepare a pull request that inserts this material into https://github.com/oasis-tcs/odata-csdl-schemas.

   Atomicity requirements and partial execution #2101
   TC reviews the PR Define atomicity #2107 and suggests changes. Most importantly, it agrees that application of the continue-on-error preference implies no atomicity for the changes.

   The response scheme with next-links for asynchronous mass update requests that is proposed in Atomicity requirements and partial execution #2101 (comment) is allowed.

   Deep create - all or nothing #2095
   The text tries to distinguish between cases where the user expects specific entities to be created versus have the equivalent effect of the aggregate of the request. There are more cases where the former is implied, for example client-specified keys. Heiko will adapt PR Explain intent vs. successful data modification #2099 accordingly.

5. Next meetings [9:30]

   • Wednesday, August 6, 2025, during 8-10 PST (17:00-19:00 CET): Ralf, Gerald and Hubert out
   • Wednesday, August 13, 2025, during 8-10 PST (17:00-19:00 CET): Gerald out
   • Wednesday, August 20, 2025, during 8-10 PST (17:00-19:00 CET): Gerald and Hubert out
   • Wednesday, August 27, 2025, during 8-10 PST (17:00-19:00 CET): Hubert out

   Consider on August 13 whether to take the following 2 weeks off.

6. AOB and wrap up [9:35]

   Meeting is adjourned.
   Find these minutes also at Minutes of 2025-07-30 Meeting #521 #2108.

[HeikoTheissen]

Permalink