RE: [odata] Agenda for OData TC meeting on 2018-02-22 - chat transcript

["Handl, Ralf" <ralf.handl@sap.com>]

[16:38] Stefan Hagen1: chat.keep_alive()

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

[17:04] Ralf Handl (SAP SE): Voting Members: 7 of 11 (63%) (used for quorum calculation)

[17:04] Ralf Handl (SAP SE): Quorum achieved: yes

[17:04] Ralf Handl (SAP SE): Only four members in the call so far

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

[17:07] Stefan Hagen: Still Travelling

[17:07] Stefan Hagen: Still Travelling

[17:08] Stefan Hagen: I will be alle to join the Adobe.connect in a few  minutes

[17:09] Ralf Handl (SAP SE): No changes

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

a.Minutes from February 15, 2018 TC meeting: https://www.oasis-open.org/committees/download.php/62546/odata-meeting-203_on-20180215-minutes.html

[17:09] 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:11] Ralf Handl (SAP SE): 5.Issues [8:20 am PT]

a.APPLIED

i.ODATA-1121 Add FilterExpressionType values "MultiRange" and "MultiRangeOrSearchExpression"

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

[17:11] Ralf Handl (SAP SE): https://github.com/oasis-tcs/odata-vocabularies/pull/9

[17:16] Ralf Handl (SAP SE): I move to close ODATA-1121 as applied

[17:16] Hubert Heijkers (IBM): I second

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

[17:17] Ralf Handl (SAP SE): ii.ODATA-1144 Allow percent-encoded colon in time values in URLs

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

[17:19] Hubert Heijkers (IBM): I move to close ODATA-1144 as applied

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

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

[17:19] Ralf Handl (SAP SE): iii.ODATA-1147 Annotate a function or action as "availability is advertised per instance"

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

[17:22] Hubert Heijkers (IBM): I move to close ODATA-1147 as applied

[17:22] George Ericson (Dell): I second

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

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

i.ODATA-1152 Align Prefer header rule with RFC7240: optional whitespace around commas

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

[17:27] Ralf Handl (SAP SE): ODATA-1152 is OPEN

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

[17:27] George Ericson (Dell): I second

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

[17:28] Hubert Heijkers (IBM): I move to close ODATA-1152 as applied

[17:28] George Ericson (Dell): I second

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

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

i.ODATA-1153 Core.Immutable: clarify that value can be provided *by client* in insert

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

[17:33] Ralf Handl (SAP SE): Sorry, ODATA-1153

[17:34] Ralf Handl (SAP SE): I move to resolve ODATA-1153 as proposed

[17:34] Hubert Heijkers (IBM): I second

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

[17:34] Ralf Handl (SAP SE): ii.ODATA-1142 Clarify MaxDistance is an optional parameter in hierarchy filter functions

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

[17:44] George Ericson (Dell): Issue with: <Parameter Name="MaxDistance" Type="Edm.Int16">.

[17:45] George Ericson (Dell): 1) What is minimum value 0 or 1?

[17:45] George Ericson (Dell): 2) Should this be a Edm.Uint16?

[17:48] Ralf Handl (SAP SE): ODATA-1142 is OPEN

[17:51] Ralf Handl (SAP SE): Use Validation.Minimum on the distance parameter

[17:52] Gerald Krause (SAP): Add meaning of distance to description

[17:54] George Ericson (Dell): I move to resolve ODATA-1142 as proposed and with changes as discussed.

[17:55] Gerald Krause (SAP): updated proposal:

[17:56] Gerald Krause (SAP): Extend the current definitions to make the maximum distance parameters optional by assigning the maximum possible distance by default (additions are enclosed in *):

<Function Name="isdescendant" IsBound="true">

  <Annotation Term="Core.Description" String="Returns true, if and only if the value of the node property of the specified hierarchy is a descendant of the given parent node with a distance of less than or equal to the optionally specified maximum distance"/>

  <Parameter Name="Entity" Type="Edm.EntityType" Nullable="false"/>

  <Parameter Name="Hierarchy" Type="Edm.String" Nullable="false"/>

  <Parameter Name="Node" Type="Edm.PrimitiveType" Nullable="false"/>

  <Parameter Name="MaxDistance" Type="Edm.Int16">

*    

    <Annotation Term="Core.OptionalParameter"> 

      <PropertyValue Property="DefaultValue" Int="32767"/> 

    </Annotation>

*    

  </Parameter>

  <ReturnType Type="Edm.Boolean"/>

</Function>

<Function Name="isancestor" IsBound="true">

  <Annotation Term="Core.Description" String="Returns true, if and only if the value of the node property of the specified hierarchy is an ancestor of the given child node with a distance of less than or equal to the optionally specified maximum distance"/>

  <Parameter Name="Entity" Type="Edm.EntityType" Nullable="false"/>

  <Parameter Name="Hierarchy" Type="Edm.String" Nullable="false"/>

  <Parameter Name="Node" Type="Edm.PrimitiveType" Nullable="false"/>

  <Parameter Name="MaxDistance" Type="Edm.Int16">

*    

    <Annotation Term="Core.OptionalParameter"> 

      <PropertyValue Property="DefaultValue" Int="32767"/> 

    </Annotation>

*    

  </Parameter>

  <ReturnType Type="Edm.Boolean"/>

</Function>

Note that term OptionalParameter has become available in the Core vocabulary with the work on OData version 4.01.

add to this proposal:

  - Use Validation.Minimum on the distance parameter

- Add meaning of distance to description

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

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

[17:57] Ralf Handl (SAP SE): iii.ODATA-1136 Allow hierarchy filter functions for ancestors and descendants to return true for starting node

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

[18:02] Gerald Krause (SAP): $it/Aggregation.isdescendant(Hierarchy='SalesOrgHierarchy',Node='EMEA',IncludeParent=true)

[18:05] Hubert Heijkers (IBM): As opposed to adding a parameter I'd introduce two new bound functions called isIAncestor and isIDescendant

[18:12] Hubert Heijkers (IBM): Scrap my comment, the implementation is intended to work the other way around, never mind

[18:19] Ralf Handl (SAP SE): ODATA-1136 is OPEN

[18:20] Gerald Krause (SAP): add to proposal: 

- extend description by explanation of newly added parameter.

[18:21] Hubert Heijkers (IBM): I move to resolve ODATA-1136 as per the amended proposal

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

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

[18:22] Ralf Handl (SAP SE): iv.ODATA-1072 Annotation to describe supported aggregation methods

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

[18:38] Ralf Handl (SAP SE): ODATA-1072 is OPEN

[18:41] Ralf Handl (SAP SE): We could make this into a structured term that also has a property for the recommended (single) aggregation method

[18:41] Ralf Handl (SAP SE): Gerald to extend the proposal for the next meeting

[18:41] Ralf Handl (SAP SE): d.Vocabularies: NEW or OPEN that need more discussion

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

[18:55] Ralf Handl (SAP SE): Prefer: include-annotations="odata.navigationLink"

[18:59] Ralf Handl (SAP SE): George will adjust proposal accordingly

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

a.Thursday March 01, 2018 during 8-10 am PST

b.Thursday March 08, 2018 during 8-10 am PST

[19:00] Ralf Handl (SAP SE): Hubert can't make next week

[19:00] Ralf Handl (SAP SE): 7.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: Dienstag, 20. Februar 2018 16:13
To: odata@lists.oasis-open.org
Subject: [CAUTION] [odata] Agenda for OData TC meeting on 2018-02-22

 

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

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

 

2.        Approve agenda [8:05 am PT]

 

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

1. Minutes from February 15, 2018 TC meeting: https://www.oasis-open.org/committees/download.php/62546/odata-meeting-203_on-20180215-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]

1. Action items due

                                  i.    none

 

5.        Issues [8:20 am PT]

1. APPLIED

                                  i.    ODATA-1121 Add FilterExpressionType values "MultiRange" and "MultiRangeOrSearchExpression"

                                 ii.    ODATA-1144 Allow percent-encoded colon in time values in URLs

                                iii.    ODATA-1147 Annotate a function or action as "availability is advertised per instance"

 

2. Errata: NEW or OPEN with concrete proposal

                                  i.    ODATA-1152 Align Prefer header rule with RFC7240: optional whitespace around commas

 

3. Vocabularies: NEW or OPEN with concrete proposal

                                  i.    ODATA-1153 Core.Immutable: clarify that value can be provided *by client* in insert

                                 ii.    ODATA-1142 Clarify MaxDistance is an optional parameter in hierarchy filter functions

                                iii.    ODATA-1136 Allow hierarchy filter functions for ancestors and descendants to return true for starting node

                                iv.    ODATA-1072 Annotation to describe supported aggregation methods

 

4. Vocabularies: NEW or OPEN that need more discussion

                                  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-1064 Add ability to annotate collections to return only count and NextLink

                                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.        Next meetings [9:50 am PT]

1. Thursday March 01, 2018 during 8-10 am PST
2. Thursday March 08, 2018 during 8-10 am PST

 

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