RE: Agenda for OData TC meeting on 2018-08-09 - chat transcript

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

[16:58] Room information was updated by: Ralf Handl (SAP SE)

Note: new dial-in info via Skype for Business: 

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 

Here [1] is a draft agenda for the OData TC (Technical Committee) meeting scheduled on Thursday August 09, 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]

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

2.Approve agenda [8:05 am PT]

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

a.Minutes from August 02, 2018 TC meeting: https://www.oasis-open.org/committees/download.php/63669/odata-meeting-223_on-20180802-minutes-informal.html 

i.No quorum, nothing to approve

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

a.Due

i.#0038 Prepare proposal for REST Profile / OData Essentials  Mike Pizzo  2018-08-08

b.Upcoming

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

c.Pending

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

5.Issues [8:20 am PT]

a.Data Aggregation: NEW or OPEN

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

ii.ODATA-1206 Explicitly note support for collection-valued navigation/complex properties in property paths in aggregate/groupby

iii.ODATA-1205 Examples 53, 54, and 59 are not compliant with Data Aggregation ABNF

iv.ODATA-947 Transformation for computing ratios with aggregated values

v.ODATA-945 Correct examples 53 and 54

b.Vocabularies: Annotation Examples and Example Values for types, parameters, request/response bodies 

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

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

c.V4.01: NEW or OPEN 

i.ODATA-1213 Address use of 201 Created for Create Link Requests

ii.ODATA-1212 Validation term for allowed terms in Annotation Paths

iii.ODATA-1211 ODATA-681 4.2 and 5.1: Explicitly state that an alias MUST NOT be identical to any other alias or namespace in the same document.

iv.ODATA-1210 CSDL ReturnType element needs to specify rules for Nullable and Collection with entity types

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

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

vii.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)

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

ix.ODATA-1196 Clarify update of media streams

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

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

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

xiii.ODATA-1189 Conformance: Nullable for collections

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

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

xvi.ODATA-1183 Allow Singletons to be null

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

xviii.ODATA-1177 Core: add term SchemaLocation

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

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

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

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

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

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

xxv.ODATA-1135 Document use of JSON $schema

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

d.Vocabularies: NEW or OPEN with concrete proposal

i.ODATA-1212 Validation term for allowed terms in Annotation Paths

ii.ODATA-1209 Term for original OData version of (auto-)converted $metadata

iii.ODATA-1204 Vocabularies Document references OData Version 4.01. Part 3: Common Schema Definition Language (CSDL)

iv.ODATA-1176 Capabilities: add new term SelectRestrictions

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

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

e.Vocabularies: NEW or OPEN that need more discussion

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

ii.ODATA-1199 ODATA-884 / Add property SystemQueryOptions to call out supported system query options per request method

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

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

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

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

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

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

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

6.Next meetings [9:50 am PT]

a.Thursday Mm 16, 2018 during 8-10 am PDT (17:00-19:00 CEST)

b.Thursday Mm 23, 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

[17:02] Ralf Handl (SAP SE): Please note the new dial-in data

[17:02] Ralf Handl (SAP SE): https://www.oasis-open.org/apps/org/workgroup/odata/download.php/63673/latest/TC%20meeting%20dial-in%20details.htm

[17:02] Ted Jones (Red Hat): Hi Ralf, I have a conflict the first hour. I will participate then.

[17:03] Ralf Handl (SAP SE): Ok, talk to you later!

[17:08] Ralf Handl (SAP SE): Voting Members: 6 of 11 (54%) (used for quorum calculation)

[17:08] Ralf Handl (SAP SE): Quorum achieved: yes

[17:13] Ralf Handl (SAP SE): Join by phone

+1 8552234162 "Canada" (SAP Dial-In)                          

+86 4008106069 "China All Cities" (SAP Dial-In)                           

+49 8005891883 "Germany" (SAP Dial-In)                     

+49 6922227996 "Germany Frankfurt" (SAP Dial-In)                   

+91 8071279160 "India Bangalore" (SAP Dial-In)                         

0008004404099 "India" (SAP Dial-In)                             

+65 67041630 "Singapore All Cities" (SAP Dial-In)                       

+44 3306068668 "United Kingdom All Cities" (SAP Dial-In)                        

+1 8664100244 "United States" (SAP Dial-In)                               

+1 2106069508 "United States All Cities" (SAP Dial-In)

[17:13] Ralf Handl (SAP SE): Find a local number: https://www.intercalleurope.com/sap/ecclyncnumlookup/?confCode=4491205697&eb=SAP

[17:15] Ralf Handl (SAP SE): 2.Approve agenda [8:05 am PT]

[17:18] Ralf Handl (SAP SE): No changes, agenda is approved

[17:18] Ralf Handl (SAP SE): 3.Approve minutes from previous meeting(s) [8:10 am PT]

a.Minutes from August 02, 2018 TC meeting: https://www.oasis-open.org/committees/download.php/63669/odata-meeting-223_on-20180802-minutes-informal.html 

i.No quorum, nothing to approve

[17:19] Ralf Handl (SAP SE): b.Minutes from July 26, 2018 TC meeting: https://www.oasis-open.org/committees/download.php/63491/odata-meeting-222_on-20180726-minutes.html

[17:20] Ralf Handl (SAP SE): Minutes are approved

[17:20] Ralf Handl (SAP SE): a.Minutes from July 26, 2018 TC meeting: https://www.oasis-open.org/committees/download.php/63491/odata-meeting-222_on-20180726-minutes.html

[17:21] Ralf Handl (SAP SE): 4.Review action items [Action item list: https://www.oasis-open.org/apps/org/workgroup/odata/members/action_items.php] [8:15am PT]

a.Due

i.#0038 Prepare proposal for REST Profile / OData Essentials  Mike Pizzo  2018-08-08

[17:21] Ralf Handl (SAP SE): https://www.oasis-open.org/apps/org/workgroup/odata/download.php/63678/REST-EZ.docx

[18:04] Michael Pizzo: Issue: To be popular with hobby developers and generate buzz we need libraries on popular platforms.

[18:05] Michael Pizzo: Issue: Is everything in REST-EZ required?  i.e., expand? what filter functionality is required?  Should we define a simplified subset of the _expression_ language?

[18:06] Michael Pizzo: Should identify "levels" according to use cases

[18:07] Michael Pizzo: Rather than "levels" could even consider (possibly overlapping) scenario-based "feature sets"

[18:10] Michael Pizzo: Relationship of REST-EZ to OpenAPI:

REST-EZ and OpenAPI

OpenAPI is an extremely popular specification for documenting a REST API. Because REST-EZ APIs are REST APIs, it is natural and encouraged for REST-EZ services to support OpenAPI.

As the REST-EZ service description defines a superset of what a service might want to document through OpenAPI, a suggested translation is defined for translating a REST-EZ service description to OpenAPI.

[18:35] Michael Pizzo: Here is a link to the Microsoft library for converting OData CSDL->OpenAPI, which is currently in beta: https://www.nuget.org/packages/Microsoft.OpenApi.OData/1.0.0-beta4

[18:37] Michael Pizzo: We are working on updating this library with additional patterns and plan to open source the code.

[18:38] Ralf Handl (SAP SE): 5.Issues [8:20 am PT]

a.Data Aggregation: NEW or OPEN

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

[18:38] Ralf Handl (SAP SE): https://issues.oasis-open.org/browse/ODATA-1207

[18:41] Ralf Handl (SAP SE): ODATA-1207 is OPEN

[19:06] Ralf Handl (SAP SE): Check whether known libraries rely on either getting an @id or all key fields

[19:08] Ralf Handl (SAP SE): 6.Next meetings [9:50 am PT]

a.Thursday Mm 16, 2018 during 8-10 am PDT (17:00-19:00 CEST)

b.Thursday Mm 23, 2018 during 8-10 am PDT (17:00-19:00 CEST)

[19:08] Ralf Handl (SAP SE): Mm == August

[19:08] Ralf Handl (SAP SE): 7.AOB and wrap up [9:55 am PT]

[19:08] Ralf Handl (SAP SE): Meeting is adjourned

 

 

From: odata@lists.oasis-open.org <odata@lists.oasis-open.org> On Behalf Of Handl, Ralf
Sent: Mittwoch, 8. August 2018 16:20
To: odata@lists.oasis-open.org
Subject: [CAUTION] [odata] Agenda for OData TC meeting on 2018-08-09

 

Note: new dial-in info via Skype for Business:

• 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

 

Here [1] is a draft agenda for the OData TC (Technical Committee) meeting scheduled on Thursday August 09, 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]

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

 

2.        Approve agenda [8:05 am PT]

 

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

1. Minutes from August 02, 2018 TC meeting: https://www.oasis-open.org/committees/download.php/63669/odata-meeting-223_on-20180802-minutes-informal.html

                                  i.    No quorum, nothing to approve

 

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

1. Due

                                  i.    #0038 Prepare proposal for REST Profile / OData Essentials – Mike Pizzo – 2018-08-08

2. Upcoming

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

3. Pending

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

 

5.        Issues [8:20 am PT]

1. Data Aggregation: NEW or OPEN

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

                                 ii.    ODATA-1206 Explicitly note support for collection-valued navigation/complex properties in property paths in aggregate/groupby

                                iii.    ODATA-1205 Examples 53, 54, and 59 are not compliant with Data Aggregation ABNF

                                iv.    ODATA-947 Transformation for computing ratios with aggregated values

                                 v.    ODATA-945 Correct examples 53 and 54

 

2. Vocabularies: Annotation Examples and Example Values for types, parameters, request/response bodies

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

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

 

3. V4.01: NEW or OPEN

                                  i.    ODATA-1213 Address use of 201 Created for Create Link Requests

                                 ii.    ODATA-1212 Validation term for allowed terms in Annotation Paths

                                iii.    ODATA-1211 ODATA-681 4.2 and 5.1: Explicitly state that an alias MUST NOT be identical to any other alias or namespace in the same document.

                                iv.    ODATA-1210 CSDL ReturnType element needs to specify rules for Nullable and Collection with entity types

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

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

                               vii.    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)

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

                                ix.    ODATA-1196 Clarify update of media streams

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

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

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

                              xiii.    ODATA-1189 Conformance: Nullable for collections

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

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

                              xvi.    ODATA-1183 Allow Singletons to be null

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

                            xviii.    ODATA-1177 Core: add term SchemaLocation

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

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

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

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

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

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

                            xxv.    ODATA-1135 Document use of JSON $schema

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

 

4. Vocabularies: NEW or OPEN with concrete proposal

                                  i.    ODATA-1212 Validation term for allowed terms in Annotation Paths

                                 ii.    ODATA-1209 Term for original OData version of (auto-)converted $metadata

                                iii.    ODATA-1204 Vocabularies Document references OData Version 4.01. Part 3: Common Schema Definition Language (CSDL)

                                iv.    ODATA-1176 Capabilities: add new term SelectRestrictions

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

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

 

5. Vocabularies: NEW or OPEN that need more discussion

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

                                 ii.    ODATA-1199 ODATA-884 / Add property SystemQueryOptions to call out supported system query options per request method

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

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

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

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

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

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

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

 

6.        Next meetings [9:50 am PT]

1. Thursday Mm 16, 2018 during 8-10 am PDT (17:00-19:00 CEST)
2. Thursday Mm 23, 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