RE: Agenda for OData TC meeting on 2019-09-19 - chat transcript

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

[‎19.‎09.‎2019 16:59] 

                1. Roll call [8:00 am]

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

Voting Members: 2 of 8 (25%) (used for quorum calculation)

 

[‎19.‎09.‎2019 17:03] 

Voting Members: 6 of 8 (75%) (used for quorum calculation)

 

[‎19.‎09.‎2019 17:03] 

Quorum achieved: yes

 

[‎19.‎09.‎2019 17:05] 

              2. Approve agenda [8:05 am]

 

[‎19.‎09.‎2019 17:05] 

Agenda is approved

 

[‎19.‎09.‎2019 17:07] 

              3. Approve minutes from previous meeting(s)

                            a. Minutes from September 12, 2019 TC meeting: https://www.oasis-open.org/committees/download.php/65917/Minutes%20of%202019-09-12%20Meeting%20%23267.docx 

 

[‎19.‎09.‎2019 17:08] 

Minutes are approved

 

[‎19.‎09.‎2019 17:08] 

No Title

              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:15 am]

                            a. Upcoming

                                          i.            #0039 Concept for Compact JSON data format – Hubert Heijkers – 2019-10-31

                                          ii.           #0037 Concept for binary data format – Hubert Heijkers – 2020-03-26

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

 

[‎19.‎09.‎2019 17:08] 

             5. Repeatable Requests [8:20 am]

                            a. Document Walkthrough

                                          i.            https://www.oasis-open.org/committees/download.php/65909/repeatable-requests-v1.0-wd01-2019-09-06.docx 

 

[‎19.‎09.‎2019 17:18] 

7.1.1.1.  Date/Time Formats

   Prior to 1995, there were three different formats commonly used by
   servers to communicate timestamps.  For compatibility with old
   implementations, all three are defined here.  The preferred format is
   a fixed-length and single-zone subset of the date and time
   specification used by the Internet Message Format [RFC5322].

     HTTP-date    = IMF-fixdate / obs-date

   An example of the preferred format is

     Sun, 06 Nov 1994 08:49:37 GMT    ; IMF-fixdate

 

We saved this conversation. You'll see it soon in the Conversations tab in Skype for Business and in the Conversation History folder in Outlook.

We saved this conversation. You'll see it soon in the Conversations tab in Skype for Business and in the Conversation History folder in Outlook.

We saved this conversation. You'll see it soon in the Conversations tab in Skype for Business and in the Conversation History folder in Outlook.

[‎19.‎09.‎2019 18:13] 

Clients MAY associate an id with individual nested entities in the request by using the Core.ContentID term defined in [OData-VocCore]. Services that respond with 201 Created SHOULD annotate the entities in the response using the same Core.ContentID value as specified in the request. 

 

[‎19.‎09.‎2019 18:27] 

             6. Issues [9:20 am]

 

[‎19.‎09.‎2019 18:31]  Ericson, George: 

OData 1325 review applied changes

 

[‎19.‎09.‎2019 18:33]  SAP Dial-In Connector 6: 

Audio to the Conference Bridge Provider conference has unexpectedly terminated. Please hold while we try to reestablish it.

 

[‎19.‎09.‎2019 18:53] 

No Title

                                          i.            ODATA-1331 Override entity set when extending an entity container (public comment)

                                          ii.           ODATA-1330 JSON Batch: explicitly state that continue-on-error=true

                                          iii.           ODATA-1328 Simplify query rules by removing $expand select option

                                          iv.          ODATA-1325 Explicitly state server behaviour when a client uses $select/$expand for an update response

                                          v.           ODATA-1324 Incorrect text about mediaEditLink control information

                                          vi.          ODATA-1321 Prefer:respond-async on individual requests within a batch request

                                          vii.         ODATA-1319 Clarify format parameter IEEE754Compatible with requests

 

[‎19.‎09.‎2019 18:54]  Mike Pizzo: 

I move to close ODATA-1331, ODATA-1330, ODATA-1328, ODATA-1325, ODATA-1324, ODATA-1321, and ODATA-1319 as applied

 

[‎19.‎09.‎2019 18:55]  Ericson, George: 

Second

 

[‎19.‎09.‎2019 18:55]  Borges, Matt: 

I second

 

[‎19.‎09.‎2019 18:55] 

No objections, motion passes

 

[‎19.‎09.‎2019 18:57] 

             7. Next meetings [9:50 am]

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

                           b.           Thursday October 03, 2019 during 8-10 am PDT (17:00-19:00 CEST) – public holiday in Germany

                           c.           Thursday October 10, 2019 during 8-10 am PDT (17:00-19:00 CEST)

                           d.           Thursday October 17, 2019 during 8-10 am PDT (17:00-19:00 CEST)

 

[‎19.‎09.‎2019 18:58] 

              8.  AOB and wrap up [9:55 am]

 

[‎19.‎09.‎2019 18:58]  Borges, Matt: 

https://issues.oasis-open.org/browse/ODATA-1274

 

[‎19.‎09.‎2019 18:58]  Borges, Matt: 

New wording for 11.4.2.2: Clients MAY associate an id with individual nested entities in the request by using the Core.ContentID term defined in [OData-VocCore]. Services that respond with 201 Created SHOULD annotate the entities in the response using the same Core.ContentID value as specified in the request. Services SHOULD advertise support for deep inserts through the Capabilities.DeepInsertSupport term, defined in [OData-VocCap]; services that advertise support through Capabilities.DeepInsertSupport MUST return the Core.ContentID for the inserted or updated entities.

 

Clarify that the response must include the entity ID (or all key properties if conventional IDs are used) for all entities returned in the response for a create or update.

 

[‎19.‎09.‎2019 18:59] 

Meeting is adjourned

 

 

 

 

From: odata@lists.oasis-open.org <odata@lists.oasis-open.org> On Behalf Of Handl, Ralf
Sent: Donnerstag, 19. September 2019 11:43
To: odata@lists.oasis-open.org
Subject: [CAUTION] [odata] Agenda for OData TC meeting on 2019-09-19

 

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

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

 

      2. Approve agenda [8:05 am]

 

      3. Approve minutes from previous meeting(s)

           a. Minutes from September 12, 2019 TC meeting: https://www.oasis-open.org/committees/download.php/65917/Minutes%20of%202019-09-12%20Meeting%20%23267.docx

 

      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:15 am]

           a. Upcoming

                 i.    #0039 Concept for Compact JSON data format – Hubert Heijkers – 2019-10-31

                 ii.   #0037 Concept for binary data format – Hubert Heijkers – 2020-03-26

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

 

    5. Repeatable Requests [8:20 am]

           a. Document Walkthrough

                 i.    https://www.oasis-open.org/committees/download.php/65909/repeatable-requests-v1.0-wd01-2019-09-06.docx

 

    6. Issues [9:20 am]

          a. APPLIED

                 i.    ODATA-1331 Override entity set when extending an entity container (public comment)

                 ii.   ODATA-1330 JSON Batch: explicitly state that continue-on-error=true

                 iii.  ODATA-1328 Simplify query rules by removing $expand select option

                 iv.  ODATA-1325 Explicitly state server behaviour when a client uses $select/$expand for an update response

                 v.   ODATA-1324 Incorrect text about mediaEditLink control information

                 vi.  ODATA-1321 Prefer:respond-async on individual requests within a batch request

                 vii. ODATA-1319 Clarify format parameter IEEE754Compatible with requests

                 viii.      ODATA-1327 Extend applicability of Core.MediaType and Core.AcceptableMediaTypes to non-stream (string/binary) properties and terms

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

 

          b. V4.01: NEW or OPEN

                 i.    ODATA-1323 Clarify representation of GEO literals in annotations (XML, JSON)

                ii.   ODATA-1333 Add Terms, Abbreviated Terms, and Symbols sections to specifications

 

          c. Vocabularies: NEW or OPEN with concrete proposal

                i.    ODATA-1326 Enhance syntax of term Validation.OpenPropertyTypeConstraint

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

 

          d. Vocabularies: NEW or OPEN that need more discussion

                i.    ODATA-1300 Capabilities: clarify CountRestrictions and ExpandRestrictions

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

                ii.   ODATA-1275 Describing and querying "JSON properties"

                iii.  ODATA-1214 Annotate constructor actions

                iv.  ODATA-1140 Add details to HttpResponse

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

                vi.  ODATA-1060 Improve specification of element response requirements

                vii. ODATA-884 Allow describing possible responses to requests for a particular resource (public comment c201510e00019)

 

           e. Data Aggregation: NEW or OPEN

                 i.    ODATA-1332 Support augmenting entities with aggregated values from related entities

                 ii.   ODATA-1218 Transformations for recursive hierarchy processing

                 iii.  ODATA-945 Correct examples 53 and 54

 

     7. Next meetings [9:50 am]

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

          b.  Thursday October 03, 2019 during 8-10 am PDT (17:00-19:00 CEST) – public holiday in Germany

          c.   Thursday October 10, 2019 during 8-10 am PDT (17:00-19:00 CEST)

          d.  Thursday October 17, 2019 during 8-10 am PDT (17:00-19:00 CEST)

 

      8.  AOB and wrap up [9:55 am]

 

[2] References

• Conference call, Chat & 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/65915/TC%20Timeline-2019-09-18.docx