OASIS Open Data Protocol (OData) TC

 View Only

  • 1.  Agenda for OData TC meeting on 2024-03-20

    Posted 03-14-2024 06:56

    Here [1] is a draft agenda for the OData TC (Technical Committee) meeting scheduled on Wednesday March 20, 2024, during 8-10 am PDT (16:00-18:00 CET) – one hour earlier in Europe.

     

    For TC timeline, see [2].

     

    Feel free to suggest additions or modifications.

    Thanks.

     

     

    [1] Agenda

    1. Roll call [8:00]
      1. Meeting link (self-registration not yet possible): vanished
      2. Join Microsoft Teams Meeting

    Conference ID: 629 315 222#

    Local numbers | Learn more about Teams | 19_meeting_YWNiMDg5MjItYmY4Mi00ZjAxLTlhOWUtZWVjZjM5NjMzMTM3@thread.v2&messageId=0&language=en-US" title="https://teams.microsoft.com/meetingOptions/?organizerId=b711c831-085c-47cd-9f39-6b716eac5611&tenantId=42f7676c-f455-423c-82f6-dc2d99791af7&threadId=19_meeting_YWNiMDg5MjItYmY4Mi00ZjAxLTlhOWUtZWVjZjM5NjMzMTM3@thread.v2&messageId=0&language=en-US">Meeting options

    1. Approve agenda [8:05]
    2. Approve minutes from previous meeting(s) [8:10]
      1. Minutes from March 06, 2024, TC meeting: https://groups.oasis-open.org/higherlogic/ws/public/download/71731/Minutes%20of%202024-03-06%20Meeting%20%23464.docx
      2. Minutes from March 13, 2024, TC meeting: https://groups.oasis-open.org/higherlogic/ws/public/download/71743/Minutes%20of%202024-03-13%20Meeting%20%23465.docx
    1. Review action items [8:15]
      1. Upcoming
        1. #0039 Concept for Compact JSON data format – Hubert Heijkers – 2024-05-03
        2. #0037 Concept for binary data format – Hubert Heijkers – 2024-05-03
    1. RAPID Profile for OData [8:15]
      1. Pull Requests
      2. Issues
    1. Issues [8:20]
      1. V4.02 and V4.01 Errata 01: with pull request
        1. ODATA-1239 Define a mechanism to distinguish between inserted and updated entities in a Delta message
        2. ODATA-1336 Querying "JSON properties"
        3. ODATA-1370 CSDL Section 12.9 "Parameter" mixing with "overload" causes ambiguity, particularly with regard to parameter ordering
        4. ODATA-1405 /$query shall allow Content-Type: application/x-www-form-urlencoded
        5. ODATA-1435 Conditionally add an element to a collection
        6. ODATA-1506 Allow index segments in path expressions
        7. ODATA-1583 Clarify representation of context URLs in JSON payloads
        8. ODATA-1610 Clarify use of 'wait' preference without 'respond-async' preference
        9. ODATA-1624 Make conformance clauses more future-proof
        10. ODATA-1626 Should support annotations to bound actions/functions via path
        11. ODATA-1630 Resharpen definitions of PropertyPath and NavigationPropertyPath
        12. ODATA-1642 Clarify key values in upsert along navigation properties

     

      1. V4.02 and V4.01 Errata 01: RESOLVED without pull request
        1.  12 issues

     

      1. V4.02 and V4.01 Errata: NEW or OPEN without pull request
        1. ODATA-579 Should we support dynamic functions/actions?
        2. ODATA-601 Investigate enhancements to interoperability and feature set of OData JSON through JSON-LD
        3. ODATA-730 Lack of ordering constraints on delta responses may require clients to buffer (or persist) entire response to process it correctly
        4. ODATA-854 Consider use of OPTIONS for discovering formats, other capabilities and features
        5. ODATA-879 Support Arrays of Arrays
        6. ODATA-919 Specify the result type for each operation based on operator types
        7. ODATA-923 Support subsetting returned metadata
        8. ODATA-1052 Consider the "fragility" of server-driven paging
        9. ODATA-1059 Improve specification and use of NavigationProperties, EntitySets, and Singletons
        10. ODATA-1060 Improve specification of element response requirements
        11. ODATA-1062 Formally define OData Metamodel
        12. ODATA-1070 Clarify text related to Canonical URL
        13. ODATA-1071 Nullable Collection Navigation Property
        14. ODATA-1107 Introduce instance annotation to specify which types an instance "implements"
        15. ODATA-1113 Allow alternate / native search syntax
        16. ODATA-1235 ActionImport and FunctionImport on EntityType
        17. ODATA-1246 Allow BaseType of EntityType to be a ComplexType
        18. ODATA-1261 Allow $pagesize system query option
        19. ODATA-1262 Explicitly state structural restrictions of type Edm.Untyped
        20. ODATA-1308 Ability to reference newly discovered OData services
        21. ODATA-1317 ContextUrl does not represent navigation properties for which the entity references ($ref) are included
        22. ODATA-1333 Add Terms, Abbreviated Terms, and Symbols sections to specifications
        23. ODATA-1340 PATCH: new preference return=delta to get back a delta response
        24. ODATA-1350 OData V2 required continue-on-error style batch responses, V4 makes it optional for servers (due to use of Prefer)
        25. ODATA-1379 Consider adding railroad diagrams for the URL syntax
        26. ODATA-1386 Introduce primitive types for color values
        27. ODATA-1407 No way to $select instance annotations on primitive types
        28. ODATA-1424 OData 4.01 JSON "Delta Responses" doesn't describe use of "@id" (or "@odata.id") for Added/Changed Entity
        29. ODATA-1438 New preference return=keys
        30. ODATA-1441 New query option $expect combining $expand and $select
        31. ODATA-1457 Potential confusion wrt Content-Type header for media entities
        32. ODATA-1479 Current instance/collection is only defined adhoc
        33. ODATA-1504 Dry-run of data modification requests
        34. ODATA-1505 Expressions in action payloads
        35. ODATA-1514 Generalize the use of $each
        36. ODATA-1527 Allow functions/actions to return (and take) a delta payload
        37. ODATA-1529 Provide support for selecting the id of an entity
        38. ODATA-1534 OData 4.01 JSON batch format doesn't support streaming use cases well
        39. ODATA-1535 Should updates of related resources be supported in Create?
        40. ODATA-1544 Section 4.17: support new HTTP QUERY method, deprecate /$query path suffix
        41. ODATA-1545 Allow services to validate read-only properties in update payloads
        42. ODATA-1548 Encourage clients to specify the correct value for non-key, non-computed read-only values (or omit)
        43. ODATA-1558 Define semantics for navigation properties of type Edm.EntityType
        44. ODATA-1560 Clarify usage of URL templates with callback preference
        45. ODATA-1573 clarify behavior for omitted values in PATCH and PUT
        46. ODATA-1574 Expand function results
        47. ODATA-1575 Remove restriction on Partner navigation
        48. ODATA-1579 Allow references to Core.ContentIDs in batch request URLs
        49. ODATA-1585 Should be able to change type when PATCHing an entity
        50. ODATA-1586 Clarify create/replace for server-defined dynamic properties
        51. ODATA-1589 /$query shall allow Content-Type: application/json
        52. ODATA-1590 Clarify where alternate keys can be used
        53. ODATA-1594 Add support for fuzzy search function within $filter, etc.
        54. ODATA-1597 Allow to create annotations in CSDL with a less verbose format to increase adoption
        55. ODATA-1603 It is not clear if the entities in a collection returned by a function always have an entity-id
        56. ODATA-1606 Separation of concerns: ABNF for URL components instead of whole URLs
        57. ODATA-1608 Safety, Security and Privacy Considerations: fill out or remove appendix
        58. ODATA-1614 Add NonSelectableProperties to SelectSupportType
        59. ODATA-1616 Clarify rules around results returned from Create/Update
        60. ODATA-1621 Clarify annotations on unavailable properties
        61. ODATA-1623 Support alternate keys in delta patch
        62. ODATA-1625 Cannot specify null as DefaultValue in CSDL XML
        63. ODATA-1638 Clarify creation of a singleton media entity
        64. ODATA-1640 Access a property of the result of a non-composable function
        65. ODATA-1641 More rigorous definition of $ references
        66. ODATA-1645 Find reliable references for Geo WKT and SRID
    1. Next meetings [9:50]
      1. Wednesday March 27, 2024, during 8-10 PDT (16:00-18:00 CET) – one hour earlier in Europe
      2. Wednesday April 03, 2024, during 8-10 PST (17:00-19:00 CET)
      3. Wednesday April 10, 2024, during 8-10 PST (17:00-19:00 CET)
      4. Wednesday April 17, 2024, during 8-10 PST (17:00-19:00 CET)
    2. AOB and wrap up [9:55]

     

    [2] Timeline

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

     

     

     



  • 2.  RE: Agenda for OData TC meeting on 2024-03-20

    Posted 03-18-2024 05:01

    Additional agenda item

    5.5 Move from OASIS Jira to Github issues

    a. Login to Jira is not possible at the moment

    b. Many TCs already moved to Github with very positive feedback

    c. Kelly Cullinane from OASIS highly recommends to switch

    d. We could use either

     

     




    Original Message


  • 3.  RE: Agenda for OData TC meeting on 2024-03-20

    Posted 03-19-2024 12:10

    Demo repo for moving Jira issues to Github: https://github.com/ralfhandl/issue-test/issues - contains a subset of the OData-TC Jira issues

     




    Original Message


  • 4.  RE: Agenda for OData TC meeting on 2024-03-20

    Posted 03-20-2024 05:00

    Additional Agenda Item

     

    5.8 Christof on OData Metamodel, ODATA-1062

     

     




    Original Message


  • 5.  RE: Agenda for OData TC meeting on 2024-03-20

    Posted 03-20-2024 05:13

    Additional agenda items

    5.5 Move from OASIS Jira to Github issues

    a. Login to Jira is not possible at the moment

    b. Many TCs already moved to Github with very positive feedback

    c. Kelly Cullinane from OASIS highly recommends to switch

    d. We could use either 

    ·         the dedicated https://github.com/oasis-tcs/odata-specs repo where we develop the specifications, or 

    ·         the generic https://github.com/oasis-tcs/odata repo that we currently don't use much

    e. Demo repo for moving Jira issues to Github: github.com/ralfhandl/issue-test/issues - contains a subset of the OData-TC Jira issues   

     

    5.8 Christof on OData Metamodel, ODATA-1062

     

     




    Original Message


Related Content