Agenda for OData TC meeting on 2018-08-30

Here [1] is a draft agenda for the OData TC (Technical Committee) meeting scheduled on Thursday August 30, 2018 during 8-10 am PDT (17:00-19:00 CEST). For additional information, such as dial-in details and chat room, refer to [2]. For TC timeline, see [3]. Feel free to suggest additions or modifications.

Thanks.

[1] Agenda

1. Roll call [8:00 am PT]

Self-registration link: https://www.oasis-open.org/apps/org/workgroup/odata/event.php?event_id=46271

2. Approve agenda [8:05 am PT]

3. Approve minutes from previous meeting(s) [8:10 am PT]

Minutes from August 23, 2018 TC meeting: https://www.oasis-open.org/committees/download.php/63827/odata-meeting-226_on-20180823-minutes.html

4. Review action items [Action item list: https://www.oasis-open.org/apps/org/workgroup/odata/members/action_items.php?sort_field=due_closed_date] [8:15am PT]

Upcoming

i. #0037 Concept for Google Protocol Buffers as a data format – Hubert Heijkers – 2018-09-27

In progress

i. #0036 Register the OData- headers and preferences with IANA – Mark Biamonte – 2018-07-26

5. Issues [8:20 am PT]

APPLIED

i. ODATA-1176 Capabilities: add new term SelectRestrictions

ii. ODATA-1167 Add way to specify which batch formats (if any) are supported by a service

Vocabularies: NEW or OPEN with concrete proposal

i. ODATA-1216 Terms for POST/PATCH/PUT with system query options to shape response

ii. ODATA-1064 Add ability to annotate collections to return only count and NextLink

Data Aggregation: NEW or OPEN

i. ODATA-1207 Clarify need for @odata.id in nested response structures

ii. ODATA-947 Transformation for computing ratios with aggregated values (deferred to F2F)

iii. ODATA-945 Correct examples 53 and 54 (deferred to F2F)

V4.01: NEW or OPEN

i. ODATA-1208 Specify the finest possible granularity for Duration

ii. ODATA-1203 Allow numeric indexes in Path constructs within annotations

iii. ODATA-1202 Deep update with nested delta items should allow Core.ContentID

iv. ODATA-1198 ETag handling deviations from RFC7232 are avoidable if we consider two kinds of ETag (ETag in response header and ETag in response payload)

v. ODATA-1197 Chapter 21 Error Response: replace misleading "code" values with FOO or BAR

vi. ODATA-1196 Clarify update of media streams

vii. ODATA-1195 11.2.6.6: value of $search is search _expression_, not boolean _expression_

viii. ODATA-1191 Make sure that all model elements are annotatable

ix. ODATA-1190 Add matchesPattern as a $filter function

x. ODATA-1189 Conformance: Nullable for collections

xi. ODATA-1188 Allow using instance annotations in $select and $expand

xii. ODATA-1187 No way to bind nav prop on recursively nested (contained or complex) type

xiii. ODATA-1183 Allow Singletons to be null

xiv. ODATA-1180 Cast between enumeration types and integer types

xv. ODATA-1177 Core: add term SchemaLocation

xvi. ODATA-1171 Consider using matrix parameters for filter segments

xvii. ODATA-1168 Clarify the use of ETags for Avoiding Update Conflicts

xviii. ODATA-1165 Describe $expand and $select via prose text and examples, remove ABNF snippets

xix. ODATA-1148 PATCH with nested nav props should not remove omitted resources

xx. ODATA-1143 Extend the Property metatype to allow a type that is an EntityType.

xxi. ODATA-1141 Upsert: clarify upsert along nullable single-valued navigation path

xxii. ODATA-1135 Document use of JSON $schema

xxiii. ODATA-1088 Clarify effect of applying an Annotation to an element

Vocabularies: NEW or OPEN that need more discussion

i. ODATA-1193 Automated vocabulary checks indicate some potential issues

ii. ODATA-1177 Allow referencing a (JSON) schema for Edm.Untyped properties

iii. ODATA-1107 Introduce instance annotation to specify which types an instance "implements"

iv. ODATA-1005 Make sure we have capabilities for all new 4.01 functionality

Vocabularies: deferred to F2F – examples, custom headers and query options, error codes

i. ODATA-1214 Annotate constructor actions

ii. ODATA-1200 ODATA-884 / Support sample values for types, parameters, request/response bodies

iii. ODATA-1194 Add term Core.Example to allow including annotation examples in term definitions

iv. ODATA-1140 ODATA-884 / Add details to HTTPResponseCode term

v. ODATA-1099 Add annotations to describe custom query options and custom headers

vi. ODATA-884 Add term ErrorCodes to describe possible codes in error messages (public comment c201510e00019)

6. Next meetings [9:50 am PT]

Thursday September 06, 2018 during 8-10 am PDT (17:00-19:00 CEST)
Thursday September 13, 2018 during 8-10 am PDT (17:00-19:00 CEST)
Thursday September 20, 2018 during 8-10 am PDT (17:00-19:00 CEST)

7. AOB and wrap up [9:55 am PT]

[2] References

Chat room: http://webconf.soaphub.org/conf/room/odatatc
Conference call & Screen sharing: https://lync.co.sap.com/meet/ralf.handl/Q4QB1098
Conference call details: https://www.oasis-open.org/apps/org/workgroup/odata/download.php/63673/latest/TC%20meeting%20dial-in%20details.htm

[3] Timeline

https://www.oasis-open.org/committees/download.php/62637/TC%20Timeline-2018-03-02.docx

odata message