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

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

[17:03] 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 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]

a.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]

a.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]

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-1176 Capabilities: add new term SelectRestrictions

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

b.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

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

d.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

e.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

f.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]

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

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

c.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

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

[17:05] Michael Pizzo: I am on, but about to get kicked off for a couple minutes while they work on the power...  back shortly.

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

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

[17:08] Ralf Handl (SAP SE): Add to 5.d: https://issues.oasis-open.org/browse/ODATA-1163 - case function

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

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

[17:09] Ralf Handl (SAP SE): https://www.oasis-open.org/apps/org/workgroup/odata/download.php/63841/latest/odata-meeting-226_on-20180823-minutes.html

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

[17:11] 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:11] Ralf Handl (SAP SE): Mark: Chet Ensign submitted the registration documents yesterday

[17:12] Ralf Handl (SAP SE): Mark will register on the IANA mailing list to keep us updated

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

a.APPLIED

[17:13] Ralf Handl (SAP SE): i.ODATA-1176 Capabilities: add new term SelectRestrictions

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

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

[17:14] Ralf Handl (SAP SE): Three changed files: https://github.com/oasis-tcs/odata-vocabularies/pull/14/files

[17:14] Ralf Handl (SAP SE): <Term Name="SelectSupported" Type="Core.Tag" Nullable="false" DefaultValue="true" AppliesTo="EntitySet Singleton">

        <Annotation Term="Core.Description" String="Supports $select" />

      </Term>

[17:18] Ralf Handl (SAP SE): Hubert: how to express that a complex or navigation property does not support $select

[17:21] Hubert Heijkers (IBM): I move to reject the current application of this issue.

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

[17:23] Ralf Handl (SAP SE): No objections, application is rejected

[17:25] Hubert Heijkers (IBM): I move to reject the current proposal.

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

[17:25] Ralf Handl (SAP SE): No objection, ODATA-1176 is OPEN again

[17:26] Hubert Heijkers (IBM): I propose to also add SelectSupported to the CollectionPropertyRestrictionsType and NavigationPropertyRestriction in our capabilities vocabulary

[17:27] Hubert Heijkers (IBM): I move to resolve ODATA-1176 as per the amended proposal

[17:28] Michael Pizzo: I second

[17:28] Ralf Handl (SAP SE): ODATA-1176 is RESOLVED with the amended proposal

[17:37] Ralf Handl (SAP SE): @NavigationRestrictions: {

RestrictedProperties:[

  {

     NavigationProperty: Customers,

     TopSupported:false

  }

]}

[17:47] Ralf Handl (SAP SE): Need some "global" flag "CanDoSelectWithNestedQueryOptions" applicable to entity container

[17:47] Ralf Handl (SAP SE): Probably also to entity set and singleton

[18:04] Ralf Handl (SAP SE): Defer to F2F and discuss in context of ODATA-1005 - capabilities for all new V4.01 functionality

[18:04] George Ericson (Dell): Placeholder for discussion on how to facilitate conversations between this committee and external organizations like DMTF Redfish.  Perhaps an alliance relationship.

[18:04] Ralf Handl (SAP SE): ii.ODATA-1167 Add way to specify which batch formats (if any) are supported by a service

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

[18:04] Ralf Handl (SAP SE): Add a SupportedFormats property to the BatchSupportType:

<Property Name="SupportedFormats" Type="Collection(Edm.String)" Nullable="false">

  <Annotation Term="Core.Description" String="Media types of supported formats for $batch" />

  <Annotation Term="Core.IsMediaType" />

  <Annotation Term="Validation.AllowedValues">

    <Collection>

      <Record>

        <PropertyValue Property="Value" String="multipart/mixed" />

        <Annotation Term="Core.Description"

          String="Multipart Batch Format, see http://docs.oasis-open.org/odata/odata/v4.01/cs01/part1-protocol/odata-v4.01-cs01-part1-protocol.html#sec_MultipartBatchFormat" />

      </Record>

      <Record>

        <PropertyValue Property="Value" String="application/json" />

        <Annotation Term="Core.Description"

          String="JSON Batch Format, see http://docs.oasis-open.org/odata/odata-json-format/v4.01/cs01/odata-json-format-v4.01-cs01.html#sec_BatchRequestsandResponses" />

      </Record>

    </Collection>

  </Annotation>

</Property>

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

[18:08] Hubert Heijkers (IBM): I move to resolve ODATA-1167 as proposed.

[18:08] Hubert Heijkers (IBM): I move to close ODATA-1167 as applied.

[18:08] Michael Pizzo: I second

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

[18:18] Ralf Handl (SAP SE): c.Data Aggregation: NEW or OPEN

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

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

[18:27] Michael Pizzo: Propose: in OData 4.01, say that the absence of an @id and key properties means that the returned entity cannot be read, updated, or compared to other entities.

[18:40] Michael Pizzo: That would mean that, for the JSON minimal metadata, if you didn't select the key properties you might not be able to update (but in another format, or full metadata, you might be able to update).  We would have to make a general rule that, if you apply a select, you must include the key properties if you want to update.  This would be a bit of a step backward for 4.01.

[18:46] Michael Pizzo: I'm okay with omitting the id in a 4.01 aggregation response, since that was never updatable anyway.  Just concerned about relaxing for general case.

[18:47] Michael Pizzo: We *can* make the general statement that an entity that does not have an id cannot be reread, updated, or compared.

[18:48] Michael Pizzo: (or key properties in minimal)

[18:57] Ralf Handl (SAP SE): Mike: defer to F2F

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

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

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

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

[18:59] Ralf Handl (SAP SE): George can't make next week

[18:59] Ralf Handl (SAP SE): Hubert can't make September 20

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

[19:00] 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, 29. August 2018 10:56
To: odata@lists.oasis-open.org
Subject: [CAUTION] [odata] 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]

1. 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]

1. 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]

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-1176 Capabilities: add new term SelectRestrictions

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

 

2. 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

 

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

 

4. 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

 

5. 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

 

6. 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]

1. Thursday September 06, 2018 during 8-10 am PDT (17:00-19:00 CEST)
2. Thursday September 13, 2018 during 8-10 am PDT (17:00-19:00 CEST)
3. 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