RE: [odata] Agenda for OData TC meeting on 2018-03-08

[16:39] Room information was updated by: Stefan Hagen

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

- Thursday, 08 March 2018, 08:00am to 10:00am PST

   - i.e. 2018-03-08 17:00 to 19:00 CET (UTC+1)

   - other timezone? Try eg.:

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

TimezoneInterferences:

- In North America, daylight savings time begins on March 11th. (Ends November 4th if you want to be proactive.)

- In Europe (by and large), daylight savings time begins two weeks later on March 25th.

- Note as always that different locales do this differently.

  - (For example, Mexico starts on April 1st.) So folks may want to check to be sure.

UsefulPlaces:

- Chat:

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

- ScreenShare and Voice:

   - https://lync.co.sap.com/meet/ralf.handl/82RDM4K6

     - Conference ID: 50209199

Next Planned meetings (tentative):

- Thursday March 15, 2018 during 8-10 am PDT (16:00-18:00 CET)  Daylight Saving Time in North America

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

- Thursday March 22, 2018 during 8-10 am PDT (16:00-18:00 CET) - Daylight Saving Time in North America

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

Agenda-Draft E-Mail URL:

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

Minutes Draft Public URL (previous meeting):

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

Online document walkthroughs or presentations:

- URL = "" href="https://lync.co.sap.com/meet/ralf.handl/82RDM4K6" target="_blank">https://lync.co.sap.com/meet/ralf.handl/82RDM4K6

  - Conference ID: 50209199

- Fallbacks:

  - old Conference call & Screen sharing: https://sap.emea.pgiconnect.com/OData-TC

  - old Conference call details: https://www.oasis-open.org/apps/org/workgroup/odata/download.php/56760/TC%20meeting%20dial-in%20details.htm

Timeline(Updated!):

- URL = "" href="https://www.oasis-open.org/committees/download.php/62637/TC%20Timeline-2018-03-02.docx" target="_blank">https://www.oasis-open.org/committees/download.php/62637/TC%20Timeline-2018-03-02.docx

Agenda Draft (for meeting #206):

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

1. Roll call [8:00 am PT]

  1.1 Self-registration link:

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

2. Approve agenda [8:05 am PT]

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

  3.1 Minutes from March 01, 2018 TC meeting:

  URL = "" href="https://www.oasis-open.org/committees/download.php/62633/odata-meeting-205_on-20180301-minutes.html" target="_blank">https://www.oasis-open.org/committees/download.php/62633/odata-meeting-205_on-20180301-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 none

5. Infos from TC Admin (Chet Ensign)

  5.1 Vocabularies and V4.0 Errata 04

    5.1.1 We can change the vocabulary references in the specification documents to the GitHub vocabularies

    5.1.2 We should in addition pack the most recent copy of the GitHub vocabularies into the Errata zip, so they are published at the usual location

    5.1.3 This is not a problem because the GitHub vocabularies contain latest-version links that point to GitHub

  5.2 Jira Issue Notifications

    5.2.1 Currently the TC Jira sends notifications to the TC mailing list for every change of an issue

          Created, Updated, Resolved, Closed, Commented, Comment Edited, Comment Deleted, Reopened, Deleted

    5.2.2 Now a terse notification scheme is available, reduced to

          Created, Resolved

    5.2.3 Do we want to switch to terse? Watchers of an issue will still receive notifications of any change to the watched issue

6. Timeline

  6.1 Updated timeline, see [3]:

      URL = "" href="https://www.oasis-open.org/committees/download.php/62637/TC%20Timeline-2018-03-02.docx" target="_blank">https://www.oasis-open.org/committees/download.php/62637/TC%20Timeline-2018-03-02.docx

7. Issues [8:20 am PT]

  7.1 APPLIED

    7.1.1 ODATA-1155 ABNF: allow omitting default namespaces everywhere in the URL

  7.2 Vocabularies: NEW or OPEN with concrete proposal

    7.2.1 ODATA-1072 Annotation to describe supported aggregation methods

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

  7.3 Vocabularies: NEW or OPEN that need more discussion  triage

    7.3.1 ODATA-1099 Add annotations to describe custom query options and custom headers

    7.3.2 ODATA-1067 Consider ability to define computed default values

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

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

  7.4 V4.01: NEW or OPEN

    7.4.1 ODATA-1156 Context URL: allow empty parentheses after navigation property

    7.4.2 ODATA-1154 Clarify which OData-Version a service should return

    7.4.3 ODATA-1151 Edm.Stream and Nullable

    7.4.4 ODATA-1149 Support Delta responses for Singletons

    7.4.5 ODATA-1148 PATCH with nested nav props should not remove omitted resources

    7.4.6 ODATA-1141 Upsert: clarify upsert along nullable single-valued navigation path

8. Next meetings [9:50 am PT]

  8.1 Thursday March 15, 2018 during 8-10 am PDT (16:00-18:00 CET)  Daylight Saving Time in North America

  8.2 Thursday March 22, 2018 during 8-10 am PDT (16:00-18:00 CET)  Daylight Saving Time in North America

  8.3 Thursday March 29, 2018 during 8-10 am PDT (17:00-19:00 CEST)  back to normal time difference, Easter is coming

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=46246" target="_blank">https://www.oasis-open.org/apps/org/workgroup/odata/event.php?event_id=46246

   - 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=46246&confirmed=1

Room Information:

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

- Thursday, 08 March 2018, 08:00am to 10:00am PST

   - i.e. 2018-03-08 17:00 to 19:00 CET (UTC+1)

   - other timezone? Try eg.:

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

TimezoneInterferences:

- In North America, daylight savings time begins on March 11th. (Ends November 4th if you want to be proactive.)

- In Europe (by and large), daylight savings time begins two weeks later on March 25th.

- Note as always that different locales do this differently.

  - (For example, Mexico starts on April 1st.) So folks may want to check to be sure.

UsefulPlaces:

- Chat:

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

- ScreenShare and Voice:

   - https://lync.co.sap.com/meet/ralf.handl/82RDM4K6

     - Conference ID: 50209199

Next Planned meetings (tentative):

- Thursday March 15, 2018 during 8-10 am PDT (16:00-18:00 CET)  Daylight Saving Time in North America

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

- Thursday March 22, 2018 during 8-10 am PDT (16:00-18:00 CET) - Daylight Saving Time in North America

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

Agenda-Draft E-Mail URL:

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

Minutes Draft Public URL (previous meeting):

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

Online document walkthroughs or presentations:

- URL = "" href="https://lync.co.sap.com/meet/ralf.handl/82RDM4K6" target="_blank">https://lync.co.sap.com/meet/ralf.handl/82RDM4K6

  - Conference ID: 50209199

- Fallbacks:

  - old Conference call & Screen sharing: https://sap.emea.pgiconnect.com/OData-TC

  - old Conference call details: https://www.oasis-open.org/apps/org/workgroup/odata/download.php/56760/TC%20meeting%20dial-in%20details.htm

Timeline(Updated!):

- URL = "" href="https://www.oasis-open.org/committees/download.php/62637/TC%20Timeline-2018-03-02.docx" target="_blank">https://www.oasis-open.org/committees/download.php/62637/TC%20Timeline-2018-03-02.docx

Agenda Draft (for meeting #206):

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

1. Roll call [8:00 am PT]

  1.1 Self-registration link:

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

2. Approve agenda [8:05 am PT]

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

  3.1 Minutes from March 01, 2018 TC meeting:

  URL = "" href="https://www.oasis-open.org/committees/download.php/62633/odata-meeting-205_on-20180301-minutes.html" target="_blank">https://www.oasis-open.org/committees/download.php/62633/odata-meeting-205_on-20180301-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 none

5. Infos from TC Admin (Chet Ensign)

  5.1 Vocabularies and V4.0 Errata 04

    5.1.1 We can change the vocabulary references in the specification documents to the GitHub vocabularies

    5.1.2 We should in addition pack the most recent copy of the GitHub vocabularies into the Errata zip, so they are published at the usual location

    5.1.3 This is not a problem because the GitHub vocabularies contain latest-version links that point to GitHub

  5.2 Jira Issue Notifications

    5.2.1 Currently the TC Jira sends notifications to the TC mailing list for every change of an issue

          Created, Updated, Resolved, Closed, Commented, Comment Edited, Comment Deleted, Reopened, Deleted

    5.2.2 Now a terse notification scheme is available, reduced to

          Created, Resolved

    5.2.3 Do we want to switch to terse? Watchers of an issue will still receive notifications of any change to the watched issue

6. Timeline

  6.1 Updated timeline, see [3]:

      URL = "" href="https://www.oasis-open.org/committees/download.php/62637/TC%20Timeline-2018-03-02.docx" target="_blank">https://www.oasis-open.org/committees/download.php/62637/TC%20Timeline-2018-03-02.docx

7. Issues [8:20 am PT]

  7.1 APPLIED

    7.1.1 ODATA-1155 ABNF: allow omitting default namespaces everywhere in the URL

  7.2 Vocabularies: NEW or OPEN with concrete proposal

    7.2.1 ODATA-1072 Annotation to describe supported aggregation methods

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

  7.3 Vocabularies: NEW or OPEN that need more discussion  triage

    7.3.1 ODATA-1099 Add annotations to describe custom query options and custom headers

    7.3.2 ODATA-1067 Consider ability to define computed default values

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

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

  7.4 V4.01: NEW or OPEN

    7.4.1 ODATA-1156 Context URL: allow empty parentheses after navigation property

    7.4.2 ODATA-1154 Clarify which OData-Version a service should return

    7.4.3 ODATA-1151 Edm.Stream and Nullable

    7.4.4 ODATA-1149 Support Delta responses for Singletons

    7.4.5 ODATA-1148 PATCH with nested nav props should not remove omitted resources

    7.4.6 ODATA-1141 Upsert: clarify upsert along nullable single-valued navigation path

8. Next meetings [9:50 am PT]

  8.1 Thursday March 15, 2018 during 8-10 am PDT (16:00-18:00 CET)  Daylight Saving Time in North America

  8.2 Thursday March 22, 2018 during 8-10 am PDT (16:00-18:00 CET)  Daylight Saving Time in North America

  8.3 Thursday March 29, 2018 during 8-10 am PDT (17:00-19:00 CEST)  back to normal time difference, Easter is coming

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=46246" target="_blank">https://www.oasis-open.org/apps/org/workgroup/odata/event.php?event_id=46246

   - 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=46246&confirmed=1

[16:59] Stefan Hagen: H4Q::Voting Members: 3 of 11 (27%) (used for quorum calculation)

[17:02] anonymous morphed into George Ericson (Dell)

[17:03] Stefan Hagen: H4Q::Voting Members: 8 of 11 (72%) (used for quorum calculation)

[17:03] Stefan Hagen: We are quorate I guess ...

[17:03] Ralf Handl (SAP SE): Note: we are trying to use Skype for Business today:

   - https://lync.co.sap.com/meet/ralf.handl/82RDM4K6

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

[17:11] Ralf Handl (SAP SE): Agenda is approved

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

a.Minutes from March 01, 2018 TC meeting: https://www.oasis-open.org/apps/org/workgroup/odata/download.php/62633/latest/odata-meeting-205_on-20180301-minutes.html

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

[17:12] 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:13] Ralf Handl (SAP SE): @Mark: please dial in via https://lync.co.sap.com/meet/ralf.handl/82RDM4K6

[17:14] Ralf Handl (SAP SE): 5.Infos from TC Admin (Chet Ensign)

a.Vocabularies and V4.0 Errata 04

i.We can change the vocabulary references in the specification documents to the GitHub vocabularies

ii.We should in addition pack the most recent copy of the GitHub vocabularies into the Errata zip, so they are published at the usual location

iii.This is not a problem because the GitHub vocabularies contain latest-version links that point to GitHub

[17:17] Mark Biamonte (Progress)1: Sorry I am late.  I didn't see that we had switched to the Skype for Business bridge

[17:17] Ralf Handl (SAP SE): George: let's go with GitHub as the vocabulary source and NOT publish Errata 04

[17:19] Ralf Handl (SAP SE): Change log of vocabulary files is GitHub: https://github.com/oasis-tcs/odata-vocabularies

[17:19] Ralf Handl (SAP SE): Commits link back to TC Jira

[17:20] Ralf Handl (SAP SE): Same procedure in the time before GitHub: SVN as source control, commit comment links to TC Jira

[17:21] Ralf Handl (SAP SE): <Annotation Term="Core.Links">

        <Collection>

          <Record>

            <PropertyValue Property="rel" String="latest-version" />

            <PropertyValue Property="href" String="https://oasis-tcs.github.io/odata-vocabularies/vocabularies/Org.OData.Core.V1.xml" />

          </Record>

          <Record>

            <PropertyValue Property="rel" String="alternate" />

            <PropertyValue Property="href" String="https://oasis-tcs.github.io/odata-vocabularies/vocabularies/Org.OData.Core.V1.json" />

          </Record>

          <Record>

            <PropertyValue Property="rel" String="describedby" />

            <PropertyValue Property="href"

              String="https://github.com/oasis-tcs/odata-vocabularies/blob/master/vocabularies/Org.OData.Core.V1.md" />

          </Record>

        </Collection>

      </Annotation>

[17:24] Ralf Handl (SAP SE): b.Jira Issue Notifications

i.Currently the TC Jira sends notifications to the TC mailing list for every change of an issue

1.Created, Updated, Resolved, Closed, Commented, Comment Edited, Comment Deleted, Reopened, Deleted

ii.Now a terse notification scheme is available, reduced to

1.Created, Resolved

iii.Do we want to switch to terse? Watchers of an issue will still receive notifications of any change to the watched issue

[17:26] Ralf Handl (SAP SE): Gerald: terse

[17:26] Ralf Handl (SAP SE): Ralf: terse

[17:26] Ralf Handl (SAP SE): Mark: no preference

[17:27] Ralf Handl (SAP SE): Ramesh: keep verbose

[17:31] Ralf Handl (SAP SE): Ramesh: fine with switching to terse

[17:31] Ralf Handl (SAP SE): Ralf to contact TC Admin to switch to "terse" notifications

[17:31] Stefan Hagen: Stefan also in favour of terse

[17:32] Ralf Handl (SAP SE): 6.Timeline

a.Updated timeline, see [3]: https://www.oasis-open.org/committees/download.php/62637/TC%20Timeline-2018-03-02.docx

[17:36] Ralf Handl (SAP SE): I move to approve the new timeline

[17:36] Martin Z. SAP SE: second

[17:36] Martin Z. SAP SE: I second

[17:36] Ralf Handl (SAP SE): No objections, motion passes

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

a.APPLIED

i.ODATA-1155 ABNF: allow omitting default namespaces everywhere in the URL

[17:37] Ralf Handl (SAP SE): https://issues.oasis-open.org/browse/ODATA-1155

[17:37] Ralf Handl (SAP SE): Relax ABNF to allow omitting namespaces for

- functions

- actions

- type-cast

in

- path

- query options

But NOT in the context URL.

[17:39] Ralf Handl (SAP SE): https://tools.oasis-open.org/version-control/browse/wsvn/odata/?op=comp&compare%5B%5D=%2Ftrunk%2F4.01+spec%2FABNF@1129&compare%5B%5D=%2Ftrunk%2F4.01+spec%2FABNF@1142&manualorder=1

[17:44] Ralf Handl (SAP SE): I move to CLOSE ODATA-1155 as applied

[17:44] Mark Biamonte (Progress): second

[17:44] Ralf Handl (SAP SE): ODATA-1155 is CLOSED as applied

[17:45] Ralf Handl (SAP SE): b.Vocabularies: NEW or OPEN with concrete proposal

i.ODATA-1072 Annotation to describe supported aggregation methods

[17:45] Ralf Handl (SAP SE): https://issues.oasis-open.org/browse/ODATA-1072

[17:48] Gerald Krause (SAP): I move to resolve ODATA-1072 as proposed.

[17:49] Martin Z. SAP SE: I second

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

[17:49] Ralf Handl (SAP SE): ii.ODATA-1064 Add ability to annotate collections to return only count and NextLink

[17:50] Ralf Handl (SAP SE): Skipped

[17:50] Ralf Handl (SAP SE): c.Vocabularies: NEW or OPEN that need more discussion  triage

[17:50] Ralf Handl (SAP SE): i.ODATA-1099 Add annotations to describe custom query options and custom headers

[17:51] Ralf Handl (SAP SE): Ralf: would like to have it for odata-to-openapi mapping

[17:51] Ralf Handl (SAP SE): ii.ODATA-1067 Consider ability to define computed default values

[17:52] Ralf Handl (SAP SE): No one voting for doing it now, deferred

[17:52] Ralf Handl (SAP SE): iii.ODATA-1005 Make sure we have capabilities for all new 4.01 functionality

[17:53] Ralf Handl (SAP SE): Ralf: need this for generic clients

[17:53] Ralf Handl (SAP SE): Mark: agreed, need to do it

[17:54] Ralf Handl (SAP SE): Ralf: split it up into "topic groups" to see some progress

[17:54] Ralf Handl (SAP SE): iv.ODATA-884 Add term ErrorCodes to describe possible codes in error messages (public comment c201510e00019)

[17:55] Ralf Handl (SAP SE): https://issues.oasis-open.org/browse/ODATA-884

[17:57] Ralf Handl (SAP SE): Ralf: probably have to do this together with ODATA-1099 https://issues.oasis-open.org/browse/ODATA-1099

[17:57] Ralf Handl (SAP SE): d.V4.01: NEW or OPEN

i.ODATA-1156 Context URL: allow empty parentheses after navigation property

[17:58] Ralf Handl (SAP SE): https://issues.oasis-open.org/browse/ODATA-1156

[17:58] Ralf Handl (SAP SE): ABNF issue, ABNF is more restrictive than prose specification

[17:59] Ralf Handl (SAP SE): ODATA-1156 is OPEN

[17:59] Ralf Handl (SAP SE): https://tools.oasis-open.org/version-control/browse/wsvn/odata/trunk/4.01%20spec/ABNF/odata-abnf-construction-rules.txt?op=diff&rev=1137

https://tools.oasis-open.org/version-control/browse/wsvn/odata/trunk/4.01%20spec/ABNF/odata-abnf-testcases.xml?op=diff&rev=1137

[18:00] Ralf Handl (SAP SE): Change:

old: selectList         = OPEN selectListItem *( COMMA selectListItem ) CLOSE

new: selectList         = OPEN [ selectListItem *( COMMA selectListItem ) ] CLOSE

[18:00] Ralf Handl (SAP SE): I move to resolve ODATA-1156 as proposed

[18:00] George Ericson (Dell): Second

[18:01] Ralf Handl (SAP SE): I move to close ODATA-1156 as applied

[18:01] George Ericson (Dell): second

[18:01] Ralf Handl (SAP SE): ODATA-1156 is CLOSED as applied

[18:02] Ralf Handl (SAP SE): ii.ODATA-1154 Clarify which OData-Version a service should return

[18:02] Ralf Handl (SAP SE): Skipped

[18:02] Ralf Handl (SAP SE): iii.ODATA-1151 Edm.Stream and Nullable

[18:02] Ralf Handl (SAP SE): https://issues.oasis-open.org/browse/ODATA-1151

[18:03] Ralf Handl (SAP SE): 1) Expanded returns null

2) Link is always valid, returns 204 if the value is null

[18:03] Ralf Handl (SAP SE): Remark:

1) is consistent with the representation of structural properties of other primitive type and with expanded single-valued navigation properties

2) is consistent with directly accessing a property that has the null value, directly accessing the raw value of a property that has the null value, and directly accessing a single-valued navigation property that has no entity related

- http://docs.oasis-open.org/odata/odata/v4.01/cs01/part1-protocol/odata-v4.01-cs01-part1-protocol.html#sec_RequestingIndividualProperties

- http://docs.oasis-open.org/odata/odata/v4.01/cs01/part1-protocol/odata-v4.01-cs01-part1-protocol.html#sec_RequestingaPropertysRawValueusingval

- http://docs.oasis-open.org/odata/odata/v4.01/cs01/part1-protocol/odata-v4.01-cs01-part1-protocol.html#sec_RequestingRelatedEntities

[18:05] Ralf Handl (SAP SE): I move to resolve ODATA-1151 as proposed

[18:05] George Ericson (Dell): Second

[18:05] Matt Borges (SAP): I second

[18:06] Ralf Handl (SAP SE): ODATA-2251 is RESOVLED as proposed

[18:06] Ralf Handl (SAP SE): iv.ODATA-1149 Support Delta responses for Singletons

[18:06] Ralf Handl (SAP SE): https://issues.oasis-open.org/browse/ODATA-1149

[18:07] Ralf Handl (SAP SE): Today we are a bit unclear about whether or not deltas are supported for singletons.

In 11.3 Requesting Changes of the Protocol document, we say:

"Any GET request to retrieve one or more entities MAY allow change-tracking."

However, in 15.1 Delta Response of the JSON document we say:

"Responses from a delta request are returned as a JSON object. The JSON object MUST contain an array-valued property named value containing all added, changed, or deleted entities, as well as added links or deleted links between entities, and MAY contain additional, unchanged entities."

The wording from the JSON spec makes sense for 4.0, since changes to related entities and links were represented in a flattened result, but with the ability to represent nested related content, it is useful to support a delta payload (GET or PATCH) for requests anchored on a single node.

[18:09] Ralf Handl (SAP SE): George: why not

[18:09] Ralf Handl (SAP SE): George: no array, just one "delta object"

[18:09] Ralf Handl (SAP SE): Ralf: need new context URL pattern to distinguish this from "full object"

[18:10] Ralf Handl (SAP SE): ODATA-1149 is OPEN

[18:10] Ralf Handl (SAP SE): Need a more concrete proposal

[18:11] Ralf Handl (SAP SE): v.ODATA-1148 PATCH with nested nav props should not remove omitted resources

[18:11] Ralf Handl (SAP SE): https://issues.oasis-open.org/browse/ODATA-1148

[18:12] Ralf Handl (SAP SE): In OData 4.0 we explicitly disallowed deep updates (i.e., including related entities in a PUT or PATCH request). We did allow binding (through the @bind annotation).

In OData 4.01 we added the ability to do deep updates, but we are inconsistent with how we describe the behavior.

In the Protocol document we say that the nested content replaces the existing content, removing any related resources not specified in the payload:

11.4.3.1 Update Related Entities When Updating an Entity (Protocol)

Payloads with an OData-Version header with a value of 4.01 or greater MAY include nested entities and entity references that specify the full set of currently related entities, or a nested delta payload representing the related entities that have been added, removed, or changed.

If the nested collection is represented identical to an expanded navigation property, then the set of nested entities and entity references specified in a successful update request represents the full set of entities to be related according to that relationship and MUST NOT include added links, deleted links, or deleted entities.

However, this is different than the semantics we describe in section 8.5 of the JSON document (taken from 4.0), which says that the bound items are added, and don't affect the existing relationships:

8.5 Bind Operation (JSON)

For update operations a bind operation on a collection navigation property adds additional relationships, it does not replace existing relationships, while bind operations on an entity navigation property update the relationship.

In fact, for a PATCH operation, most people expect that the membership of the collection-valued nav prop is not replaced, but that specified resources are added or updated.

It would probably be more intuitive to say that PATCH updates the service with the references in the payload, and that PUT must be used in order to do the replace semantics, or @delta can be used to remove (or upsert) individual entries.

[18:15] Ralf Handl (SAP SE): George: consider PATCH on collection

[18:15] Ralf Handl (SAP SE): 11.4.12 Update a Collection of Entities

Collections of entities can be updated by submitting a PATCH request to the resource path of the collection. The body of the request MUST be a delta payload, and the resource path of the collection MUST NOT contain type cast or filter segments.

Added/changed entities are applied as upserts, and deleted entities as deletions. The top-level collection may include added and deleted links, and related entities represented inline are updated according to the rules for treating related entities when updating an entity.

The response, if requested, is a delta payload, in the same structure and order as the request payload, representing the applied changes.

On failure, the service MUST NOT apply any of the changes specified in the delta request payload.

[18:18] Ralf Handl (SAP SE): Current PATCH behavior for single entity with related collection:

  "Items": [...]

means replace

[18:19] Ralf Handl (SAP SE): For "delta patch" use

  "Items@odata.delta": [...]

[18:20] Ralf Handl (SAP SE): ODATA-1148 is OPEN

[18:20] Ralf Handl (SAP SE): vi.ODATA-1141 Upsert: clarify upsert along nullable single-valued navigation path

[18:20] Ralf Handl (SAP SE): https://issues.oasis-open.org/browse/ODATA-1141

[18:21] Ralf Handl (SAP SE): Description:

Section 11.4.4 Upsert an Entity allows upsert request to any URL that identifies a single entity. It then references section 11.4.2 Create an Entity, which only talks about creating entities in a collection

Clarify that upsert is also valid along a nullable single-valued navigation property, at least as long the key property values are client-defined. May also work with server-defined keys by responding with 201 and a location header with the canonical URL of the newly created entity.

[18:24] Ralf Handl (SAP SE): George: for server-generated keys: if key is provided, relate and update target, otherwise create and relate new target entity

[18:24] Ralf Handl (SAP SE): ODATA-1141 is OPEN

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

a.Thursday March 15, 2018 during 8-10 am PST (16:00-18:00 CEST)  Daylight Saving Time in Central Europe

b.Thursday March 22, 2018 during 8-10 am PST (16:00-18:00 CEST)  Daylight Saving Time in Central Europe

c.Thursday March 29, 2018 during 8-10 am PDT (17:00-19:99 CEST)  back to normal time difference, Easter is coming

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

[18:27] Ralf Handl (SAP SE): Switch back to Adobe Connect for telco

[18:28] Ralf Handl (SAP SE): Dial-in not possible from Linux with Skype for Business

[18:29] Ralf Handl (SAP SE): Screen sharing problematic

[18:30] 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: Mittwoch, 7. März 2018 09:58
To: odata@lists.oasis-open.org
Subject: [CAUTION] RE: [odata] Agenda for OData TC meeting on 2018-03-08

Renamed 5 to “Infos from TC Admin (Chet Ensign)”

Added 5.b. Jira Issue Notifications

From: odata@lists.oasis-open.org [mailto:odata@lists.oasis-open.org] On Behalf Of Handl, Ralf
Sent: Montag, 5. März 2018 10:31
To: odata@lists.oasis-open.org
Subject: [CAUTION] RE: [odata] Agenda for OData TC meeting on 2018-03-08

As mentioned a few weeks ago I’d like to switch to Skype for Business for our conference call. Please dial in using the Skype meeting info below.

This will only replace the conference call, we will continue using the chat room http://webconf.soaphub.org/conf/room/odatatc.

.........................................................................................................................................

à Join Skype Meeting

Trouble Joining? Try Skype Web App

Join by phone

+1 8552234162 "Canada", access code: 50209199 (SAP Dial-In)

+86 4008106069 "China All Cities", access code: 50209199 (SAP Dial-In)

+49 8005891883 "Germany", access code: 50209199 (SAP Dial-In)

+49 6922227996 "Germany Frankfurt", access code: 50209199 (SAP Dial-In)

+91 8071279160 "India Bangalore", access code: 50209199 (SAP Dial-In)

0008004404099 "India", access code: 50209199 (SAP Dial-In)

+65 67041630 "Singapore All Cities", access code: 50209199 (SAP Dial-In)

+44 3306068668 "United Kingdom All Cities", access code: 50209199 (SAP Dial-In)

+1 8664100244 "United States", access code: 50209199 (SAP Dial-In)

+1 2106069508 "United States All Cities", access code: 50209199 (SAP Dial-In)

Find a local number

Conference ID: 50209199 (same as access code above)

Forgot your dial-in PIN? |Help

_{[!OC([1033])!]}

.........................................................................................................................................

From: odata@lists.oasis-open.org [mailto:odata@lists.oasis-open.org] On Behalf Of Handl, Ralf
Sent: Freitag, 2. März 2018 15:19
To: odata@lists.oasis-open.org
Subject: [CAUTION] [odata] Agenda for OData TC meeting on 2018-03-08

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

2. Approve agenda [8:05 am PT]

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

Minutes from March 01, 2018 TC meeting: https://www.oasis-open.org/apps/org/workgroup/odata/download.php/62633/latest/odata-meeting-205_on-20180301-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. Infos from TC Admin (Chet Ensign)

Vocabularies and V4.0 Errata 04

i. We can change the vocabulary references in the specification documents to the GitHub vocabularies

ii. We should in addition pack the most recent copy of the GitHub vocabularies into the Errata zip, so they are published at the usual location

iii. This is not a problem because the GitHub vocabularies contain latest-version links that point to GitHub

Jira Issue Notifications

i. Currently the TC Jira sends notifications to the TC mailing list for every change of an issue

Created, Updated, Resolved, Closed, Commented, Comment Edited, Comment Deleted, Reopened, Deleted

ii. Now a “terse” notification scheme is available, reduced to

Created, Resolved

iii. Do we want to switch to “terse”? Watchers of an issue will still receive notifications of any change to the watched issue

6. Timeline

Updated timeline, see [3]: https://www.oasis-open.org/committees/download.php/62637/TC%20Timeline-2018-03-02.docx

7. Issues [8:20 am PT]

APPLIED

i. ODATA-1155 ABNF: allow omitting default namespaces everywhere in the URL

Vocabularies: NEW or OPEN with concrete proposal

i. ODATA-1072 Annotation to describe supported aggregation methods

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

Vocabularies: NEW or OPEN that need more discussion – triage

i. ODATA-1099 Add annotations to describe custom query options and custom headers

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

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

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

V4.01: NEW or OPEN

i. ODATA-1156 Context URL: allow empty parentheses after navigation property

ii. ODATA-1154 Clarify which OData-Version a service should return

iii. ODATA-1151 Edm.Stream and Nullable

iv. ODATA-1149 Support Delta responses for Singletons

v. ODATA-1148 PATCH with nested nav props should not remove omitted resources

vi. ODATA-1141 Upsert: clarify upsert along nullable single-valued navigation path

8. Next meetings [9:50 am PT]

Thursday March 15, 2018 during 8-10 am PST (16:00-18:00 CEST) – Daylight Saving Time in Central Europe
Thursday March 22, 2018 during 8-10 am PST (16:00-18:00 CEST) – Daylight Saving Time in Central Europe
Thursday March 29, 2018 during 8-10 am PDT (17:00-19:99 CEST) – back to normal time difference, Easter is coming

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

[2] References

Chat room: http://webconf.soaphub.org/conf/room/odatatc
Fallback: old Conference call & Screen sharing: https://sap.emea.pgiconnect.com/OData-TC
Fallback: old 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/62637/TC%20Timeline-2018-03-02.docx

odata message