RE: Agenda for OData TC meeting on 2019-12-05

[‎05.‎12.‎2019 17:02]

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

[‎05.‎12.‎2019 17:05]

Voting Members: 5 of 8 (62%) (used for quorum calculation)

[‎05.‎12.‎2019 17:05]

Achieved quorum: yes

[‎05.‎12.‎2019 17:08]

Voting Members: 7 of 9 (77%) (used for quorum calculation)

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

2. Approve agenda [8:05 am]

[‎05.‎12.‎2019 17:10]

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

a. Minutes from November 21, 2019 TC meeting: https://www.oasis-open.org/committees/download.php/66276/Minutes%20of%202019-11-21%20Meeting%20%23276.docx

[‎05.‎12.‎2019 17:10]

Minutes are approved

[‎05.‎12.‎2019 17:12]

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 – 2020-01-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

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

iii: no response yet from Chet Ensign

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

5. Issues [8:20 am]

a. V4.01: NEW or OPEN

i. ODATA-1345 Issues with ContextUrl

[‎05.‎12.‎2019 17:26] Mike Pizzo:

The OData syntax rules for URLs are defined in this document and the [OData-ABNF]. Note that the ABNF is not expressive enough to define what a correct OData URL is in every imaginable use case. This specification document defines additional rules that a correct OData URL MUST fulfill. In case of doubt on what makes an OData URL correct the rules defined in this specification document take precedence.

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.

[‎05.‎12.‎2019 17:42]

ODATA-1345 is OPEN

This message wasn't sent to Ericson, George.

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.

[‎05.‎12.‎2019 17:53]

Current text:
- For a 4.0 response, the expanded navigation property suffixed with parentheses MAY be omitted from the select-list if it does not contain a nested $select or $expand, but MUST still be present, without a suffix, if it is explicitly selected.

[‎05.‎12.‎2019 17:54]

New text:
- For a 4.0 response, the expanded navigation property suffixed with parentheses is omitted from the select-list if it does not contain a nested $select or $expand, but MUST still be present, without a suffix, if it is explicitly selected.

[‎05.‎12.‎2019 17:59]

ii. ODATA-1344 Remove leftover wording regarding $expand within $select

[‎05.‎12.‎2019 18:00] Ericson, George:

NMote: Update proposal and deferring for process check.

[‎05.‎12.‎2019 18:07]

ODATA-1344 is OPEN

This message wasn't sent to Ericson, George.

[‎05.‎12.‎2019 18:08] Mike Pizzo:

I move to resolve ODATA-1344 as proposed, and apply it as a non-normative change in our next publication opportunity of the specification

[‎05.‎12.‎2019 18:08] Mike Pizzo:

(next opportunity to publish should be as a non-normative change between candidate OASIS Specification and OASIS Specification)

[‎05.‎12.‎2019 18:08] Borges, Matt:

I second

[‎05.‎12.‎2019 18:09]

ODATA-1344 is RESOLVED as proposed

[‎05.‎12.‎2019 18:12]

iii. ODATA-1343 Multipart Batch Request Body example is missing required CRLF before first occurrence of boundary

[‎05.‎12.‎2019 18:13]

Correct:
--batch_36522ad7-fc75-4b56-8c71-56071383e77b
Content-Type: application/http

GET /service/Customers('ALFKI')
Host: host

--batch_36522ad7-fc75-4b56-8c71-56071383e77b

[‎05.‎12.‎2019 18:16]

ODATA-1343 is OPEN

[‎05.‎12.‎2019 18:19] Mike Pizzo:

I move to resolve ODATA-1343 as proposed.

[‎05.‎12.‎2019 18:19] Ericson, George:

I Second

[‎05.‎12.‎2019 18:19]

ODATA-1343 is RESOLVED as proposed

[‎05.‎12.‎2019 18:20]

6. Progress V4.01 to Candidate OASIS Standard [9:20 am]

a. Accept Statements of Use

i. Sample motions:

[‎05.‎12.‎2019 18:22]

1. I move to accept the Statements of Use for OData V4.01 Committee Specification 02 approved on 15 November 2013 provided by SAP and Microsoft.

[‎05.‎12.‎2019 18:23]

2. I move to accept the Statements of Use for OData JSON Format V4.01 Committee Specification 02 approved on 15 November 2013 provided by SAP and Microsoft.

3. I move to accept the Statements of Use for OData Common Schema Definition Language (CSDL) JSON Representation V4.01 Committee Specification 02 approved on 15 November 2013 provided by SAP and Microsoft.

4. I move to accept the Statements of Use for OData Common Schema Definition Language (CSDL) XML Representation V4.01 Committee Specification 02 approved on 15 November 2013 provided by SAP and Microsoft.

[‎05.‎12.‎2019 18:25]

No Title

SAP's statement of use:
SAP successfully uses Committee Specification 02 of the OData version 4.01 specifications approved on 15 November 2019 in accordance with the required clauses for minimal conformance of read-only services specified in chapter 13.1.1 of Part 1. This use does not include interoperation with other independent implementations.

SAP successfully uses Committee Specification 02 of the OData JSON Format version 4.01 specification approved on 15 November 2019. This use does not include interoperation with other independent implementations.

SAP successfully uses Committee Specification 02 of the OData CSDL JSON version 4.01 specification approved on 15 November 2019 in accordance with the conformance clauses specified in chapter 17. This use does not include interoperation with other independent implementations.

SAP successfully uses Committee Specification 02 of the OData CSDL XML version 4.01 specification approved on 15 November 2019 in accordance with the conformance clauses specified in chapter 17. This use does not include interoperation with other independent implementations.

[‎05.‎12.‎2019 18:26]

https://www.oasis-open.org/apps/org/workgroup/odata/email/archives/201911/msg00044.html

[‎05.‎12.‎2019 18:27]

Microsoft's statement of use

[‎05.‎12.‎2019 18:27]

No Title

Microsoft has successfully implemented the Committee Specification 02 (approved November 15, 2019) version of the OASIS OData Protocol Version 4.01 specification in our OData core and service libraries for the .NET framework, and used those libraries in production as well as demonstration services.

The libraries enable developers to write OData clients in accordance with the required clauses for Interoperable OData clients as specified in Section 13.3, as well as OData Read-only or Updatable Data Services in accordance with the required clauses for Intermediate Conformance as specified in Section 13.2.2, of Part 1: Protocol and Section 6 of Part 2: URL Conventions, and in accordance with the conformance clauses for services specified in Section 17 of OData CSDL XML version 4.01 specification also approved November 15, 2019. Additionally, we have an internal implementation that generates JSON CSDL in accordance with the conformance clauses for services specified in Section 17 of OData CSDL JSON version 4.01 specification approved November 15, 2019.

These libraries support the Committee Specification 02 (approved November 15, 2019) version of the OData JSON Format version 4.01 specification in accordance with the conformance clauses specified in Section 24 for both a consumer and producer of the OData JSON format.

[‎05.‎12.‎2019 18:29] Mike Pizzo:

I move to accept the Statements of Use for OData V4.01 Committee Specification 02 approved on 15 November 2013 provided by SAP and Microsoft.

[‎05.‎12.‎2019 18:29] Borges, Matt:

I second

[‎05.‎12.‎2019 18:30]

No objections, motion passes

[‎05.‎12.‎2019 18:30] Mike Pizzo:

I move to accept the Statements of Use for OData JSON Format V4.01 Committee Specification 02 approved on 15 November 2013 provided by SAP and Microsoft.

[‎05.‎12.‎2019 18:31] Mike Pizzo:

motion withdrawn

[‎05.‎12.‎2019 18:32] Mike Pizzo:

I move to accept the Statements of Use for OData V4.01 Committee Specification 02 approved on 15 November 2019 provided by SAP and Microsoft.

[‎05.‎12.‎2019 18:32] Mark Biamonte:

I second

[‎05.‎12.‎2019 18:32] Borges, Matt:

I second

[‎05.‎12.‎2019 18:33]

No objections, motion passes

[‎05.‎12.‎2019 18:33] Mike Pizzo:

I move to accept the Statements of Use for OData JSON Format V4.01 Committee Specification 02 approved on 15 November 2019 provided by SAP and Microsoft.

[‎05.‎12.‎2019 18:33] Mark Biamonte:

I second

[‎05.‎12.‎2019 18:33]

No objections, motion passes

[‎05.‎12.‎2019 18:33] Mike Pizzo:

I move to accept the Statements of Use for OData Common Schema Definition Language (CSDL) JSON Representation V4.01 Committee Specification 02 approved on 15 November 2019 provided by SAP and Microsoft.

[‎05.‎12.‎2019 18:34] Ericson, George:

I Second

[‎05.‎12.‎2019 18:34]

No objections, motion passes

[‎05.‎12.‎2019 18:34] Mike Pizzo:

I move to accept the Statements of Use for OData Common Schema Definition Language (CSDL) XML Representation V4.01 Committee Specification 02 approved on 15 November 2019 provided by SAP and Microsoft.

[‎05.‎12.‎2019 18:34] Borges, Matt:

I second

[‎05.‎12.‎2019 18:34]

No objections, motion passes

[‎05.‎12.‎2019 18:36]

7. More Issues [9:40 am]

[‎05.‎12.‎2019 18:36]

a. V4.02: NEW or OPEN with concrete proposal

[‎05.‎12.‎2019 18:36]

ODATA-1341

Clarify that nested next links can appear on the same page as a delta link

[‎05.‎12.‎2019 18:52]

1. ODATA-1341

[‎05.‎12.‎2019 18:53] Borges, Matt:

Clarify that each page of results within a response can have either a next link or a delta link but not both.

[‎05.‎12.‎2019 18:59] Mike Pizzo:

Conceptually: Clarify that each page of results within a response can have either a nextlink or a deltalink but not both. Probably best to avoid the use of the word "page" as it is ambiguous.

Also clarify that following next links within a delta typically don't result in a delta at the end-the delta is tracked by the top level response. Clients MAY request the delta link when requesting the nested content and, since it's a preference, the service MAY ignore it.

[‎05.‎12.‎2019 18:59] Mike Pizzo:

(second sentence is for *nested* next links...)

[‎05.‎12.‎2019 19:02] Mike Pizzo:

Something like: The delta payload, and each nested collection within the delta payload, may be paged. The delta link appears on the last page of each collection.

[‎05.‎12.‎2019 19:03] Mike Pizzo:

Modified proposal:
Clarify that each page of results within a response can have either a nextlink or a deltalink but not both. Probably best to avoid the use of the word "page" as it is ambiguous. Maybe something like "The delta payload, and each nested collection within the delta payload, may be paged. The delta link appears on the last page of each collection in place of the nextlink."
Also clarify that following nested next links within a delta payload typically doesn't result in a delta at the end-the delta is tracked by the top level response. Clients MAY request the delta link when requesting the nested content and, since it's a preference, the service MAY ignore it.

[‎05.‎12.‎2019 19:04] Borges, Matt:

I move to resolve ODATA-1341 with the modified proposal

[‎05.‎12.‎2019 19:04] Mike Pizzo:

I second

[‎05.‎12.‎2019 19:04]

ODATA-1341 is RESOLVED as proposed

[‎05.‎12.‎2019 19:04] Mike Pizzo:

We believe this to be a non-normative clarification.

[‎05.‎12.‎2019 19:05]

8. Next meetings [9:50 am]

a. Thursday December 12, 2019 during 8-10 am PST (17:00-19:00 CET)

b. Thursday December 19, 2019 during 8-10 am PST (17:00-19:00 CET)

c. Thursday January 16, 2020 during 8-10 am PST (17:00-19:00 CET)

[‎05.‎12.‎2019 19:06]

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

[‎05.‎12.‎2019 19:06]

Meeting is adjourned

From: odata@lists.oasis-open.org <odata@lists.oasis-open.org>On Behalf Of Handl, Ralf
Sent: Donnerstag, 5. Dezember 2019 14:14
To: odata@lists.oasis-open.org
Subject: [CAUTION] [odata] Agenda for OData TC meeting on 2019-12-05

Here [1] is a draft agenda for the OData TC (Technical Committee) meetingscheduled onThursday December 05, 2019 during 8-10 am PST (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]

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

2. Approve agenda [8:05 am]

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

a. Minutes from November 21, 2019 TC meeting:https://www.oasis-open.org/committees/download.php/66276/Minutes%20of%202019-11-21%20Meeting%20%23276.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 – 2020-01-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. Issues [8:20 am]

a. V4.01:NEW or OPEN

i. ODATA-1345 Issues with ContextUrl

ii. ODATA-1344 Remove leftover wording regarding $expand within $select

iii. ODATA-1343 Multipart Batch Request Body example is missing required CRLF before first occurrence of boundary

6. Progress V4.01 to Candidate OASIS Standard [9:20 am]

a. Accept Statements of Use

i. Sample motions:

1. I move to accept the Statements of Use for OData V4.01 Committee Specification 02 approved on 15 November 2013 provided bySAP, IBM, and Microsoft.

2. I move to accept the Statements of Use for OData JSON Format V4.01 Committee Specification 02 approved on 15 November 2013 provided bySAP, IBM, and Microsoft.

b. Request special majority ballots to approve Candidate OASIS Standard 01

i. Sample motions:

1. I move to approve the Chair requesting that TC Administration hold a Special Majority Vote to approve submitting OData V4.01 Committee Specification 02 as a Candidate OASIS Standard.

2. I move to approve the Chair requesting that TC Administration hold a Special Majority Vote to approve submitting OData JSON Format V4.01 Committee Specification 02 as a Candidate OASIS Standard.

3. I move to approve the Chair requesting that TC Administration hold a Special Majority Vote to approve submitting OData Common Schema Definition Language (CSDL) JSON Representation V4.01 Committee Specification 02 as a Candidate OASIS Standard.

4. I move to approve the Chair requesting that TC Administration hold a Special Majority Vote to approve submitting OData Common Schema Definition Language (CSDL) XML Representation V4.01 Committee Specification 02 as a Candidate OASIS Standard.

7. More Issues [9:40 am]

a. V4.02:NEW or OPEN with concrete proposal

i. ODATA-1340 PATCH: new preference return=delta to get back a delta response

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

b. Vocabularies:NEW or OPEN with concrete proposal

i. ODATA-1342 Core.Ordered: mention "Term" in AppliesTo

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

ii. ODATA-1275 Describe structure of "JSON properties"

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

2. https://github.com/oasis-tcs/odata-csdl-schemas/pull/9/files

8. Next meetings [9:50 am]

a. Thursday December 12, 2019 during 8-10 am PST (17:00-19:00 CET)