OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

odata message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: Agenda for OData TC meeting on 2023-07-12


Here [1] is a draft agenda for the OData TC (Technical Committee) meeting scheduled on Wednesday July 12, 2023 during 8-10 am PDT (17:00-19:00 CEST).

 

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=53531

  2. Approve agenda [8:05]

  3. Approve minutes from previous meeting(s) [8:10 am]
    1. Minutes from July 05, 2023 TC meeting: https://www.oasis-open.org/committees/download.php/71173/Minutes%20of%202023-07-05%20Meeting%20%23439.docx

  4. Whatâs next: V4.01 Errata 01 or V4.02 [8:15]
    1. Situation

                                          i.    We have ~100 issues for Errata 01, ~60 already resolved, ~40 new/open

                                         ii.    We have ~60 issues for V4.02, 6 already resolved

                                        iii.    V4.01 uses Word as the authoritative source, and Errata have to continue with that

                                        iv.    V4.02 can use Markdown as the authoritative source, and a simplified multi-part document structure

    1. Options

                                          i.    Publish V4.01 Errata 01 with the old editing tools and document structure, then switch to Markdown and the simplified structure with V4.02

                                         ii.    Publish V4.02 CSD01 with the new editing tools and document structure, incorporating (a subset of) the already resolved issues, add new/open issues in CSD02

  1. RAPID Profile for OData [8:30]
    1. Pull Requests
    2. Issues

  2. Issues [9:00]

a.    V4.01 Errata 01: NEW or OPEN with assigned champion

                                          i. ODATA-1239 Define a mechanism to distinguish between inserted and updated entities in a Delta message

                                         ii. ODATA-1262 Explicitly state structural restrictions of type Edm.Untyped

                                        iii. ODATA-1360 Clarify that clients have to do content-ID replacing to interpret Location headers in batch results

                                        iv. ODATA-1370 CSDL Section 12.9 "Parameter" mixing with "overload" causes ambiguity, particularly with regard to parameter ordering

                                         v. ODATA-1379 Consider adding railroad diagrams for the URL syntax

                                        vi. ODATA-1397 Examples 86 and 87 apply an entity type as term

                                       vii. ODATA-1398 Improve text and examples for JSON and multipart batch

                                      viii. ODATA-1407 No way to $select instance annotations on primitive types

                                        ix. ODATA-1424 OData 4.01 JSON "Delta Responses" doesn't describe use of "@id" (or "@odata.id") for Added/Changed Entity

                                         x. ODATA-1457 Potential confusion wrt Content-Type header for media entities

                                        xi. ODATA-1475 How to search for double quotes

                                       xii. ODATA-1496 clarify the relationship of the various path _expression_ types

                                      xiii. ODATA-1503 Instance annotations of absent complex properties

                                      xiv. ODATA-1508 Missing annotation namespace in example 8

                                       xv. ODATA-1517 [OData-CSDL, example 64] annotating a navigation property or its addressed resource?

                                      xvi. ODATA-1520 Central definition for type-cast and term-cast segments

                                     xvii. ODATA-1526 Support collapsing individual sections (chapters) in the HTML versions of the specification

                                    xviii. ODATA-1527 Allow functions/actions to return (and take) a delta payload

                                      xix. ODATA-1528 Update JSON Delta Response payload examples

                                       xx. ODATA-1530 Specify when and how stream valued properties are included

                                      xxi. ODATA-1534 OData 4.01 JSON batch format doesn't support streaming use cases well

                                     xxii. ODATA-1547 Recursive complex types must be nullable

                                    xxiii. ODATA-1548 Encourage clients to specify the correct value for non-key, non-computed read-only values (or omit)

                                   xxiv. ODATA-1553 Clarify the algorithm for evaluating $compute

                                    xxv. ODATA-1555 Strengthen definitions for $orderby, $top and $skip

                                   xxvi. ODATA-1558 Define semantics for navigation properties of type Edm.EntityType

                                  xxvii. ODATA-1560 Clarify usage of URL templates with callback preference

                                 xxviii. ODATA-1563 URL 4.11, paragraph 2: clarify restriction "that is part of a Boolean _expression_"

                                   xxix. ODATA-1564 Protocol 11.7.7.1 misleading text on request formats

                                    xxx. ODATA-1568 Allow handling of in-stream errors on protocol level

                                   xxxi. ODATA-1573 clarify behavior for omitted values in PATCH and PUT

                                  xxxii. ODATA-1576 Consistently use "instances of structured types" instead of "structured instances"

                                 xxxiii. ODATA-1577 Consistently use "entity id" instead of "entity-id"

                                 xxxiv. ODATA-1578 Consistently use "annotated with the term" instead of "annotated with term"

                                  xxxv. ODATA-1582 Mention use of ETag with bound function: only process if binding entity matches ETag

                                 xxxvi. ODATA-1584 Inconsistency regarding $select=@Namespace.Term

b.    V4.01 Errata 01: NEW or OPEN that need a champion

                                          i. ODATA-1583 Clarify representation of context URLs in JSON payloads

c.     V4.02: NEW or OPEN with concrete proposal

                                          i. ODATA-1364 Define ExpandOptions for nav property in $select

                                         ii. ODATA-1388 Make key aliases optional, clarify multiple to-one navigation hops

                                        iii. ODATA-1389 New control information @fileName / @odata.fileName

                                        iv. ODATA-1405 /$query shall allow Content-Type: application/x-www-form-urlencoded and Content-Type: application/json

                                         v. ODATA-1435 Conditionally add an element to a collection

                                        vi. ODATA-1438 New preference return=keys

                                       vii. ODATA-1441 New query option $expect combining $expand and $select

                                      viii. ODATA-1483 Expand all containment navigation properties recursively

                                        ix. ODATA-1506 Allow index segments in path expressions

                                         x. ODATA-1540 Require decoding of plus as space in query part of URL

                                        xi. ODATA-1544 Section 4.17: support new HTTP QUERY method, deprecate /$query path suffix

                                       xii. ODATA-1545 Allow services to validate read-only properties in update payloads

                                      xiii. ODATA-1571 Allow empty entity containers

                                      xiv. ODATA-1575 Remove restriction on Partner navigation

d.    V4.02: NEW or OPEN that need more discussion

                                          i. currently 37 issues

e.    Vocabularies: NEW or OPEN with concrete proposal

                                          i.  ODATA-1336 Querying âJSON propertiesâ

1.     https://github.com/oasis-tcs/odata-vocabularies/pull/157

                                         ii. ODATA-1358 Detach textual descriptions from operation restriction terms in Capability vocabulary

                                        iii. ODATA-1394 Add full-fledged support for ISO 8601-1 duration

                                        iv. ODATA-1412 Capabilities vocabulary: Add EntityContainer as annotation target

                                         v. ODATA-1453 Capabilities.SearchRestrictions/UnsupportedExpressions: description of default value "none" is misleading

                                        vi. ODATA-1467 Keep a CHANGELOG.md, use Semantic Versioning for each vocabulary

                                       vii. ODATA-1550 Clarify whether Validation.AllowedValues can be applied to collection-valued properties

  1. Next meetings [9:50]

a.    Wednesday July 19, 2023 during 8-10 PDT (17:00-19:00 CEST) â Heiko on leave

b.    Wednesday July 26, 2023 during 8-10 PDT (17:00-19:00 CEST)

c.     Wednesday August 02, 2023 during 8-10 PDT (17:00-19:00 CEST)

d.    Wednesday August 09, 2023 during 8-10 PDT (17:00-19:00 CEST)

  1. AOB and wrap up [9:55]

 

[2] Timeline

     1.  https://www.oasis-open.org/committees/download.php/71007/TC-Timeline-2023-05-10.docx

 

 

________________________________________________________________________________

Join Microsoft Teams Meeting

Conference ID: 629 315 222#

Local numbers | Learn more about Teams | Meeting options

________________________________________________________________________________

 

 

 



[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]