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

Room information was updated by: Stefan Hagen

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

- Thursday, 03 August 2017, 08:00am to 10:00am PDT

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

  - other timezone? Try eg.:

  - https://www.timeanddate.com/worldclock/meetingdetails.html?year=2017&month=8&day=03&hour=15&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 August 24, 2017 during 8-10 am PDT (17:00-19:00 CEST)

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

- Thursday August 31, 2017 during 8-10 am PDT (17:00-19:00 CEST)

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

- Thursday September 07, 2017 during 8-10 am PDT?

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

Agenda-Draft E-Mail URL:

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

Minutes Draft Public URL (previous meeting):

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

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

Agenda Draft (for meeting #183):

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

1.  Roll call

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

2.  Approve agenda

3.  Approve minutes from previous meeting(s)

  3.1 Minutes from July 20, 2017 TC meeting: https://www.oasis-open.org/committees/download.php/61256/odata-meeting-182_on-20170720-minutes.html

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

  4.1 Action items due

    None

5. Version 4.01 Public Review

  5.1 05 July 2017 to 03 August 2017 - Issues

    5.1.1 ODATA-1087 Discourage or disallow names differing only in case

    5.1.2 ODATA-1094 Apply _expression_: allow all URL functions with prefix odata.

    5.1.3 ODATA-1095 Allow empty edm:Schema elements

    5.1.4 ODATA-1096 9.1.4 Response Code 204 No Content: rephrase second paragraph

    5.1.5 ODATA-1097 14.4.1.1 Path Syntax: add odata.mediaETag

6. Issues

  6.1 Vocabularies: NEW or OPEN

    6.1.1 ODATA-1067 Consider ability to define computed default values

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

    6.1.3 ODATA-1060 Improve specification of element response requirements

    6.1.4 ODATA-1055 DeepInsertSupport: allow applying to entity sets

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

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

7. Next meetings

  7.1 Two-week break mid of August, then back to weekly schedule

  7.2 Thursday August 24, 2017 during 8-10 am PDT

  7.3 Thursday August 31, 2017 during 8-10 am PDT

  7.4 Thursday September 07, 2017 during 8-10 am PDT

8. AOB and wrap up

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

Meeting Member URL:

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

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

Stefan Hagen: [NOOP]

Stefan2: (Noop)

Stefan1: (Noop)

Stefan2: (Noop)

Stefan: (Noop)

Stefan1: (Noop)

Stefan: (Noop)

Stefan Hagen: RegInfo:{Voting Members: 3 of 12 (25%) (used for quorum calculation)}

anonymous morphed into Martin Z. SAP SE

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

Room Information:

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

- Thursday, 03 August 2017, 08:00am to 10:00am PDT

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

  - other timezone? Try eg.:

  - https://www.timeanddate.com/worldclock/meetingdetails.html?year=2017&month=8&day=03&hour=15&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 August 24, 2017 during 8-10 am PDT (17:00-19:00 CEST)

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

- Thursday August 31, 2017 during 8-10 am PDT (17:00-19:00 CEST)

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

- Thursday September 07, 2017 during 8-10 am PDT?

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

Agenda-Draft E-Mail URL:

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

Minutes Draft Public URL (previous meeting):

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

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

Agenda Draft (for meeting #183):

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

1.  Roll call

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

2.  Approve agenda

3.  Approve minutes from previous meeting(s)

  3.1 Minutes from July 20, 2017 TC meeting: https://www.oasis-open.org/committees/download.php/61256/odata-meeting-182_on-20170720-minutes.html

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

  4.1 Action items due

    None

5. Version 4.01 Public Review

  5.1 05 July 2017 to 03 August 2017 - Issues

    5.1.1 ODATA-1087 Discourage or disallow names differing only in case

    5.1.2 ODATA-1094 Apply _expression_: allow all URL functions with prefix odata.

    5.1.3 ODATA-1095 Allow empty edm:Schema elements

    5.1.4 ODATA-1096 9.1.4 Response Code 204 No Content: rephrase second paragraph

    5.1.5 ODATA-1097 14.4.1.1 Path Syntax: add odata.mediaETag

6. Issues

  6.1 Vocabularies: NEW or OPEN

    6.1.1 ODATA-1067 Consider ability to define computed default values

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

    6.1.3 ODATA-1060 Improve specification of element response requirements

    6.1.4 ODATA-1055 DeepInsertSupport: allow applying to entity sets

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

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

7. Next meetings

  7.1 Two-week break mid of August, then back to weekly schedule

  7.2 Thursday August 24, 2017 during 8-10 am PDT

  7.3 Thursday August 31, 2017 during 8-10 am PDT

  7.4 Thursday September 07, 2017 during 8-10 am PDT

8. AOB and wrap up

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

Meeting Member URL:

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

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

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

[17:00] anonymous morphed into Matt Borges (SAP)

[17:02] Stefan Hagen: RegInfo:{Voting Members: 6 of 12 (50%) (used for quorum calculation)}

[17:02] Stefan Hagen: one missing for Quorum ...

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

[17:03] Ralf Handl (SAP SE): Voting Members: 7 of 12 (58%) (used for quorum calculation)

[17:03] Ralf Handl (SAP SE): Achieved quorum: yes

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

[17:05] Ralf Handl (SAP SE): New topics:

[17:05] Ralf Handl (SAP SE): Release date for new vocabularies, and whether these would be V4.01 or V4

[17:06] Ralf Handl (SAP SE): 2: Actions, especially bound actions

[17:06] Ralf Handl (SAP SE): New issue ODATA-1098

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

a.Minutes from July 20, 2017 TC meeting: https://www.oasis-open.org/committees/download.php/61256/odata-meeting-182_on-20170720-minutes.html

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

[17:08] 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): 4.5 Actions

[17:09] Ralf Handl (SAP SE): 2)The specification of Actions is not intuitive to me.

a.Why would redfish specify the binding parameter with type  MyType.Actions?

i.Unclear why it isnt defined with type: MyType.MyType

b.Is the value of the binding parameter intended to be a reference to the property Actions?

c.How are by value or by reference semantics communicated in a parameter specification?

[17:12] Michael Pizzo: Hi all -- I'm on my way to the airport, but wanted to make sure you had quorum.  Have a great meeting!

[17:12] Ralf Handl (SAP SE): @Mike: thanks, and have a good flight!

[17:12] Michael Pizzo: Thanks!

[17:12] Michael Pizzo: ttfn

[17:14] Unknown/malformed action: /function(something=@s)?@s={"@odata.id":"/some/thing(1)"}

Check ?help

[17:15] Ralf Handl (SAP SE): 5.Version 4.01 Public Review - 05 July 2017 to 03 August 2017 [8:20 am PT]

a.Issues

i.ODATA-1087 Discourage or disallow names differing only in case

[17:17] Ralf Handl (SAP SE): George: disallow is hard as the spec is out for some years, so only discourage is possible

[17:19] Ralf Handl (SAP SE): ODATA-1087 is OPEN

[17:20] George Ericson (Dell): I move to add text to discourage use of names within any namespace that differ only in case.

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

[17:23] Ralf Handl (SAP SE): ODATA-1087 is RESOLVED as proposed: discourage, not disallow (yet)

[17:23] Ralf Handl (SAP SE): ii.ODATA-1094 Apply _expression_: allow all URL functions with prefix odata.

[17:24] Ralf Handl (SAP SE): <Annotation Term="org.example.display.DisplayName">

  <Apply Function="odata.concat">

    <String>Product: </String>

    <Path>ProductName</Path>

    <String> (</String>

    <Path>Available/Quantity</Path>

    <String> </String>

    <Path>Available/Unit</Path>

    <String> available)</String>

  </Apply>

</Annotation>

[17:25] Ralf Handl (SAP SE): <Term Name="Constraint" Type="Validation.ConstraintType" AppliesTo="Property EntityType ComplexType">

        <Annotation Term="Core.Description" String="Condition that the annotation target has to fulfill" />

      </Term>

      <ComplexType Name="ConstraintType">

        <Property Name="FailureMessage" Type="Edm.String" Nullable="true">

          <Annotation Term="Core.IsLanguageDependent" />

          <Annotation Term="Core.Description" String="Human-readable message that can be shown to end users if the constraint is not fulfilled" />

        </Property>

        <Property Name="Condition" Type="Edm.Boolean" Nullable="false">

          <Annotation Term="Core.Description"

            String="Value MUST be a dynamic _expression_ that evaluates to true if and only if the constraint is fulfilled" />

        </Property>

      </ComplexType>

[17:28] Ralf Handl (SAP SE): ODATA-1094 is OPEN

[17:28] George Ericson (Dell): I move odata 1094

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

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

[17:29] Ralf Handl (SAP SE): iii.ODATA-1095 Allow empty edm:Schema elements

[17:30] Ralf Handl (SAP SE): Description:

The current XML Schema for the EDM namespaces requires the edm:Schema element to contain at least one child element.

This is problematic in at least two use cases:

* OData API Designer tools - when starting with a "blank page"

* Services that "shrink" the schema to match user authorization - when the current user isn't allowed to see anything

Both require workarounds, e.g. having a dummy annotation in the schema telling that "this schema is intentionally empty".

[17:32] Ralf Handl (SAP SE): Eric likes the need to explain an empty schema

[17:33] Ralf Handl (SAP SE): Mark agrees

[17:33] Ralf Handl (SAP SE): ODATA-1095 is OPEN

[17:34] Mark Biamonte (Progress): I move that OData-1095 be resolved as proposed

[17:34] Matt Borges (SAP): I second

[17:34] Stefan Hagen: Scribe guesses, that above "Eric" should read "George" in the minutes ;-)

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

[17:35] Ralf Handl (SAP SE): iv.ODATA-1096 9.1.4 Response Code 204 No Content: rephrase second paragraph

[17:38] Ralf Handl (SAP SE): ODATA-1096 is OPEN

[17:39] Ralf Handl (SAP SE): The second paragraph of section 9.1.4 is a quote from RFC7231 and somewhat hard to parse. Replace it with text that expresses its intention: send an ETag only if the client can reasonably "know" the current entity representation that has not been sent in the response:

(1) For a PUT request: if the response body of a corresponding 200 response would have been identical to the request body, i.e. no server-side modification of values sent in the request body, no "calculated" values.

(2) We could extend this to PATCH requests and if a corresponding 200 response would have consisted of

- values sent in PATCH request body, plus

- server-side values corresponding to ETag sent in If-Match header of PATCH request (for values not sent in PATCH request body)

[17:39] Ralf Handl (SAP SE): The intention of the qoute from RFC7231 in section 9.4.1 is expressed by Julian Reschke (one of the

editors of RFC7231): "The main point here is that the server can only return an Etag if what was stored actually is what the client sent. If the server modified the data, the client will have to fetch the content using a subsequent GET request."

Source: First comment to the question at https://stackoverflow.com/questions/42246577/why-responses-to-put-requests-must-not-provide-an-etag.

[17:40] Ralf Handl (SAP SE): @George: sorry for naming you "Eric" (again)

[17:42] Martin Z. SAP SE: As defined in [RFC7231], a Data Modification Request that responds with 204 No Content MUST NOT include an ETag header unless the request's representation data was saved without any transformation applied to the body (i.e., the resource's new representation data is identical to the representation data received in the PUT request) and the ETag value reflects the new representation.

[17:45] Martin Z. SAP SE: From RFC7231:

An origin server MUST NOT send a validator header field (Section 7.2), such as an ETag or  Last-Modified field, in a successful response to PUT unless the request's representation data was saved without any transformation applied to the body (i.e., the resource's new representation data is identical to the representation data received in the PUT request) and the validator field value reflects the new representation. This requirement allows a user agent to know when the representation body it has in memory remains current as a result of the PUT, thus not in need of being retrieved again from the origin server, and that the new validator(s) received in the response can be used for future conditional requests in order to prevent accidental overwrites (Section 5.2).

[17:47] Martin Z. SAP SE: The main point here is that the server can only return an Etag if what was stored actually is what the client sent. If the server modified the data, the client will have to fetch the content using a subsequent GET request.  Julian Reschke Feb 15 at 11:49

[17:48] George Ericson (Dell): I move to approve ODATA-1096 for application to the text.

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

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

[17:50] Ralf Handl (SAP SE): v.ODATA-1097 14.4.1.1 Path Syntax: add odata.mediaETag

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

We allow only three of the for odata.media* control information names in "term casts", and omit the odata.mediaETag.

[17:51] Ralf Handl (SAP SE): ODATA-1097 is OPEN

[17:54] George Ericson (Dell): I move to approve ODATA-1097

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

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

[17:56] Ralf Handl (SAP SE): 5.5 Release date for new vocabularies, and whether these would be V4.01 or V4

[17:58] Ralf Handl (SAP SE): Core:

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

[18:00] Ralf Handl (SAP SE): https://oasis-tcs.github.io/odata-vocabularies/vocabularies/Org.OData.Core.V1.json

[18:02] Ralf Handl (SAP SE): Latest versions of vocabulary files (XML, JSON) and documentation (MarkDown) are in GitHub and reference each other

[18:02] Ralf Handl (SAP SE): Will publish new wrapper OASIS Spec pointing to these files once we've resolved the current set of vocabulary-related issues

[18:04] Ralf Handl (SAP SE): 6.Issues [9:10 am PT]

a.Vocabularies: NEW or OPEN

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

[18:09] Ralf Handl (SAP SE): ODATA-1098 is OPEN

[18:12] Mark Biamonte (Progress): I move that OData-1098 as proposed

[18:12] Martin Z. SAP SE: I second

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

[18:13] Ralf Handl (SAP SE): i.ODATA-1067 Consider ability to define computed default values

[18:14] Ralf Handl (SAP SE): Postpone to next meeting

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

[18:21] Ralf Handl (SAP SE): Term would apply to NavigationProperty

[18:26] Ralf Handl (SAP SE): With array of enumeration type:

<NavigationProperty Name="Systems" Type="Collection(ComputerSystem)">

<Annotation Term="OData.AutoMetadata">

EnumMember=["Count", "NavigationLink", "Type"] />

</NavigationProperty>

[18:28] Ralf Handl (SAP SE): Better:

<NavigationProperty Name="Systems" Type="Collection(ComputerSystem)">

<Annotation Term="OData.AutoMetadata">

  <Collection>

    <EnumMember>Core.MetadataKind/Count</EnumMember>

    <EnumMember>Core.MetadataKind/NavigationLink</EnumMember>

    <EnumMember>Core.MetadataKind/Type</EnumMember>

  </Collection>

</NavigationProperty>

[18:29] Ralf Handl (SAP SE): With Flags

<Annotation Term="OData.AutoMetadata" EnumMember="Core.MetadataKind/Count Core.MetadataKind/NavigationLink Core.MetadataKind/Type" />

[18:30] Ralf Handl (SAP SE): Flags EnumType is shorter and thus better

[18:30] Ralf Handl (SAP SE): Ralf wants to drop Type for now

[18:32] Ralf Handl (SAP SE): <Term Name="AutoMetadata" AppliesTo="NavigaitonProperty" Type="Core.MetadataKind">

<Annotation Term="Core.Description"

String="Defines metadata that should automatically be returned." />

</Term>

[18:34] Ralf Handl (SAP SE): <EnumType Name="MetadataKind" IsFlags="true">

<Annotation Term="Core.Description"

String="Return count metadata, equivalent to $count." />

  <Member Name="Count" Value="1">

    <Annotation Term="Core.Description"

String="Return count metadata, equivalent to $count." />

  </Member>

  <Member Name="NavigationLink" Value="2">

    <Annotation Term="Core.Description"

String="The is a URL that can be used to retrieve an entity or collection of entities related to the current entity via a navigation property. Doing a GET on this link is equivalent to specifying $expand."/>

  </Member>

  <Member Name="AssociationLink" Value="4">

    <Annotation Term="Core.Description"

String=" The value is a URL that can be used to retrieve a reference to an entity or a collection of references to entities related to the current entity via a navigation property. Doing a GET on this link is equivalent to specifying $ref." />

  </Member>

  <Member Name="Etag" Value="8">

    <Annotation Term="Core.Description"

String="The value is an entity tag (ETag) which is an opaque string value that can be used in a subsequent request to determine if the value of the entity has changed." />

  </Member>

</EnumType>

[18:35] Ralf Handl (SAP SE): <EntityType Name="Top">

<NavigationProperty Name="Systems" Type="Collection(ComputerSystem)">

<Annotation Term="OData.AutoMetadata"

EnumMember="Core.MetadataKind/Count Core.MetadataKind/NavigationLink" />

</NavigationProperty>

</EntityType>

<EntityType Name="ComputerSystem">

</EntityType>

[18:35] Ralf Handl (SAP SE): Example: GET

-----------

GET /redfish/v1/Top

Response

"@odata.context": "/redfish/v1/$metadata#Top",

"@odata.id": "/redfish/v1/Top",

"@odata.type": "#Top ",

"Name": "Top",

"Systems@odata.count": 15,

"Systems@odata.navigationlink": {"@odata.id": "/redfish/v1/Systems"}

[18:36] Mark Biamonte (Progress): I move that OData-1064 be resolved per the amended proposal

[18:36] Martin Z. SAP SE: i second

[18:39] Ralf Handl (SAP SE): Amendment: use same spelling for enum member names as for odata.* control information, i.e. lowerCamelCase, etag, count, navigationLink, associationLink

[18:39] George Ericson (Dell): I second the amendment on spelling

[18:40] Mark Biamonte (Progress): I move that OData-1064 be resolved per the newly updated proposal

[18:40] Martin Z. SAP SE: i second

[18:41] Ralf Handl (SAP SE): ODATA-1064 is RESOLVED as proposed (and twice amended)

[18:41] Ralf Handl (SAP SE): iii.ODATA-1060 Improve specification of element response requirements

[18:43] Ralf Handl (SAP SE): Postpone to next meeting

[18:43] Ralf Handl (SAP SE): iv.ODATA-1055 DeepInsertSupport: allow applying to entity sets

[18:45] Ralf Handl (SAP SE): ODATA-1055 is OPEN

[18:45] Ralf Handl (SAP SE): George: why not allow it for all collections

[18:46] Ralf Handl (SAP SE): Proposal:

Add "EntitySet" and "Collection" to list of model elements in AppliesTo attribute and rephrase descriptions to match this generalization.

[18:46] Martin Z. SAP SE: I move that OData-1055 be resolved per the amended proposal

[18:47] George Ericson (Dell): I second

[18:47] Ralf Handl (SAP SE): ODATA-1055 is RESOLVED with the amended proposal

[18:47] Ralf Handl (SAP SE): v.ODATA-1005 Make sure we have capabilities for all new 4.01 functionality

[18:49] Ralf Handl (SAP SE): Postpone until we have concrete proposal

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

[18:51] Ralf Handl (SAP SE): Postpone until we have a concrete proposal

[18:53] Ralf Handl (SAP SE): Another gap we have towards OpenAPI is documenting custom headers and custom query options via annotations

[18:53] Ralf Handl (SAP SE): Ralf to open a ticket for that

[18:54] Ralf Handl (SAP SE): Proposal to be aligned with OpenAPI 3.0.0

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

Two-week break mid of August, then back to weekly schedule

a.Thursday August 24, 2017 during 8-10 am PDT

b.Thursday August 31, 2017 during 8-10 am PDT

c.Thursday September 07, 2017 during 8-10 am PDT

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

[18:55] Ralf Handl (SAP SE): Meeting is adjourned

[18:55] Ralf Handl (SAP SE): Enjoy the break"!

From: odata@lists.oasis-open.org [mailto:odata@lists.oasis-open.org] On Behalf Of Handl, Ralf
Sent: Mittwoch, 2. August 2017 10:28
To: odata@lists.oasis-open.org
Subject: [odata] Agenda for OData TC meeting on 2017-08-03

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

1. Roll call [8:00 am PT]

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

2. Approve agenda [8:05 am PT]

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

a. Minutes from July 20, 2017 TC meeting: https://www.oasis-open.org/committees/download.php/61256/odata-meeting-182_on-20170720-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]

a. Action items due

i. None

5. Version 4.01 Public Review - 05 July 2017 to 03 August 2017 [8:20 am PT]

a. Issues