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

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

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

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

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

   - other timezone? Try eg.:

    - https://www.timeanddate.com/worldclock/meetingdetails.html?year=2018&month=2&day=8&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 February 15, 2018 during 8-10 am PST?

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

Agenda-Draft E-Mail URL:

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

Minutes Draft Public URL (previous meeting):

- URL = "" href="https://www.oasis-open.org/committees/download.php/62433/odata-meeting-201_on-20180201-minutes.html" target="_blank">https://www.oasis-open.org/committees/download.php/62433/odata-meeting-201_on-20180201-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 #202):

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

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

2. Approve agenda [8:05 am PT]

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

  3.1 Minutes from February 201, 2018 TC meeting:

    URL = "" href="https://www.oasis-open.org/committees/download.php/62433/odata-meeting-201_on-20180201-minutes.html" target="_blank">https://www.oasis-open.org/committees/download.php/62433/odata-meeting-201_on-20180201-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. Issues [8:20 am PT]

  5.1 V4.01: NEW or OPEN

    5.1.1 ODATA-1146 Clarify that an enumeration type must have at least one member

    5.1.2 ODATA-1144 Allow percent-encoded colon in time values in URLs

  5.2 Vocabularies: NEW or OPEN

    5.2.1 ODATA-1145 Align Authorization vocabulary with OpenAPI V3

    5.2.2 ODATA-1140 Add details to HTTPResponseCode term

    5.2.3 ODATA-1132 Propagation of NavigationRestrictions

    5.2.4 ODATA-1121 Add FilterExpressionType values "MultiRange" and "MultiRangeOrSearchExpression"

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

    5.2.6 ODATA-1067 Consider ability to define computed default values

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

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

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

6. Next meetings [9:50 am PT]

  6.1 Thursday February 15, 2018 during 8-10 am PST

  6.2 Thursday February 22, 2018 during 8-10 am PST

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

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

[16:48] Stefan Hagen: Voting Members: 1 of 11 (9%) (used for quorum calculation)

Room Information:

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

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

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

   - other timezone? Try eg.:

    - https://www.timeanddate.com/worldclock/meetingdetails.html?year=2018&month=2&day=8&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 February 15, 2018 during 8-10 am PST?

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

Agenda-Draft E-Mail URL:

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

Minutes Draft Public URL (previous meeting):

- URL = "" href="https://www.oasis-open.org/committees/download.php/62433/odata-meeting-201_on-20180201-minutes.html" target="_blank">https://www.oasis-open.org/committees/download.php/62433/odata-meeting-201_on-20180201-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 #202):

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

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

2. Approve agenda [8:05 am PT]

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

  3.1 Minutes from February 201, 2018 TC meeting:

    URL = "" href="https://www.oasis-open.org/committees/download.php/62433/odata-meeting-201_on-20180201-minutes.html" target="_blank">https://www.oasis-open.org/committees/download.php/62433/odata-meeting-201_on-20180201-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. Issues [8:20 am PT]

  5.1 V4.01: NEW or OPEN

    5.1.1 ODATA-1146 Clarify that an enumeration type must have at least one member

    5.1.2 ODATA-1144 Allow percent-encoded colon in time values in URLs

  5.2 Vocabularies: NEW or OPEN

    5.2.1 ODATA-1145 Align Authorization vocabulary with OpenAPI V3

    5.2.2 ODATA-1140 Add details to HTTPResponseCode term

    5.2.3 ODATA-1132 Propagation of NavigationRestrictions

    5.2.4 ODATA-1121 Add FilterExpressionType values "MultiRange" and "MultiRangeOrSearchExpression"

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

    5.2.6 ODATA-1067 Consider ability to define computed default values

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

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

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

6. Next meetings [9:50 am PT]

  6.1 Thursday February 15, 2018 during 8-10 am PST

  6.2 Thursday February 22, 2018 during 8-10 am PST

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

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

[17:03] Stefan Hagen: Voting Members: 5 of 11 (45%) (used for quorum calculation)

[17:03] Ralf Handl (SAP SE): Telco has now started, sorry for the delay

[17:04] Stefan Hagen: Voting Members: 6 of 11 (54%) (used for quorum calculation)

[17:04] Stefan Hagen: we are quorate ...

[17:05] Ralf Handl (SAP SE): So far only four people in the call

[17:05] Stefan Hagen: Voting Members: 7 of 11 (63%) (used for quorum calculation)

[17:08] Ralf Handl (SAP SE): Only five in the call: who's going to attend via chat only?

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

[17:09] Stefan Hagen: currently fighting with the app required ...

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

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

a.Minutes from February 01, 2018 TC meeting: https://www.oasis-open.org/committees/download.php/62433/odata-meeting-201_on-20180201-minutes.html

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

[17:11] 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:12] Ralf Handl (SAP SE): i.none

5.Issues [8:20 am PT]

a.V4.01: NEW or OPEN

i.ODATA-1146 Clarify that an enumeration type must have at least one member

[17:14] Ralf Handl (SAP SE): ODATA-1146 is OPEN

[17:15] Michael Pizzo: I move we resolve ODATA-1146 as proposed, clarifying the wording that enum types MUST contain one or more members, as intended and consistent with 4.0 and JSON

[17:16] George Ericson (Dell): Second Motion to approve OData-1146

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

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

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

[17:19] George Ericson (Dell): Motion to approve ODATA-1144 as proposed.

[17:23] Michael Pizzo: I second

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

[17:24] Ralf Handl (SAP SE): b.Vocabularies: NEW or OPEN

i.ODATA-1145 Align Authorization vocabulary with OpenAPI V3

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

[17:31] Ralf Handl (SAP SE): ODATA-1145 is OPEN

[17:45] Michael Pizzo: Current Authorizations vocabulary:

      <Term Name="Authorizations" Type="Collection(Auth.Authorization)" AppliesTo="EntityContainer EntitySet Singleton NavigationProperty Action Function">

        <Annotation Term="Core.Description" String="Lists the methods available to authorize access to the annotated resource" />

      </Term>

      <ComplexType Name="Authorization" Abstract="true">

        <Annotation Term="Core.Description" String="Base type for all Authorization types" />

        <Property Name="Description" Type="Edm.String">

          <Annotation Term="Core.Description" String="Description of the authorization method" />

        </Property>

      </ComplexType>

      <ComplexType Name="OpenIDConnect" BaseType="Auth.Authorization">

        <Property Name="IssuerUrl" Type="Edm.String" Nullable="false">

          <Annotation Term="Core.Description"

            String="Issuer location for the OpenID Provider. Configuration information can be obtained by appending `/.well-known/openid-configuration` to this Url." />

          <Annotation Term="Core.IsURL" />

        </Property>

      </ComplexType>

      <ComplexType Name="Http" BaseType="Auth.Authorization">

        <Property Name="Scheme" Type="Edm.String" Nullable="false">

          <Annotation Term="Core.Description" String="HTTP Authorization scheme to be used in the Authorization header, as per RFC7235" />

        </Property>

        <Property Name="BearerFormat" Type="Edm.String">

          <Annotation Term="Core.Description" String="Format of the bearer token" />

        </Property>

      </ComplexType>

      <ComplexType Name="OAuthAuthorization" BaseType="Auth.Authorization" Abstract="true">

        <Property Name="Scopes" Type="Collection(Auth.AuthorizationScope)">

          <Annotation Term="Core.Description" String="Available scopes" />

        </Property>

        <Property Name="RefreshUrl" Type="Edm.String">

          <Annotation Term="Core.Description" String="Refresh Url" />

          <Annotation Term="Core.IsURL" />

        </Property>

      </ComplexType>

      <ComplexType Name="OAuth2ClientCredentials" BaseType="Auth.OAuthAuthorization">

        <Property Name="TokenUrl" Type="Edm.String" Nullable="false">

          <Annotation Term="Core.Description" String="Token Url" />

          <Annotation Term="Core.IsURL" />

        </Property>

      </ComplexType>

      <ComplexType Name="OAuth2Implicit" BaseType="Auth.OAuthAuthorization">

        <Property Name="AuthorizationUrl" Type="Edm.String" Nullable="false">

          <Annotation Term="Core.Description" String="Authorization URL" />

          <Annotation Term="Core.IsURL" />

        </Property>

      </ComplexType>

      <ComplexType Name="OAuth2Password" BaseType="Auth.OAuthAuthorization">

        <Property Name="TokenUrl" Type="Edm.String" Nullable="false">

          <Annotation Term="Core.Description" String="Token Url" />

          <Annotation Term="Core.IsURL" />

        </Property>

      </ComplexType>

      <ComplexType Name="OAuth2AuthCode" BaseType="Auth.OAuthAuthorization">

        <Property Name="AuthorizationUrl" Type="Edm.String" Nullable="false">

          <Annotation Term="Core.Description" String="Authorization URL" />

          <Annotation Term="Core.IsURL" />

        </Property>

        <Property Name="TokenUrl" Type="Edm.String" Nullable="false">

          <Annotation Term="Core.Description" String="Token Url" />

          <Annotation Term="Core.IsURL" />

        </Property>

      </ComplexType>

      <ComplexType Name="AuthorizationScope">

        <Property Name="Scope" Type="Edm.String" Nullable="false">

          <Annotation Term="Core.Description" String="Scope name" />

        </Property>

        <Property Name="Description" Type="Edm.String">

          <Annotation Term="Core.Description" String="Description of the scope" />

        </Property>

      </ComplexType>

      <ComplexType Name="ApiKey" BaseType="Auth.Authorization">

        <Property Name="KeyName" Type="Edm.String" Nullable="false">

          <Annotation Term="Core.Description" String="The name of the header or query parameter" />

        </Property>

        <Property Name="Location" Type="Auth.KeyLocation" Nullable="false">

          <Annotation Term="Core.Description" String="Whether the API Key is passed in the header or as a query option" />

        </Property>

      </ComplexType>

      <EnumType Name="KeyLocation">

        <Member Name="Header">

          <Annotation Term="Core.Description" String="API Key is passed in the header" />

        </Member>

        <Member Name="QueryOption">

          <Annotation Term="Core.Description" String="API Key is passed as a query option" />

        </Member>

        <Member Name="Cookie">

          <Annotation Term="Core.Description" String="API Key is passed as a cookie" />

        </Member>

      </EnumType>

[17:47] Michael Pizzo: ODATA-1145 proposal:

1) Add the following property to the Auth.Authorization complex type:

<Property Name="Name" Type="Edm.String">

  <Annotation Term="Core.Description" String="Name that can be used to reference the authorization flow."/>

</Property>

2) Add the following new complex type to the Auth vocabulary:

<ComplexType Name="SecurityScheme">

  <Property Name="AuthorizationSchemeName" Type="Edm.String">

    <Annotation Term="Core.Description" String="The name of a required authorization scheme"/>

  </Property>

  <Property Name="RequiredScopes" Type="Collection(Edm.String">

    <Annotation Term="Core.Description" String="The names of scopes required from this authorization scheme."/>

  </Property>

<ComplexType>

3) Add the following property to the new HTTPRequest type proposed in ODATA-884:

<Property Name="SecuritySchemes" Type="Collection(Auth.SecurityScheme)">

  <Annotation Term="Core.Description" String="At least one of the specified security schemes are required to make the request."/>

</Property>

[17:58] Michael Pizzo: Add proposal:

4) Add the following term that can be applied to an EntityContainer.

<Term Name="SecuritySchemes" Type="Collection(Auth.SecurityScheme)" AppliesTo="EntityContainer">

  <Annotation Term="Core.Description" String="At least one of the specified security schemes are required to make a request against the service."/>

</Term>

[18:01] Michael Pizzo: Updated #3:

3) Add the following property to the new HTTPRequest type proposed in ODATA-884:

<Property Name="SecuritySchemes" Type="Collection(Auth.SecurityScheme)">

  <Annotation Term="Core.Description" String="At least one of the specified security schemes are required to make the request. This overrides any SecuritySchemes specified on the EntityContainer."/>

</Property>

[18:03] Michael Pizzo: I move to resolve ODATA-1145 as proposed.

[18:03] George Ericson (Dell): I second 1145

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

[18:04] Ralf Handl (SAP SE): ii.ODATA-1140 Add details to HTTPResponseCode term

[18:16] Michael Pizzo: Note: this would be useful for documentation; not particularly useful for clients at runtime.

Services do tend to have service-specific error codes and descriptions, but there are typically a lot of them so documenting for each request may be verbose.

[18:16] Ralf Handl (SAP SE): ODATA-1140 is OPEN

[18:20] Michael Pizzo: It doesn't appear from a very quick read that OpenAPI has a similar concept in their Response object.

[18:24] Michael Pizzo: Renamed ODATA-884 to "Enable enumerating the valid requests and responses for a particular resource."

[18:27] Michael Pizzo: I move we move ODATA-1140 out of 4.01 CS02 to some undefined future

[18:27] Ralf Handl (SAP SE): I second

[18:27] Ralf Handl (SAP SE): No objection, motion passes

[18:27] Ralf Handl (SAP SE): iii.ODATA-1132 Propagation of NavigationRestrictions

[18:28] Ralf Handl (SAP SE): Clarify whether/how navigation restrictions "propagate".

Assume we have

- Order entity related to single Customer entity

- Customer entity related to multiple Address entities

- a navigation restriction on Customers entity set which lists Addresses as filterable:false.

Now a client knows that it cannot filter Customers by Addresses.

Should a client assume that it also cannot filter Orders by Customer/Addresses?

Or would the service have to explicitly declare navigation restrictions for all entity sets with navigation paths ending in Customer/Addresses?

[18:28] Ted Jones (Red Hat): Need to drop for another call.. see you next week.

[18:28] Ralf Handl (SAP SE): @Ted: thanks, see you next week

[18:30] Ralf Handl (SAP SE): Mike: propagation would require a navigation property binding to be able to identify another source for navigation restrictions

[18:30] Ralf Handl (SAP SE): Mike: restrictions may depend on the path

[18:32] Ralf Handl (SAP SE): Question: is it easier for the server to produce more restrictions, or for the client to walk through all possible navigation paths

[18:32] Ralf Handl (SAP SE): George: put burden on service

[18:32] Ralf Handl (SAP SE): Mike: makes $metadata more verbose

[18:44] Michael Pizzo: In all but the most hypothetical situations, the client would be safe in assuming that restrictions on the entity set applied to restrictions on navigation properties referencing the entity set.

[18:45] Michael Pizzo: Proposal: State that clients can assume that restrictions specified on an entity set are valid whether the request is to the entity set or through a navigation property bound to that entity set.

[18:46] Ralf Handl (SAP SE): Ralf: means restrictions propagate if there is a nav prop binding

[18:50] Ralf Handl (SAP SE): Hubert: can we override a "propagated" restriction?

[18:50] Michael Pizzo: Service could specify a different set of restrictions specific to a path, in which case any specified restrictions take precedence.

[18:51] Michael Pizzo: Updated (working) proposal:

State that clients can assume that restrictions specified on an entity set are valid whether the request is to the entity set or through a navigation property bound to that entity set.  Service could specify a different set of restrictions specific to a path, in which case any specified restrictions take precedence.

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

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

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

[18:53] Ralf Handl (SAP SE): iv.ODATA-1121 Add FilterExpressionType values "MultiRange" and "MultiRangeOrSearchExpression"

[18:54] Ralf Handl (SAP SE): Filter _expression_ restrictions where introduced in ODATA-816 to express restricted filter capabilities on individual properties that can only be used in equality comparison or interval comparison.

Similar to MultiValue being multiple SingleValues joined by OR, MultiRange is multiple SingleRanges joined by OR, with a slight generalization: in addition to closed intervals also half-open and open intervals are allowed, as well as degenerate intervals (closed intervals with identical lower and upper boundary can be expressed simply via EQ).

This means that MultiRange subsumes SingleRange as well as MultiValue and SingleValue.

For string-valued properties this can be extended to include multiple SearchExpressions: MultiRangeOrSearchExpression, allowing to OR zero or more startswith, endswith, or contains functions comparing the property to a string literal.

These expressions are all fairly simple, including a property, a literal value, and at most one level of parentheses. They represent expressions that can be constructed by typical "extended search" forms that allow to pick the comparison operator and enter the comparison value (or two values for "between").

[18:56] Ralf Handl (SAP SE): Add new allowed values

  <Record>

    <PropertyValue Property="Value" String="MultiRange" />

    <Annotation Term="Core.Description" String="Property can be compared to a union of one or more closed, half-open, or open intervals" />

    <Annotation Term="Core.LongDescription" String="The filter _expression_ for this property consists of one or more interval expressions combined by OR. A single interval _expression_ is either a single comparison of the property and a literal value with eq, le, lt, ge, or gt, or pair of boundaries combined by AND and enclosed in parentheses. The lower boundary is either ge or gt, the upper boundary either le or lt." />

  </Record>

  <Record>

    <PropertyValue Property="Value" String="MultiRangeOrSearchExpression" />

    <Annotation Term="Core.Description" String="Property can be compared to a union of zero or more closed, half-open, or open intervals plus zero or more simple string patters" />

    <Annotation Term="Core.LongDescription" String="The filter _expression_ for this property consists of one or more interval expressions or string comparison functions combined by OR. See MultiRange for a definition of an interval _expression_. See SearchExpression for the allowed string comparison functions." />

  </Record>

[18:59] Ralf Handl (SAP SE): a lt 5 or (a ge 9 and a le 11)

[19:00] Ralf Handl (SAP SE): a lt 'Hugo' or startswith(a, 'Fred')

[19:02] Ralf Handl (SAP SE): ODATA-1121 is OPEN

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

a.Thursday February 15, 2018 during 8-10 am PST

b.Thursday February 22, 2018 during 8-10 am PST

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

[19:02] 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. Februar 2018 13:55
To: odata@lists.oasis-open.org
Subject: [CAUTION] [odata] Agenda for OData TC meeting on 2018-02-08

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

2. Approve agenda [8:05 am PT]

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

Minutes from February 01, 2018 TC meeting: https://www.oasis-open.org/committees/download.php/62433/odata-meeting-201_on-20180201-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: NEW or OPEN

i. ODATA-1146 Clarify that an enumeration type must have at least one member

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

Vocabularies: NEW or OPEN

i. ODATA-1145 Align Authorization vocabulary with OpenAPI V3

ii. ODATA-1140 Add details to HTTPResponseCode term

iii. ODATA-1132 Propagation of NavigationRestrictions

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

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

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

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

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

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

6. Next meetings [9:50 am PT]

Thursday February 15, 2018 during 8-10 am PST
Thursday February 22, 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

odata message