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

[â04.â04.â2019 17:01] 

No soaphub today

 

[â04.â04.â2019 17:02] 

Voting Members: 6 of 9 (66%) (used for quorum calculation) 

 

[â04.â04.â2019 17:03] 

Here [1] is a draft agenda for the OData TC (Technical Committee) meeting scheduled on Thursday April 04, 2019 during 8-10 am PDT (17:00-19:00 CET). 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=47980    

 

[â04.â04.â2019 17:03] 

1.        Approve agenda [8:05 am PT]

 

[â04.â04.â2019 17:04] 

                                  i.    ODATA-1297 JSON Batch: clarify values of body property, context URL, batch in batch, continue-on-error

 

[â04.â04.â2019 17:05] 

Do this before document walkthrough

Agenda is approved with this change

 

[â04.â04.â2019 17:05] 

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

1.     
Minutes from March 07, 2019 TC meeting: https://www.oasis-open.org/committees/download.php/64931/Minutes%20of%202019-03-07%20Meeting%20%23250.docx   

Minutes from March 21, 2019 TC meeting: https://www.oasis-open.org/committees/download.php/64933/Minutes%20of%202019-03-21%20Meeting%20%23252.docx

 

[â04.â04.â2019 17:05] 

Meeting minutes are approved

 

[â04.â04.â2019 17:07] 

1.        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 â 2019-06-27

1.     
In progress 

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

 

[â04.â04.â2019 17:08] 

Face-to-face

 

[â04.â04.â2019 17:08] 

Hubert: August in New Zealand

 

[â04.â04.â2019 17:10] 

Topics:

 

[â04.â04.â2019 17:10] 

- Temporal

 

[â04.â04.â2019 17:10] 

- REST-EZ

 

[â04.â04.â2019 17:10] 

- Infrastructure / make producing and consuming OData easier

 

[â04.â04.â2019 17:11] 

- Aggregation

 

[â04.â04.â2019 17:13] 

Possible dates:

- June, one of the first three weeks

 

[â04.â04.â2019 17:14] 

George to create a Doodle for possible Calendar weeks

 

[â04.â04.â2019 17:14] 

Location proposals are welcome!

 

[â04.â04.â2019 17:17] 

Which continent/country would suit most members

 

[â04.â04.â2019 17:18] 

Hubert can offer Ottawa

 

[â04.â04.â2019 17:18] 

Mike can host in Redmond

 

[â04.â04.â2019 17:19] 

George can host in Hopkinton, Massachusetts

 

[â04.â04.â2019 17:21] 

CW24, June 10-14

 

[â04.â04.â2019 17:22] 

CW30, July 22-26

 

[â04.â04.â2019 17:22] 

CW31, July 29-August 02

 

[â04.â04.â2019 17:23] 

CW25, June 17-21

 

[â04.â04.â2019 17:26] 

Typical schedule: arrive Mon, pre-meeting Tue-Wed, meeting Thu-Fri

 

[â04.â04.â2019 17:27] 

ODATA-1297 JSON Batch: clarify values of body property, context URL, batch in batch, continue-on-error

 

[â04.â04.â2019 17:27] 

No Title

Clarify:

1.                   
Can the body property
 in request/response object have the value null? If yes, does this mean "empty body" or "no body"?
 See also next question. 

2.                   
Can responses with status:204 have
 a body? 

3.                   
"Textual media types" are represented as a string: what exactly are "textual media types"? 

4.                   
RFC 7230 distinguishes between "message body" and "payload body": which one is body,
 i.e. can a Transfer-Encoding (gzip, chunked, ...) be applied? 

5.                   
What is the context URL of a JSON batch request or JSON batch response? 

6.                   
Can a request object within a JSON batch request be itself a (JSON) batch request? 

7.                    
Why do we allow the preference continue-on-error=false at
 all? The client can specify explicit dependencies with dependsOn if it wants certain dependency
 chains to stop at first error. 

 

[â04.â04.â2019 17:32] 

Mike: omit body property if there is no body

 

[â04.â04.â2019 17:33]  Ericson, George: 

Agree with Mike.  Simplifies implementation logic.

 

[â04.â04.â2019 17:34] 

Hubert: allow body:null even with status:204

 

[â04.â04.â2019 17:35] 

1: yes, means "no body"

 

[â04.â04.â2019 17:35] 

2: yes

 

[â04.â04.â2019 17:36]  Ericson, George: 

Concensus is omit or xxx:null are equivalent representations.

 

[â04.â04.â2019 17:37] 

3: text/*

 

[â04.â04.â2019 17:37] 

application/xml

 

[â04.â04.â2019 17:40] 

Ralf to prepare list what is "textual"

 

[â04.â04.â2019 17:40] 

Check if IANA registration already provides that information

 

[â04.â04.â2019 17:42] 

Hubert: concrete list only reflects currently existing media types

 

[â04.â04.â2019 17:43] 

4: Hubert: compression and chunking apply to the JSON batch, not the nested bodies

 

[â04.â04.â2019 17:44] 

Mike: would expect that body can be compressed/chunked, would be reflected in Transfer-Encoding header

 

[â04.â04.â2019 17:45] 

Hubert: why not

 

[â04.â04.â2019 17:46] 

5: explicitly mention that these don't have a context URL

 

[â04.â04.â2019 17:46] 

Hubert: with minimal metadata it would be nice

 

[â04.â04.â2019 17:46] 

@context:x$batch

 

[â04.â04.â2019 17:47] 

@context: #batch-response

 

[â04.â04.â2019 17:48] 

would be  $batchResponse to fit in with current naming scheme

 

[â04.â04.â2019 17:49] 

Mike: would want it optional - already implemented - which would make it less useful

 

[â04.â04.â2019 17:54] 

5: no context URL

 

[â04.â04.â2019 17:55] 

6: should already be disallowed

 

[â04.â04.â2019 18:00] 

7: If processing stops in error the batch response can be incomplete, whereas with dependsOn the batch response would have a response for each individual request which has status:412
 if the request has been skipped due to a failed dependency 

 

[â04.â04.â2019 18:10] 

Ralf to craft a proposal for this issue

 

[â04.â04.â2019 18:11] 

1.        V4.01: Document Walkthrough

 

[â04.â04.â2019 18:11] 

1.      
Part 1: Protocol â https://www.oasis-open.org/committees/download.php/64946/odata-v4.01-wd06-part1-protocol-2019-03-22.docx 

 

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.

[â04.â04.â2019 18:57]  Ericson, George: 

Continue next week at clause 10.8

 

[â04.â04.â2019 18:57] 

Continue walkthrough on Protocol starting at section 10.8

 

[â04.â04.â2019 19:00] 

Hubert: check if OData-Error header needs to be in first chunk (header part) to be allowed as a trailing header

 

[â04.â04.â2019 19:00] 

1.        Next meetings [9:50 am PT]

1.     
Thursday April 11, 2019 during 8-10 am PDT (17:00-19:00 CET)  

2.     
Thursday April 18, 2019 during 8-10 am PDT (17:00-19:00 CET)  

3.      
Thursday April 25, 2019 during 8-10 am PDT (17:00-19:00 CET) 

 

[â04.â04.â2019 19:01] 

Mike cannot attend April 11

 

[â04.â04.â2019 19:02] 

Gerald cannot attend April 25

 

[â04.â04.â2019 19:02] 

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

 

[â04.â04.â2019 19:02] 

Meeting is adjourned

 

 

 

 

From:  <>
On Behalf Of Handl, Ralf

Sent: Freitag, 22. MÃrz 2019 18:43

To: 

Subject: [CAUTION] [odata] Agenda for OData TC meeting on 2019-04-04

 

Here [1] is a draft agenda for the OData TC (Technical Committee) meeting
scheduled on
Thursday April 04, 2019 during 8-10 am PDT (17:00-19:00 CET).
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=47980   

 

2.       
Approve agenda [8:05 am PT]

 

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

Minutes from March 07, 2019 TC meeting:

https://www.oasis-open.org/committees/download.php/64931/Minutes%20of%202019-03-07%20Meeting%20%23250.docx  

Minutes from March 21, 2019 TC meeting:

https://www.oasis-open.org/committees/download.php/64933/Minutes%20of%202019-03-21%20Meeting%20%23252.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:15am PT]

Upcoming

                                 
i.    #0037

Concept for Google Protocol Buffers as a data format â Hubert Heijkers â 2019-03-28

In progress

                                 
i.    #0036

Register the OData- headers and preferences with IANA â Mark Biamonte â 2018-07-26

 

5.       
V4.01: Document Walkthrough

Part 1: Protocol 
â

https://www.oasis-open.org/committees/download.php/64946/odata-v4.01-wd06-part1-protocol-2019-03-22.docx

Part 2: URL Conventions
â

https://www.oasis-open.org/committees/download.php/64682/odata-v4.01-wd06-part2-url-conventions-2019-02-08.docx

CSDL JSON â

https://www.oasis-open.org/committees/download.php/64947/odata-csdl-json-v4.01-wd05-2019-03-22.docx

CSDL XML â

https://www.oasis-open.org/committees/download.php/64948/odata-csdl-xml-v4.01-wd06-2019-03-22.docx

JSON Format
â

https://www.oasis-open.org/committees/download.php/64925/odata-json-format-v4.01-wd06-2019-03-15.docx

Whatâs New â

https://www.oasis-open.org/committees/download.php/64737/new-in-odata-v4.01-wd03.docx

 

6.       
Issues [8:20 am PT]

APPLIED

                                 
i.    ODATA-1285
 ODATA-1099 / Add ReadByKeyRestrictions similar to ReadRestrictions

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

 

V4.01: 
NEW or OPEN

                                 
i.    ODATA-1296
 Explicitly allow the underscore in a search word

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

 

Data Aggregation: 
NEW or OPEN

                                 
i.    ODATA-1218
 Transformations for recursive hierarchy processing

                                
ii.    ODATA-945
 Correct examples 53 and 54

 

Vocabularies: 
NEW or OPEN with concrete proposal

                                 
i.    ODATA-1264
 CRUDQ descriptions on entity sets

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

 

Vocabularies: 
NEW or OPEN that need more discussion

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

                                
ii.    ODATA-1214
 Annotate constructor actions

                               
iii.    ODATA-1140
 ODATA-884 / Add details to HttpResponse

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

                                
v.    ODATA-1060
 Improve specification of element response requirements

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

 

7.       
Next meetings [9:50 am PT]

Thursday April 11, 2019 during 8-10 am PDT (17:00-19:00 CET)

Thursday April 18, 2019 during 8-10 am PDT (17:00-19:00 CET)

Thursday April 25, 2019 during 8-10 am PDT (17:00-19:00 CET)

 

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

 

[2]
References

Chat room:
https://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/64563/TC%20Timeline%202019-01-23.docx