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

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

[17:01] Room information was updated by: Ralf Handl (SAP SE)

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

2.Approve agenda [8:05 am PT]

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

a.Minutes from August 30, 2018 TC meeting: https://www.oasis-open.org/committees/download.php/63860/odata-meeting-227_on-20180830-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]

a.Upcoming

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

b.In progress

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

5.Issues [8:20 am PT]

a.APPLIED

i.ODATA-1163 A Case for Common Expressions

b.Vocabularies: NEW or OPEN with concrete proposal

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

c.V4.01: NEW or OPEN 

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

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

iii.ODATA-1196 Clarify update of media streams

iv.ODATA-1217 Clients should read symbolic values in CSDL case-insensitive

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

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

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

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

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

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

xi.ODATA-1189 Conformance: Nullable for collections

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

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

xiv.ODATA-1183 Allow Singletons to be null

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

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

d.Data Aggregation: NEW or OPEN (deferred to F2F)

i.ODATA-1207 Clarify need for @odata.id in nested response structures (deferred to F2F)

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

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

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

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

ii.ODATA-1214 Annotate constructor actions

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

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

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

vi.ODATA-1176 Capabilities: add new term SelectSupported

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

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

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

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

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

f.Vocabularies: NEW or OPEN that need more discussion

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

6.Next meetings [9:50 am PT]

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

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

c.Face-to-Face Thursday & Friday September 27 & 28, 2018 during 9-17 am PDT & 9-15 PDT (18:00-02:00 CEST & 18:00-00: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

Room Information:

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

2.Approve agenda [8:05 am PT]

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

a.Minutes from August 30, 2018 TC meeting: https://www.oasis-open.org/committees/download.php/63860/odata-meeting-227_on-20180830-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]

a.Upcoming

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

b.In progress

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

5.Issues [8:20 am PT]

a.APPLIED

i.ODATA-1163 A Case for Common Expressions

b.Vocabularies: NEW or OPEN with concrete proposal

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

c.V4.01: NEW or OPEN 

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

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

iii.ODATA-1196 Clarify update of media streams

iv.ODATA-1217 Clients should read symbolic values in CSDL case-insensitive

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

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

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

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

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

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

xi.ODATA-1189 Conformance: Nullable for collections

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

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

xiv.ODATA-1183 Allow Singletons to be null

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

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

d.Data Aggregation: NEW or OPEN (deferred to F2F)

i.ODATA-1207 Clarify need for @odata.id in nested response structures (deferred to F2F)

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

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

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

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

ii.ODATA-1214 Annotate constructor actions

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

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

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

vi.ODATA-1176 Capabilities: add new term SelectSupported

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

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

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

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

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

f.Vocabularies: NEW or OPEN that need more discussion

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

6.Next meetings [9:50 am PT]

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

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

c.Face-to-Face Thursday & Friday September 27 & 28, 2018 during 9-17 am PDT & 9-15 PDT (18:00-02:00 CEST & 18:00-00: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): Voting Members: 4 of 10 (40%) (used for quorum calculation)

[17:03] Ralf Handl (SAP SE): Voting Members: 5 of 10 (50%) (used for quorum calculation)

[17:06] Ralf Handl (SAP SE): Voting Members: 7 of 10 (70%) (used for quorum calculation)

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

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

[17:08] Ralf Handl (SAP SE): Agenda is approved

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

a.Minutes from August 30, 2018 TC meeting: https://www.oasis-open.org/committees/download.php/63860/odata-meeting-227_on-20180830-minutes.html

[17:09] Ralf Handl (SAP SE): Mike: minutes look fine

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

[17:10] Ralf Handl (SAP SE): 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]

a.Upcoming

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

b.In progress

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

[17:10] Ralf Handl (SAP SE): Documents received by IANA, one question, Mark will answer it

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

a.APPLIED

i.ODATA-1163 A Case for Common Expressions

[17:11] Ralf Handl (SAP SE): https://issues.oasis-open.org/browse/ODATA-1163

[17:11] Ralf Handl (SAP SE): _expression_ case(Edm.Boolean:_expression_, ..., Edm.Boolean:_expression_)

[17:12] Ralf Handl (SAP SE): _expression_ case(Edm.Boolean:_expression_, ..., Edm.Boolean:_expression_,_expression_)

[17:12] Ralf Handl (SAP SE): _expression_ case(Edm.Boolean:_expression_, ..., Edm.Boolean:_expression_,true:_expression_)

[17:16] Michael Pizzo: I move we modify the case statement introduced by ODATA-1163 by removing the final default argument. The same can be achieved using true:_expression_ as the final argument.

[17:17] Hubert Heijkers (IBM): I second

[17:18] Michael Pizzo: I move we close OData-1163 as applied, including the removal of the final default argument.

[17:18] Ralf Handl (SAP SE): No objection, motion passes

[17:18] Gerald Krause (SAP): I second

[17:18] Ralf Handl (SAP SE): No objections, motion passes

[17:19] Ralf Handl (SAP SE): b.Vocabularies: NEW or OPEN with concrete proposal

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

[17:19] Ralf Handl (SAP SE): https://issues.oasis-open.org/browse/ODATA-1193

[17:20] Ralf Handl (SAP SE): https://github.com/oasis-tcs/odata-vocabularies/pull/19

[17:21] Hubert Heijkers (IBM): Please join my WebEx meeting using this linkL https://ibm.webex.com/join/hubert.heijkers

[17:25] Ralf Handl (SAP SE): https://lync.co.sap.com/meet/ralf.handl/Q4QB1098

[17:54] Michael Pizzo: I move we resolve OData-1193 by applying the changes proposed in https://github.com/oasis-tcs/odata-vocabularies/pull/19.

[17:55] Hubert Heijkers (IBM): I second

[17:55] Ted Jones (Red Hat)7: Ugh.. internet issues. There is really only one of me. 

[17:55] Ralf Handl (SAP SE): ODATA-1193 is RESOLVED as proposed

[17:58] Hubert Heijkers (IBM): I move to close ODATA-1193 as applied.

[17:58] Mark Biamonte (Progress): I second

[17:58] Ralf Handl (SAP SE): ODATA-1193 is CLOSED as applied

[17:59] Ted Jones (Red Hat)7 morphed into Ted Jones (Red Hat)

[17:59] Ralf Handl (SAP SE): https://issues.oasis-open.org/browse/ODATA-1170

[17:59] Ralf Handl (SAP SE): Allow @odata.type next to $EnumMember for isomorphy to CSDL XML

[18:01] Ralf Handl (SAP SE): Current

"@com.odata.v4.technical.scenario.TermEnum": {

  "$EnumMember": "String1,String3"

}

[18:01] Ralf Handl (SAP SE): Proposed

"@com.odata.v4.technical.scenario.TermEnum": "String1,String3"

[18:02] Ralf Handl (SAP SE): Current with type"@com.odata.v4.technical.scenario.TermEnum": {

  "$EnumMember@odata.type": "#Namespace1_Alias.ENString",

  "$EnumMember": "String1,String3"

}

[18:02] Ralf Handl (SAP SE): "@com.odata.v4.technical.scenario.TermEnum": {

  "$EnumMember@odata.type": "#Namespace1_Alias.ENString",

  "$EnumMember": "String1,String3"

}

[18:02] Ralf Handl (SAP SE): New short form

"@com.odata.v4.technical.scenario.TermEnum@odata.type": "#Namespace1_Alias.ENString",

"@com.odata.v4.technical.scenario.TermEnum": "String1,String3"

[18:15] Gerald Krause (SAP): I move to close ODATA-1163 as applied.

[18:16] Hubert Heijkers (IBM): I second

[18:16] Ralf Handl (SAP SE): ODATA-1163 is CLOSED as applied

[18:16] Ralf Handl (SAP SE): c.V4.01: NEW or OPEN 

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

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

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

[18:19] Ralf Handl (SAP SE): Mike: use err007 or something similar instead of foo, bar, and baz

[18:19] Ralf Handl (SAP SE): how about catch22#

[18:20] Ralf Handl (SAP SE): err123

[18:20] Ralf Handl (SAP SE): not42

[18:21] Ralf Handl (SAP SE): Current example:

{

  "error": {

    "code": "501",

    "message": "Unsupported functionality",

    "target": "query",

    "details": [

      {

       "code": "301",

       "target": "$search", 

       "message": "$search query option not supported"

      }

    ],

    "innererror": {

      "trace": [...],

      "context": {...}

    }

  }

}

[18:22] Ralf Handl (SAP SE): err123

fourtytwo

[18:23] Michael Pizzo: I move to resolve ODATA-1197 by substituting the values "err123" and "fourtytwo"

[18:23] Michael Pizzo: Stephan seconds?

[18:23] Ralf Handl (SAP SE): Stefan seconds

[18:23] Ralf Handl (SAP SE): ODATA-1197 is RESOLVED as proposed

[18:23] Ralf Handl (SAP SE): ii.ODATA-1195 11.2.6.6: value of $search is search _expression_, not boolean _expression_

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

[18:24] Ralf Handl (SAP SE): ODATA-1195 is OPEN

[18:25] Michael Pizzo: I move we approve ODATA-1195 as proposed

[18:25] Hubert Heijkers (IBM): I second

[18:25] Ralf Handl (SAP SE): ODATA-1195 is RESOLVED as proposed

[18:26] Ralf Handl (SAP SE): iii.ODATA-1196 Clarify update of media streams

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

[18:26] Ralf Handl (SAP SE): Description

Section 8.2.8.7 explicitly forbids return=representation for updating stream property values but allows it for updating media entity streams.

Also the text does not explicitly state that 204 No Content is the only response for updating stream property values, and that it is the default response for updating media entity streams.

[18:27] Ralf Handl (SAP SE): Proposal

Allow preference return=representation for all requests and make clear that the default is "204 No Content" for updating both kinds of streams.

[18:36] Ralf Handl (SAP SE): ODATA-1196 is OPEN

[18:37] Hubert Heijkers (IBM): I move to resolve ODATA-1196 as proposed

[18:37] Ralf Handl (SAP SE): Stefan seconds

[18:38] Ralf Handl (SAP SE): ODATA-1196 is RESOLVED as proposed

[18:39] Ralf Handl (SAP SE): iv.ODATA-1217 Clients should read symbolic values in CSDL case-insensitive

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

[18:43] Ralf Handl (SAP SE): ODATA-1217 is OPEN

[18:49] Ralf Handl (SAP SE): Services SHOULD use current casing, all-lowercase

[18:49] Ralf Handl (SAP SE): Clients SHOULD accept any casing, even for 4.0 services

[18:50] Michael Pizzo: Services SHOULD use the casing specified in the specification; clients SHOULD handle these symbolic values in a case-insensitive manner in order to be more robust.

[18:52] Michael Pizzo: MOre specifically:

Services SHOULD use lower case for symbolic values "variable" and "floating" for scale, and "max" for MaxLength, as specified in the specification; clients SHOULD handle these symbolic values in a case-insensitive manner in order to be more robust.

[18:53] Hubert Heijkers (IBM): I move to resolve ODATA-1217 as per the amended proposal

[18:53] Ralf Handl (SAP SE): Stefan seconds

[18:54] Ralf Handl (SAP SE): ODATA-1217 is RESOLVED as proposed

[18:54] Ralf Handl (SAP SE): Mike: conference room for F2F is reserved

[18:56] Michael Pizzo: The meetings will be taking place in building 41, Conf Room 64, on the Redmond Main Campus.

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

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

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

c.Face-to-Face Thursday & Friday September 27 & 28, 2018 during 9-17 am PDT & 9-15 PDT (18:00-02:00 CEST & 18:00-00:00 CEST)

[18:58] Ralf Handl (SAP SE): Hubert might not make September 20

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

[18:59] 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, 5. September 2018 10:23
To: odata@lists.oasis-open.org
Subject: [CAUTION] [odata] Agenda for OData TC meeting on 2018-09-06

 

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

 

2.        Approve agenda [8:05 am PT]

 

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

1. Minutes from August 30, 2018 TC meeting: https://www.oasis-open.org/committees/download.php/63860/odata-meeting-227_on-20180830-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]

1. Upcoming

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

2. In progress

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

 

5.        Issues [8:20 am PT]

1. APPLIED

                                  i.    ODATA-1163 A Case for Common Expressions

 

2. Vocabularies: NEW or OPEN with concrete proposal

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

 

3. V4.01: NEW or OPEN

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

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

                                iii.    ODATA-1196 Clarify update of media streams

                                iv.    ODATA-1217 Clients should read symbolic values in CSDL case-insensitive

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

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

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

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

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

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

                                xi.    ODATA-1189 Conformance: Nullable for collections

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

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

                              xiv.    ODATA-1183 Allow Singletons to be null

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

                              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

 

4. Data Aggregation: NEW or OPEN (deferred to F2F)

                                  i.    ODATA-1207 Clarify need for @odata.id in nested response structures (deferred to F2F)

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

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

 

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

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

                                 ii.    ODATA-1214 Annotate constructor actions

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

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

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

                                vi.    ODATA-1176 Capabilities: add new term SelectSupported

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

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

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

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

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

 

6. Vocabularies: NEW or OPEN that need more discussion

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

 

6.        Next meetings [9:50 am PT]

1. Thursday September 13, 2018 during 8-10 am PDT (17:00-19:00 CEST)
2. Thursday September 20, 2018 during 8-10 am PDT (17:00-19:00 CEST)
3. Face-to-Face Thursday & Friday September 27 & 28, 2018 during 9-17 am PDT & 9-15 PDT (18:00-02:00 CEST & 18:00-00: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