RE: [odata] Agenda for OData TC meeting on 2017-11-09

Room information was updated by: Stefan Hagen

OASIS Open Data Protocol (OData) TC OData TC Weekly Meeting (Conference Call) #195

- Thursday, 09 November 2017, 08:00am to 10:00am PDT

  - i.e. 2017-11-09 17:00 to 19:00 CEST (UTC+2)

  - other timezone? Try eg.:

  - https://www.timeanddate.com/worldclock/meetingdetails.html?year=2017&month=11&day=9&hour=16&min=0&sec=0&p1=47&p2=69&p3=179

UsefulPlaces:

- Chat:

  - http://webconf.soaphub.org/conf/room/odatatc   # ... this place

- ScreenShare and Voice:

  - https://sap.emea.pgiconnect.com/OData-TC/

Next Planned meetings (tentative):

- Thursday November 02, 2017 during 8-10 am PDT?

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

- Thursday November 09, 2017 during 8-10 am PDT?

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

Agenda-Draft E-Mail URL:

- E-Mail Public URL = "" href="https://lists.oasis-open.org/archives/odata/201711/msg00051.html" target="_blank">https://lists.oasis-open.org/archives/odata/201711/msg00051.html

Minutes Draft Public URL (previous meeting):

- URL = "" href="https://www.oasis-open.org/committees/download.php/61946/odata-meeting-194_on-20171102-minutes.html" target="_blank">https://www.oasis-open.org/committees/download.php/61946/odata-meeting-194_on-20171102-minutes.html

Online document walkthroughs or presentations:

- URL = "" href="https://sap.emea.pgiconnect.com/OData-TC/" target="_blank">https://sap.emea.pgiconnect.com/OData-TC/

Timeline(Updated!):

- URL = "" href="https://www.oasis-open.org/committees/download.php/61677/TC%20Timeline-2017-09-29.docx" target="_blank">https://www.oasis-open.org/committees/download.php/61677/TC%20Timeline-2017-09-29.docx

Agenda Draft (for meeting #195):

==============================================================

1. Roll call [8:00 am PT]

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

2. Approve agenda [8:05 am PT]

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

  3.1 Minutes from November 02, 2017 TC meeting:

      URL = "" href="https://www.oasis-open.org/committees/download.php/61946/odata-meeting-194_on-20171102-minutes.html" target="_blank">https://www.oasis-open.org/committees/download.php/61946/odata-meeting-194_on-20171102-minutes.html

4. Review action items [Action item list: https://www.oasis-open.org/apps/org/workgroup/odata/members/action_items.php] [8:15am PT]

  4.1 Action items due

    4.1.1 #0036 Register the OData- headers and preferences with IANA

      https://www.oasis-open.org/committees/download.php/61752/IANA_Header_Registration.docx

      https://www.oasis-open.org/committees/download.php/61751/IANA_Preference_Registration.docx

5. Issues [8:20 am PT]

  5.1 V4.01 Public Review

      5.1.1 ODATA-1129 Allow deep insert of media resources

      5.1.2 ODATA-1130 JSON Batch and continue-on-error

      5.1.3 ODATA-1131 Consistent order of function parameters

  5.2 V4.01 Next Steps

      5.2.1 Issues ODATA-1126 and ODATA-1129 are new features and will require CSD04 for Part 1: Protocol and Part 2: URL Conventions

                Publish CSD04 before CS01 or schedule issues for CS02 (with CSD04 after CS01)?

      5.2.2 Issues ODATA-1127 and ODATA-1130 are material changes and will require CSD04 for JSON Format

                Publish CSD04 before CS01 or schedule issues for CS02 (with CSD04 after CS01)?

      5.2.3 The CSDL XML and CSDL JSON documents only require non-material changes and may be pushed to CS01 immediately

                Wait for CSD04 review of other documents to finish or publish CS01 immediately?

  5.3 Vocabularies: APPLIED

      5.3.1 ODATA-1064 Add ability to annotate collections to return only count and NextLink

  5.4 Vocabularies: NEW or OPEN

      5.4.1 ODATA-1124 Authorization vocabulary: KeyLocation - also allow cookie as value?

      5.4.2 ODATA-1121 Extend FilterExpressionRestrictions with "MultiPredicate"

      5.4.3 ODATA-1067 Consider ability to define computed default values

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

      5.4.5 ODATA-884 Add term ErrorCodes to describe possible codes in error messages (public comment c201510e00019)

6. Committee Note on Google Protocol Buffers as an alternative data format [9:30 am PT]

   George: describe use case and purpose of the proposed committee note

7. Structural Property with Type=Entity Type versus Containment Navigation Property [9:40 am PT]

   George: describe use case and why containment navigation properties arent sufficient

8. Next meetings [9:50 am PT]

   Thursday November 16, 2017 during 8-10 am PST

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

==============================================================

Meeting Member URL:

- URL = "" href="https://www.oasis-open.org/apps/org/workgroup/odata/event.php?event_id=44003" target="_blank">https://www.oasis-open.org/apps/org/workgroup/odata/event.php?event_id=44003

  - Please use starting approx. 15 minutes before the meeting for self registration. Thanks.

  - Self registration deep link (as a service):

    - https://www.oasis-open.org/apps/org/workgroup/odata/record_my_attendance.php?event_id=44003&confirmed=1

Stefan Hagen: KeepAlive

Stefan Hagen: KeepAlive

Stefan Hagen: KeepAlive

Stefan1: KeepAlive

Stefan Hagen: H4Q::Voting Members: 1 of 12 (8%) (used for quorum calculation) - 6 voting members missing for quorum ...

Stefan Hagen: H4Q::Voting Members: 1 of 12 (8%) (used for quorum calculation) - 6 voting members missing for quorum ...

Please change your name from 'anonymous' using the Settings button

Room Information:

OASIS Open Data Protocol (OData) TC OData TC Weekly Meeting (Conference Call) #195

- Thursday, 09 November 2017, 08:00am to 10:00am PDT

  - i.e. 2017-11-09 17:00 to 19:00 CEST (UTC+2)

  - other timezone? Try eg.:

  - https://www.timeanddate.com/worldclock/meetingdetails.html?year=2017&month=11&day=9&hour=16&min=0&sec=0&p1=47&p2=69&p3=179

UsefulPlaces:

- Chat:

  - http://webconf.soaphub.org/conf/room/odatatc   # ... this place

- ScreenShare and Voice:

  - https://sap.emea.pgiconnect.com/OData-TC/

Next Planned meetings (tentative):

- Thursday November 02, 2017 during 8-10 am PDT?

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

- Thursday November 09, 2017 during 8-10 am PDT?

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

Agenda-Draft E-Mail URL:

- E-Mail Public URL = "" href="https://lists.oasis-open.org/archives/odata/201711/msg00051.html" target="_blank">https://lists.oasis-open.org/archives/odata/201711/msg00051.html

Minutes Draft Public URL (previous meeting):

- URL = "" href="https://www.oasis-open.org/committees/download.php/61946/odata-meeting-194_on-20171102-minutes.html" target="_blank">https://www.oasis-open.org/committees/download.php/61946/odata-meeting-194_on-20171102-minutes.html

Online document walkthroughs or presentations:

- URL = "" href="https://sap.emea.pgiconnect.com/OData-TC/" target="_blank">https://sap.emea.pgiconnect.com/OData-TC/

Timeline(Updated!):

- URL = "" href="https://www.oasis-open.org/committees/download.php/61677/TC%20Timeline-2017-09-29.docx" target="_blank">https://www.oasis-open.org/committees/download.php/61677/TC%20Timeline-2017-09-29.docx

Agenda Draft (for meeting #195):

==============================================================

1. Roll call [8:00 am PT]

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

2. Approve agenda [8:05 am PT]

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

  3.1 Minutes from November 02, 2017 TC meeting:

      URL = "" href="https://www.oasis-open.org/committees/download.php/61946/odata-meeting-194_on-20171102-minutes.html" target="_blank">https://www.oasis-open.org/committees/download.php/61946/odata-meeting-194_on-20171102-minutes.html

4. Review action items [Action item list: https://www.oasis-open.org/apps/org/workgroup/odata/members/action_items.php] [8:15am PT]

  4.1 Action items due

    4.1.1 #0036 Register the OData- headers and preferences with IANA

      https://www.oasis-open.org/committees/download.php/61752/IANA_Header_Registration.docx

      https://www.oasis-open.org/committees/download.php/61751/IANA_Preference_Registration.docx

5. Issues [8:20 am PT]

  5.1 V4.01 Public Review

      5.1.1 ODATA-1129 Allow deep insert of media resources

      5.1.2 ODATA-1130 JSON Batch and continue-on-error

      5.1.3 ODATA-1131 Consistent order of function parameters

  5.2 V4.01 Next Steps

      5.2.1 Issues ODATA-1126 and ODATA-1129 are new features and will require CSD04 for Part 1: Protocol and Part 2: URL Conventions

                Publish CSD04 before CS01 or schedule issues for CS02 (with CSD04 after CS01)?

      5.2.2 Issues ODATA-1127 and ODATA-1130 are material changes and will require CSD04 for JSON Format

                Publish CSD04 before CS01 or schedule issues for CS02 (with CSD04 after CS01)?

      5.2.3 The CSDL XML and CSDL JSON documents only require non-material changes and may be pushed to CS01 immediately

                Wait for CSD04 review of other documents to finish or publish CS01 immediately?

  5.3 Vocabularies: APPLIED

      5.3.1 ODATA-1064 Add ability to annotate collections to return only count and NextLink

  5.4 Vocabularies: NEW or OPEN

      5.4.1 ODATA-1124 Authorization vocabulary: KeyLocation - also allow cookie as value?

      5.4.2 ODATA-1121 Extend FilterExpressionRestrictions with "MultiPredicate"

      5.4.3 ODATA-1067 Consider ability to define computed default values

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

      5.4.5 ODATA-884 Add term ErrorCodes to describe possible codes in error messages (public comment c201510e00019)

6. Committee Note on Google Protocol Buffers as an alternative data format [9:30 am PT]

   George: describe use case and purpose of the proposed committee note

7. Structural Property with Type=Entity Type versus Containment Navigation Property [9:40 am PT]

   George: describe use case and why containment navigation properties arent sufficient

8. Next meetings [9:50 am PT]

   Thursday November 16, 2017 during 8-10 am PST

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

==============================================================

Meeting Member URL:

- URL = "" href="https://www.oasis-open.org/apps/org/workgroup/odata/event.php?event_id=44003" target="_blank">https://www.oasis-open.org/apps/org/workgroup/odata/event.php?event_id=44003

  - Please use starting approx. 15 minutes before the meeting for self registration. Thanks.

  - Self registration deep link (as a service):

    - https://www.oasis-open.org/apps/org/workgroup/odata/record_my_attendance.php?event_id=44003&confirmed=1

[17:01] anonymous morphed into Ralf Handl (SAP SE)

[17:01] Stefan Hagen: H4Q::Voting Members: 5 of 12 (41%) (used for quorum calculation)  - 2 voting members until quorum reached ...

[17:02] Stefan Hagen: H4Q::Voting Members: 7 of 12 (58%) (used for quorum calculation)  - quorate

[17:03] Stefan Hagen: H4Q::Voting Members: 9 of 12 (75%) (used for quorum calculation)

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

[17:06] Ralf Handl (SAP SE): Mike: walk through already applied issues in V4.01 documents

[17:06] Ralf Handl (SAP SE): Hubert: discrepancy between CSDL XML and JSON

[17:07] Ralf Handl (SAP SE): Agenda approved with these changes

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

a.Minutes from November 02, 2017 TC meeting: https://www.oasis-open.org/committees/download.php/61946/odata-meeting-194_on-20171102-minutes.html

[17:08] Ralf Handl (SAP SE): Mike: appreciate Stefan's work

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

[17:09] Ralf Handl (SAP SE): 4.Review action items [Action item list: https://www.oasis-open.org/apps/org/workgroup/odata/members/action_items.php] [8:15am PT]

a.Action items due

i.none

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

a.V4.01 Public Review

[17:09] Ralf Handl (SAP SE): i.ODATA-1129 Allow deep insert of media resources

[17:11] Ralf Handl (SAP SE): ODATA-1129 is OPEN

[17:11] Hubert Heijkers (IBM): I move to resolve ODATA-1129 as proposed

[17:11] Michael Pizzo: I second

[17:11] Ralf Handl (SAP SE): ODATA-1129 is RESOLVED as proposed

[17:11] Ralf Handl (SAP SE): ii.ODATA-1130 JSON Batch and continue-on-error

[17:18] Michael Pizzo: In the multipartmixed format, with continue-on-error false, each statement outside of a changeset is implicitly dependent upon the statement (or changeset) before it.

[17:19] Michael Pizzo: currently, continue-on-error defaults to false.

[17:23] Michael Pizzo: continue-on-error false may still be useful in json batch for non-dependent statements that are allowed to run in parallel but whose result is uninteresting if incomplete.

[17:25] Ralf Handl (SAP SE): Current text seems to imply that processing MUST stop if no continue-on-error is specified

[17:25] Ralf Handl (SAP SE): "Processing stops on the first error unless the continue-on-error preference is specified."

[17:25] Michael Pizzo: service *must* be able to continue on error for the JSON batch format if it is processing statements in parallel.

[17:26] Michael Pizzo: otherwise, continue-on-error false would mean can't run in parallel.

[17:26] Ralf Handl (SAP SE): Rephrase to "MAY stop"

[17:27] Ralf Handl (SAP SE): Currently clients can't say "continue-on-error=false"

[17:31] Ralf Handl (SAP SE): Mike: continue-on-error=false is not the correct/expected default for JSON Batch

[17:38] Michael Pizzo: We want it to default to false for multipart/mixed (current behavior) and to default to true for JSON Batch.

[17:39] Michael Pizzo: We could make current definition dependent on whether or not the format has a way to explicitly declare dependencies outside of an atomicity group.

[17:40] Michael Pizzo: Alternatively, just say it only applies to multipart mixed.  Not as format-independent, but certainly clearer.

[17:41] Ralf Handl (SAP SE): ODATA-1130 is OPEN

[17:41] Michael Pizzo: We still don't have a way, in the JSON format, to say that I am okay running in parallel but I don't care about results if there are any errors, but that we could add later if necessary.

[17:44] Michael Pizzo: We could later add "continue-on-error=false".

[17:45] Michael Pizzo: We could also do it now, and say that continue-on-error defaults to false for multipart mixed, and continue-on-error defaults to true for json.

[17:48] Michael Pizzo: allow "continue-on-error=false" and "continue-on-error=true".  "continue-on-error" implies true.  If continue-on-error is not specified, then default is false in multipart mixed, true in json. In multipartmixed, continue-on-error=false means stop if any statement fails. In json it means that a best effort is requested not to spend cycles on further processing if a failure occurs outside of dependency groups because the client is not interested in the result.

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

[17:49] Michael Pizzo: I second

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

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

[17:50] Ralf Handl (SAP SE): iii.ODATA-1131 Consistent order of function parameters

[17:52] Ralf Handl (SAP SE): ODATA-1131 is OPEN

[17:53] Ralf Handl (SAP SE): Mike: problem even more pressing with the addition of optional parameters

[17:53] Ralf Handl (SAP SE): Mike: expectation of current protocol that isn't yet explicitly stated

[17:58] Michael Pizzo: For functions, ordering is required. For actions, it only matters for the binding parameter, but should we say that the ordering is stable for all parameters for simplicity/consistency/future extensibility?

[18:08] Michael Pizzo: Clarify that the defined order of parameters for functions or actions, as described in the metadata document, is stable over time.

[18:10] Michael Pizzo: I proposed we Clarify that the defined order of parameters for functions or actions, as described in the metadata document, is stable over time.

[18:11] Hubert Heijkers (IBM): I move to resolve ODATA-1131 as per Mike's proposal

[18:11] Mark Biamonte (Progress): I second

[18:12] Ralf Handl (SAP SE): ODATA-1131 is RESOLVED as proposed

[18:12] Ralf Handl (SAP SE): Hubert: should be mentioned in Protocol section on Model Versioning

[18:13] Ralf Handl (SAP SE): And in both CSDL documents

[18:19] Ralf Handl (SAP SE): b.V4.01 Next Steps

i.Issues ODATA-1126 and ODATA-1129 are new features and will require CSD04 for Part 1: Protocol and Part 2: URL Conventions

1.Publish CSD04 before CS01 or schedule issues for CS02 (with CSD04 after CS01)?

ii.Issues ODATA-1127 and ODATA-1130 are material changes and will require CSD04 for JSON Format

1.Publish CSD04 before CS01 or schedule issues for CS02 (with CSD04 after CS01)?

iii.The CSDL XML and CSDL JSON documents only require non-material changes and may be pushed to CS01 immediately

1.Wait for CSD04 review of other documents to finish or publish CS01 immediately?

[18:21] Ralf Handl (SAP SE): Mike: take the time for another public review

[18:22] Ralf Handl (SAP SE): Mike: we only have to react to public review comments on the changes wrt the current CSD versions

[18:22] Ralf Handl (SAP SE): Hubert: sounds like the logical thing to do

[18:23] Ralf Handl (SAP SE): Mark: fine with another review

[18:23] Ralf Handl (SAP SE): George: is shortest path to "final" CS

[18:25] Ralf Handl (SAP SE): Plan: progress documents next week

[18:25] Ralf Handl (SAP SE): Mike to walk us through the changes applied so far

[18:59] Mark Biamonte (Progress): I move that OData-1122, OData-1125, OData-1126, OData-1127 and OData-1128 be accepted as applied

[18:59] Hubert Heijkers (IBM): I second

[19:00] Ralf Handl (SAP SE): Motion passes

[19:01] Ralf Handl (SAP SE): 8.Next meetings [9:50 am PT]

a.Thursday November 16, 2017 during 8-10 am PST

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

[19:01] Ralf Handl (SAP SE): Meeting is adjourned

From: odata@lists.oasis-open.org [mailto:odata@lists.oasis-open.org] On Behalf Of Handl, Ralf
Sent: Donnerstag, 9. November 2017 11:40
To: odata@lists.oasis-open.org
Subject: RE: [odata] Agenda for OData TC meeting on 2017-11-09

New issue 5.a.iii ODATA-1131 Consistent order of function parameters

From: odata@lists.oasis-open.org [mailto:odata@lists.oasis-open.org] On Behalf Of Handl, Ralf
Sent: Dienstag, 7. November 2017 17:02
To: odata@lists.oasis-open.org
Subject: RE: [odata] Agenda for OData TC meeting on 2017-11-09

New issue 5.a.ii ODATA-1130 JSON Batch and continue-on-error

From: odata@lists.oasis-open.org [mailto:odata@lists.oasis-open.org] On Behalf Of Handl, Ralf
Sent: Dienstag, 7. November 2017 13:39
To: odata@lists.oasis-open.org
Subject: [odata] Agenda for OData TC meeting on 2017-11-09

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

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

2. Approve agenda [8:05 am PT]

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

Minutes from November 02, 2017 TC meeting: https://www.oasis-open.org/committees/download.php/61946/odata-meeting-194_on-20171102-minutes.html

4. Review action items [Action item list: https://www.oasis-open.org/apps/org/workgroup/odata/members/action_items.php] [8:15am PT]

Action items due

i. none

5. Issues [8:20 am PT]

V4.01 Public Review

i. ODATA-1129 Allow deep insert of media resources

ii. ODATA-1130 JSON Batch and continue-on-error

iii. ODATA-1131 Consistent order of function parameters

V4.01 Next Steps

i. Issues ODATA-1126 and ODATA-1129 are new features and will require CSD04 for Part 1: Protocol and Part 2: URL Conventions

Publish CSD04 before CS01 or schedule issues for CS02 (with CSD04 after CS01)?

ii. Issues ODATA-1127 and ODATA-1130 are material changes and will require CSD04 for JSON Format

Publish CSD04 before CS01 or schedule issues for CS02 (with CSD04 after CS01)?

iii. The CSDL XML and CSDL JSON documents only require non-material changes and may be pushed to CS01 immediately

Wait for CSD04 review of other documents to finish or publish CS01 immediately?

Vocabularies: APPLIED

i. ODATA-1064 Add ability to annotate collections to return only count and NextLink

Vocabularies: NEW or OPEN

i. ODATA-1124 Authorization vocabulary: KeyLocation - also allow cookie as value?

ii. ODATA-1121 Extend FilterExpressionRestrictions with "MultiPredicate"

iii. ODATA-1067 Consider ability to define computed default values

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

v. ODATA-884 Add term ErrorCodes to describe possible codes in error messages (public comment c201510e00019)

6. Committee Note on Google Protocol Buffers as an alternative data format [9:30 am PT]

George: describe use case and purpose of the proposed committee note

7. Structural Property with Type=Entity Type versus Containment Navigation Property [9:40 am PT]

George: describe use case and why containment navigation properties aren’t sufficient

8. Next meetings [9:50 am PT]

Thursday November 16, 2017 during 8-10 am PST

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

[2] References

Chat room: http://webconf.soaphub.org/conf/room/odatatc
Conference call & Screen sharing: https://sap.emea.pgiconnect.com/OData-TC
Conference call details: https://www.oasis-open.org/apps/org/workgroup/odata/download.php/56760/TC%20meeting%20dial-in%20details.htm

[3] Timeline

https://www.oasis-open.org/committees/download.php/61677/TC%20Timeline-2017-09-29.docx

odata message