Re: Agenda for OData TC meeting on 2024-01-24

["Handl, Ralf" <ralf.handl@sap.com>]

Adding

ââââââ5.c ODATA-1631 Validation.Constraint may also be applied to a navigation property

---

From: Handl, Ralf <ralf.handl@sap.com>
Sent: Monday, January 22, 2024 09:16
To: odata@lists.oasis-open.org <odata@lists.oasis-open.org>
Cc: Krause, Gerald <gerald.krause@sap.com>; Theissen, Heiko <heiko.theissen@sap.com>
Subject: Agenda for OData TC meeting on 2024-01-24

 

Here [1] is a draft agenda for the OData TC (Technical Committee) meeting scheduled on Wednesday January 24, 2024 during 8-10 am PST (17:00-19:00 CET).

 

For TC timeline, see [2].

 

Feel free to suggest additions or modifications.

Thanks.

 

 

[1] Agenda

1. Roll call [8:00]

1. Self-registration link: https://www.oasis-open.org/apps/org/workgroup/odata/event.php?event_id=54350
2. Join Microsoft Teams Meeting

   Conference ID: 629 315 222#

   Local numbers | Learn more about Teams | Meeting options

   
   
2. Approve agenda [8:05]
   
   
3. Approve minutes from previous meeting(s) [8:10]
   
1. Minutes from January 17, 2024 TC meeting: https://www.oasis-open.org/committees/download.php/71628/Minutes%20of%202024-01-17%20Meeting%20%23458.docx
   
   
4. OData Metamodel [8:15]
   
1. George's approach with UML stereotypes [8:15]
2. Christof's approach [8:45]
   
   
5. Issues [9:15]
   
1. V4.02 and V4.01 Errata 01: APPLIED
   
1. ODATA-1323 Clarify representation of GEO literals and streams in annotations (XML, JSON)
2. ODATA-1547 Recursive complex types must be nullable
   
   
2. V4.01 Errata: NEW or OPEN
   
1. ODATA-1370 CSDL Section 12.9 âParameterâ mixing with âoverloadâ causes ambiguity, particularly with regard to parameter ordering
2. ODATA-1424 OData 4.01 JSON âDelta Responsesâ doesnât describe use of â@idâ (or â@odata.idâ) for Added/Changed Entity
3. ODATA-1496 clarify the relationship of the various path _expression_ types
4. ODATA-1558 Define semantics for navigation properties of type Edm.EntityType
5. ODATA-1559 Clarify definition of transient.
6. ODATA-1560 Clarify usage of URL templates with callback preference
7. ODATA-1573 clarify behavior for omitted values in PATCH and PUT
8. ODATA-1603 It is not clear if the entities in a collection returned by a function always have an entity-id
9. ODATA-1610 Clarify use of âwaitâ preference without ârespond-asyncâ preference
10. ODATA-1628 CSDL: correct examples for odata.concat to use two parameters
11. ODATA-1629 Avoid homonym âtarget pathâ
    
    
3. V4.02: NEW or OPEN with champion and proposal
   
1. ODATA-730 Lack of ordering constraints on delta responses may require clients to buffer (or persist) entire response to process it correctly
2. ODATA-879 Support Arrays of Arrays
3. ODATA-919 Specify the result type for each operation based on operator types
4. ODATA-923 Support subsetting returned metadata
5. ODATA-1059 Improve specification and use of NavigationProperties, EntitySets, and Singletons
6. ODATA-1060 Improve specification of element response requirements
7. ODATA-1071 Nullable Collection Navigation Property
8. ODATA-1113 Allow alternate / native search syntax
9. ODATA-1239 Define a mechanism to distinguish between inserted and updated entities in a Delta message
10. ODATA-1253 Abstract type definition Core.Number as a super-type of all numeric types
11. ODATA-1336 Querying âJSON propertiesâ
12. ODATA-1340 PATCH: new preference return=delta to get back a delta response
13. ODATA-1405 /$query shall allow Content-Type: application/x-www-form-urlencoded
14. ODATA-1407 No way to $select instance annotations on primitive types
15. ODATA-1435 Conditionally add an element to a collection
16. ODATA-1457 Potential confusion wrt Content-Type header for media entities
17. ODATA-1506 Allow index segments in path expressions
18. ODATA-1534 OData 4.01 JSON batch format doesnât support streaming use cases well
19. ODATA-1540 Require decoding of plus as space in query part of URL
20. ODATA-1544 Section 4.17: support new HTTP QUERY method, deprecate /$query path suffix
21. ODATA-1545 Allow services to validate read-only properties in update payloads
22. ODATA-1548 Encourage clients to specify the correct value for non-key, non-computed read-only values (or omit)
23. ODATA-1569 Allow CSDL JSON also for OData versions 2.0 and 3.0 - close without action
24. ODATA-1575 Remove restriction on Partner navigation
25. ODATA-1583 Clarify representation of context URLs in JSON payloads
26. ODATA-1585 Should be able to change type when PATCHing an entity
27. ODATA-1589 /$query shall allow Content-Type: application/json
28. ODATA-1590 Clarify where alternate keys can be used
29. ODATA-1594 Add support for fuzzy search function within $filter, etc.
30. ODATA-1597 Allow to create annotations in CSDL with a less verbose format to increase adoption
31. ODATA-1601 concat: allow more than two arguments - close without action
32. ODATA-1616 Clarify rules around results returned from Create/Update
33. ODATA-1618 Clarify matchespattern and regular _expression_ flags
34. ODATA-1621 Clarify annotations on unavailable properties
35. ODATA-1623 Support alternate keys in delta patch
36. ODATA-1624 Make conformance clauses more future-proof
37. ODATA-1626 Should support annotations to bound actions/functions via path
38. ODATA-1630 Resharpen definitions of PropertyPath and NavigationPropertyPath
    
    
6. Next meetings [9:50]
   
1. Wednesday January 31, 2024 during 8-10 PST (17:00-19:00 CET)
   
2. Wednesday February 07, 2024 during 8-10 PST (17:00-19:00 CET)
3. Wednesday February 14, 2024 during 8-10 PST (17:00-19:00 CET)
4. Wednesday February 21, 2024 during 8-10 PST (17:00-19:00 CET)
   
   
7. AOB and wrap up [9:55]

[2] Timeline

1. https://www.oasis-open.org/committees/download.php/71620/TC-Timeline-2024-01-10.docx