RE: Agenda for OData TC meeting on 2019-06-13 - chat transkript

[‎13.‎06.‎2019 17:01] 

Voting Members: 3 of 9 (33%) (used for quorum calculation) 

 

[‎13.‎06.‎2019 17:02] 

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

 

[‎13.‎06.‎2019 17:03] 

Achieved quorum: yes

 

[‎13.‎06.‎2019 17:04] 

2. Approve agenda [8:05 am PT] 

 

[‎13.‎06.‎2019 17:04] 

No changes to the agenda

 

[‎13.‎06.‎2019 17:04] 

Agenda is approved

 

[‎13.‎06.‎2019 17:05] 

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

1.      
Minutes from June 06, 2019 TC meeting: https://www.oasis-open.org/committees/download.php/65432/Minutes%20of%202019-06-06%20Meeting%20%23260.docx 

 

[‎13.‎06.‎2019 17:05] 

Minutes are approved

 

[‎13.‎06.‎2019 17:05] 

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

 

[‎13.‎06.‎2019 17:05] 

Nothing due today

 

[‎13.‎06.‎2019 17:05] 

No Title

1.     
Face-to-Face Meeting 2019 [8:15 am PT]  

1.     
Date 

                                          i.    CW 25 2019, June 17-21

                                         ii.    Pre-Meeting Tuesday June 18 and Wednesday June 19, attendance is optional

                                        iii.    Face-to-Face-Meeting Thursday June 20 and Friday June 21, counts towards voter eligibility

1.     
Location 

                                          i.    228 South Street, Hopkinton, MA 01748…

1.     
Proposed agenda 

                                  i.    Tuesday June 18

1.     
Prepare proposals for all remaining V4.01 issues  

2.     
IANA registration for headers and preferences – only OData-specific versions as suggested by Mark Nottingham?  

3.     
Extension for Temporal Data – discuss new approach for preserving service structure 

                                 ii.    Wednesday June 19

1.     
REST-EZ (aka REST Profile for OData)  

2.     
Extension for Data Aggregation – Hierarchies 

                                iii.    Thursday June 20

1.     
Finalize V4.01  

2.     
Repeatable Requests – document walkthrough  

3.     
OData-to-OpenAPI Mapping – document walkthrough (changes only) 

                                iv.    Friday June 21

1.     
REST-EZ (aka REST Profile for OData)  

2.     
Marketing & Rebranding  

3.      
Infrastructure & tools for producing and consuming OData easier 

 

[‎13.‎06.‎2019 17:06] 

Switched Data Aggregation to Wednesday afternoon

 

[‎13.‎06.‎2019 17:07] 

IANA registration discussion with/after REST Profile discussion

 

[‎13.‎06.‎2019 17:08] 

Move REST Profile to Tuesday afternoon, Temporal to Wednesday morning

 

[‎13.‎06.‎2019 17:11] 

Mark will join Tuesday afternoon via phone

 

[‎13.‎06.‎2019 17:12] 

Use this Skype room for meeting minutes and tracking progress, which will allow anyone to dial in

 

[‎13.‎06.‎2019 17:12] 

1.     
Issues [8:20 am PT]  

1.     
V4.01: NEW
 or OPEN 

                                          i.    ODATA-1310 Let server choose whether to wrap "long" numbers as strings

 

[‎13.‎06.‎2019 17:14] 

A node.js-based server library currently receiving a request with just Accept:application/json can
 only:

·                                
blankly refuse these requests  - not very RESTish 

·                                
answer requests with plain numbers and don't care about rounding issues - the client was unspecific 

·                                
verify each number and completely fail a request if the response would contain at least one loo large number 

·                                
don't use JSON.stringify and build an own JSON serializer - eeek

 

[‎13.‎06.‎2019 17:16] 

ODATA-1310 is OPEN

 

[‎13.‎06.‎2019 17:18] 

Mike: concerned for making things harder for clients - need to be explicit on number representation or else be able to deal with both representations

 

[‎13.‎06.‎2019 17:23] 

Mike: could use string-typed instance annotation with the precise number in addition to the rounded number - not possible for collections of numbers

 

[‎13.‎06.‎2019 17:24] 

Mike: have a similar concept for cell-based authorization: property can be omitted and only instance annotation with Core.Permissions is sent

 

[‎13.‎06.‎2019 17:25] 

Could add a Core(?) instance annotation for that purpose

 

[‎13.‎06.‎2019 17:28] 

LargeInt: 9223372036854776000,

: "9223372036854775807"

 

[‎13.‎06.‎2019 17:33] 

                                          i.    ODATA-1309 JSON Batch: clarify "Textual media types" and their string representation

 

[‎13.‎06.‎2019 17:33] 

Either

·                                            
Use base64url encoding for an explicit list of "textual" media types (including application/json) which can only be extended in future versions of this specification. This list
 is 

·                                                                    
application/json and all sub-types 

·                                                                    
application/xml and all sub-types 

·                                                                    
text/* and all sub-types

Or

·                                
Add an indicator "bodyIsText":true or similar to indicate that the body is not base64url-encoded

 

[‎13.‎06.‎2019 17:37] 

Stream properties:

If the actual stream data is included inline and has the media type application/json or
 one of its subtypes, optionally with format parameters, the stream property value is represented as native JSON. If the stream data is a JSON string, the control information mediaContentType MUST be present
 to indicate that the JSON string already is the actual stream data and not a container for base64url-encoded stream data.[RH1] 

 

 

 [RH1]ODATA-1177

The action couldn’t be completed. Please try again later.

[‎13.‎06.‎2019 17:38] 

Included stream data of other media types is represented as a base64url-encoded string value, see [RFC4648],
 section 5.

The action couldn’t be completed. Please try again later.

[‎13.‎06.‎2019 17:42] 

Check implementations until F2F meeting

The action couldn’t be completed. Please try again later.

[‎13.‎06.‎2019 17:43] 

Simplify JSON Batch format to just allow JSON to be inlined and require all other content-types to be base64-encoded, drop notion of "textual media types"

The action couldn’t be completed. Please try again later.

[‎13.‎06.‎2019 17:44] 

                                          i.    ODATA-1306 Align conformance clauses with normative text

The action couldn’t be completed. Please try again later.

[‎13.‎06.‎2019 17:44] 

The prose text contains MUST requirements for features that are called out as being optional for certain conformance levels, e.g. section 11.1.2 Metadata
 Document Request says that

OData services MUST expose a metadata document [...]

whereas 13.1.1 OData
 4.0 Minimal Conformance Level says

13. SHOULD publish metadata [...]

The action couldn’t be completed. Please try again later.

[‎13.‎06.‎2019 17:45] 

Proposal: 

Make prose text either neutral (use "can" instead of "MUST" etc.) or align with lowest conformance level.

The action couldn’t be completed. Please try again later.

[‎13.‎06.‎2019 17:49]  Mike Pizzo: 

Note: if the service doesn't support $metadata, then contextUrl can't be resolved, but is still useful for describing the shape/structure of the result.

 

[‎13.‎06.‎2019 17:52] 

Service can just implement metadata=none and not send context URL

 

[‎13.‎06.‎2019 17:54] 

ODATA-1306 is OPEN

The action couldn’t be completed. Please try again later.

[‎13.‎06.‎2019 17:57] 

ODATA-1309 is OPEN

 

[‎13.‎06.‎2019 17:57] 

                                          i.    ODATA-1305 Clarify ranges of minute, hour, and second functions

 

[‎13.‎06.‎2019 17:57] 

Proposal: 

Explicitly state the result ranges 0..23 for hour, 0..59 for minute, and 0..60 for second - to allow for leap seconds.

Adapt the example headlines to be less misleading.

 

[‎13.‎06.‎2019 18:01] 

December 31, 2005 23:59:60 UTC 

https://en.wikipedia.org/wiki/Leap_second

 

[‎13.‎06.‎2019 18:05]  Ericson, George: 

Motion to resolve ODATA-1305 as proposed

 

[‎13.‎06.‎2019 18:06]  Borges, Matt: 

I second 

 

[‎13.‎06.‎2019 18:06] 

ODATA-1305 is RESOLVED as proposed

 

[‎13.‎06.‎2019 18:06] 

No Title

                                          i.    ODATA-1299 Continue-on-Error for Collection requests

                                         ii.    ODATA-1296 Allow all non-whitespace characters in a search word, and allow unbalanced
 quotes and parentheses

1.     
https://github.com/oasis-tcs/odata-abnf/pull/18/files 

                                        iii.    ODATA-1113 Allow alternate / native search syntax

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

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

 

[‎13.‎06.‎2019 18:07] 

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

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

 

[‎13.‎06.‎2019 18:07] 

No Title

Things covered by the referenced pull request:

·                                
Upsert: UpdateRestrictions/Upsertable 

·                                
PATCH on collection using delta format - with differentiation "only upsert" and "upsert and delete": UpdateRestrictions/CollectionUpdate 

·                                
PATCH with filter path segment: UpdateRestrictions/CollectionUpdate/FilterSegmentSupported 

·                                
PATCH with typecast segment: UpdateRestrictions/CollectionUpdate/TypecastSegmentSupported 

·                                
DELETE with filter path segment: DeleteRestrictions/FilterSegmentSupported 

·                                
DELETE with typecast segment: DeleteRestrictions/TypecastSegmentSupported 

·                                
POST with type cast segment: InsertRestrictions/TypecastSegmentSupported 

·                                
POST to collections of complex/primitive types: CollectionPropertyRestrictions/Insertable 

·                                
/$filter segment for invoking bound actions/functions: OperationRestrictions/FilterSegmentSupported 

·                                
Operators in, divby: FilterFunctions,
 mention that empty list means "just try" 

·                                
$compute with read: ComputeSupported on
 entity set 

·                                
$expand for stream properties and media resources: ExpandRestrictions/StreamsExpandable 

·                                
headers and query options without prefix, case-insensitive query options: minimum requirement for V4.01: RelaxedSystemQueryOptionNamesSupported 

·                                
/$query segment: QuerySegmentSupported

 

[‎13.‎06.‎2019 18:29]  Mike Pizzo: 

Perhaps defined a new CollectionUpdateRestrictions : UpdateRestrictions that adds only those properties that apply to collections?

 

[‎13.‎06.‎2019 18:38] 

See comments in pull request

 

[‎13.‎06.‎2019 18:44]  Mike Pizzo: 

Combine DeltaUpsertable and DeltaDeletable if we don't need to differentiate the case where a collection supports delete, and supports delta update, but doesn't support deletes through
 delta update.

 

[‎13.‎06.‎2019 18:45] 

                                          i.    ODATA-1113 Allow alternate / native search syntax

The action couldn’t be completed. Please try again later.

[‎13.‎06.‎2019 18:48]  Mike Pizzo: 

George: For 1296, is there any reason that the client library can't close unbalanced qutoes before sending the request?

 

[‎13.‎06.‎2019 18:59] 

Exercise: what is Bing doing with unbalanced quotes

 

[‎13.‎06.‎2019 19:00] 

1.     
Next meetings [9:50 am PT]  

1.     
Tuesday June 18 & Wednesday June 19, 2019 during 9 am to 6 pm PDT (18:00-03:00+1 CEST) 

1.     
Face-to-face pre-meeting, optional 

2.     
Thursday June 20 & Friday June 21, 2019 during 9 am to 5 pm PDT (18:00-02:00+1 CEST) 

                                          i.    Face-to-face meeting, official part

1.      
Thursday June 27, 2019 during 8-10 am PDT (17:00-19:00 CEST) 

 

[‎13.‎06.‎2019 19:00] 

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

 

[‎13.‎06.‎2019 19:00] 

Meeting is adjourned

 

[‎13.‎06.‎2019 19:00] 

See you in Hopkinton

 

 

 

From:  <>
On Behalf Of Handl, Ralf

Sent: Mittwoch, 12. Juni 2019 14:16

To: 

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

 

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

 

Roll call [8:00 am PT]

Self-registration link:

https://www.oasis-open.org/apps/org/workgroup/odata/event.php?event_id=47990 

 

Approve agenda [8:05 am PT]

 

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

Minutes from June 06, 2019 TC meeting:

https://www.oasis-open.org/committees/download.php/65432/Minutes%20of%202019-06-06%20Meeting%20%23260.docx

 

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-06-27

In progress

                                         
i.    #0036

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

 

Face-to-Face Meeting 2019
[8:15 am PT]

Date

                                         
i.    CW 25 2019, June 17-21

                                        
ii.    Pre-Meeting Tuesday June 18 and Wednesday June 19, attendance is optional

                                       
iii.    Face-to-Face-Meeting Thursday June 20 and Friday June 21, counts towards voter eligibility

Location

                                         
i.    228 South Street, Hopkinton, MA 01748…

Proposed agenda

                                  i.    Tuesday June 18

Prepare proposals for all remaining V4.01 issues

IANA registration for headers and preferences – only OData-specific versions as suggested by Mark Nottingham?

Extension for Temporal Data – discuss new approach for preserving service structure

                                 ii.    Wednesday June 19

REST-EZ (aka REST Profile for OData)

Extension for Data Aggregation – Hierarchies

                                iii.    Thursday June 20

Finalize V4.01

Repeatable Requests – document walkthrough

OData-to-OpenAPI Mapping – document walkthrough (changes only)

                                iv.    Friday June 21

REST-EZ (aka REST Profile for OData)

Marketing & Rebranding

Infrastructure & tools for producing and consuming OData easier

 

Issues [8:20 am PT]

V4.01: 
NEW or OPEN

                                         
i.    ODATA-1310 Let server choose whether
 to wrap "long" numbers as strings

                                        
ii.    ODATA-1309 JSON Batch: clarify
 "Textual media types" and their string representation

                                       
iii.    ODATA-1306 Align conformance clauses
 with normative text

                                       
iv.    ODATA-1305 Clarify ranges of minute,
 hour, and second functions

                                        
v.    ODATA-1299 Continue-on-Error for Collection
 requests

                                       
vi.    ODATA-1296 Allow all non-whitespace
 characters in a search word, and allow unbalanced quotes and parentheses

https://github.com/oasis-tcs/odata-abnf/pull/18/files

                                      
vii.    ODATA-1113 Allow alternate / native
 search syntax

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

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

 

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-1304 Improve descriptions on
 Capabilities.NavigationRestrictionsType

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

                                        
ii.    ODATA-1300 Capabilities: add ExpandRestrictions
 to type NavigationPropertyRestriction

https://github.com/oasis-tcs/odata-vocabularies/pull/50/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 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)

 

Next meetings [9:50 am PT]

Tuesday June 18 & Wednesday June 19, 2019 during 9 am to 6 pm PDT (18:00-03:00+1 CEST)

Face-to-face pre-meeting, optional

Thursday June 20 & Friday June 21, 2019 during 9 am to 5 pm PDT (18:00-02:00+1 CEST)

                                         
i.    Face-to-face meeting, official part

Thursday June 27, 2019 during 8-10 am PDT (17:00-19:00 CEST)

 

AOB and wrap up [9:55 am PT]

 

[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/64563/TC%20Timeline%202019-01-23.docx