RE: [odata] Agenda for OData TC meeting on 2017-04-27

[17:00] Ralf Handl (SAP SE): Weekly meeting of the OData TC.

Dial-in information: https://www.oasis-open.org/apps/org/workgroup/odata/download.php/56760/latest

Online chat room: http://webconf.soaphub.org/conf/room/odatatc

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

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

[17:03] Ralf Handl (SAP SE): Voting Members: 6 of 11 (54%) (used for quorum calculation)

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

[17:06] Ralf Handl (SAP SE): 1.Roll call [8:00 am PT]

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

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

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

a.Minutes from April 20, 2017 TC meeting: https://www.oasis-open.org/committees/download.php/60560/odata-meeting-171_on-20170420-minutes.html

[17:08] Ralf Handl (SAP SE): ODATA-1066 to be added to agenda item 5.b

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

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

a.Minutes from April 20, 2017 TC meeting: https://www.oasis-open.org/committees/download.php/60560/odata-meeting-171_on-20170420-minutes.html

[17:09] Ralf Handl (SAP SE): Section 5.2.1 Ralf: Walkthrough stopped before XXXXXX

[17:10] Ralf Handl (SAP SE): change to "stopped in 13.1.1 OData 4.0 Minimal Conformance"

[17:10] Ralf Handl (SAP SE): Minutes are approved with this correction

[17:10] 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.V4.01 [8:20 am PT]

[17:11] Ralf Handl (SAP SE): b.Issues for V4.01_CSD02 ready for resolution

[17:11] Ralf Handl (SAP SE): i.ODATA-1005 Make sure we have capabilities for all new 4.01 functionality - just a reminder

[17:11] Ralf Handl (SAP SE): ii.ODATA-1065 Generalize Edm.AnyPath to be a path to any model element and rename it to Edm.ModelElementPath

[17:12] Ralf Handl (SAP SE): Mike likes it because it says what the path is targeting

[17:13] Ralf Handl (SAP SE): Martin agrees

[17:13] Michael Pizzo: I move we re-resolve ODATA-1065 with the new name, as proposed.

[17:13] Martin Zurmuehl (SAP SE): I second

[17:14] Ralf Handl (SAP SE): ODATA-1065 is re-resolved as proposed

[17:15] Ralf Handl (SAP SE): iii. https://issues.oasis-open.org/browse/ODATA-1066 - Consider supporting optional operation parameters

[17:25] Ralf Handl (SAP SE): ODATA-1066 is OPEN

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

1) Add a new OptionalParameter annotation:

  <Term Name="OptionalParameter" Type="Core.Tag" DefaultValue="true" AppliesTo="Parameter">

    <Annotation Term="Core.Description" String="Supplying a value for the parameter is optional." />

  </Term>

2) All parameters marked optional must come after any parameters not marked optional

3) Keep existing rules for function overloads.

4) In function resolution:

    I) If the set of specified params exactly matches a function overload, chose it.

    ii) If the set of specified params matches a subset of parameters that includes all required parameters for exactly one function overload, choose it

   iii) otherwise, return 400 with an error stating that request was ambiguous

[17:53] Michael Pizzo: With current proposal, you can have multiple overloads with different sets of optional parameters, but you may get a 400 if there is ambiguity in resolving (i.e., case iii)

[17:53] Michael Pizzo: Alternate proposal would be to allow at most one overload per binding type that specified optional parameters.

[17:53] Michael Pizzo: This would eliminate case iii...

[17:56] Michael Pizzo: Could also require that no overloads for the same binding parameter use the same name for any optional parameters.

[17:57] Michael Pizzo: (and require uniqueness across required parameters)

[17:57] Michael Pizzo: Alternate: services should avoid ambiguity; what happens if there is ambiguity is specific to the service.

[18:13] Michael Pizzo: If we defined something like:

[18:13] Michael Pizzo: <ComplexType Name="OptionalParameterType" Type="Edm.Untyped">

  <Property Name="IsOptional" Type="Edm.Boolean" DefaultValue = "true"/>

  <Property Name="DefaultValue" Type="Edm.Untyped">

    <Annotation Term="Core.Description" String="Default value for an optional parameter" />

  </Property>

</Term>

[18:14] Michael Pizzo: If we defined:

<ComplexType Name="OptionalParameterType">

  <Property Name="IsOptional" Type="Edm.Boolean" DefaultValue = "true"/>

  <Property Name="DefaultValue" Type="Edm.Untyped">

    <Annotation Term="Core.Description" String="Default value for an optional parameter" />

  </Property>

</Term>

[18:14] Michael Pizzo: <Term Name="OptionalParameter" Type="Core.OptionalParameterType" AppliesTo="Parameter">

    <Annotation Term="Core.Description" String="Supplying a value for the parameter is optional." />

  </Term>

[18:14] Michael Pizzo: <Annotation Term="OptionalParameter"/>

[18:15] Michael Pizzo: This way to specify a default value:

<Annotation Term="OptionalParameter">

<Record>

<PropertyValue Name="IsOptional" Bool="true"/>

<PropertyValue Name="DefaultValue" Bool="true"/>

</Record>

</Annotation>

[18:17] Michael Pizzo: If we defined default value as a string (as we do for the defaultvalue facet on a property):

<ComplexType Name="OptionalParameterType">

  <Property Name="IsOptional" Type="Edm.Boolean" DefaultValue = "true"/>

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

    <Annotation Term="Core.Description" String="Default value for an optional parameter" />

  </Property>

</Term>

Then the string would be an _expression_ evaluated by the client:

<Annotation Term="OptionalParameter">

<Record>

<PropertyValue Name="IsOptional" Bool="true"/>

<PropertyValue Name="DefaultValue" String="true"/>

</Record>

</Annotation>

[18:22] Ralf Handl (SAP SE): <Term Name="DerivedDefaultValue" Type="Edm.String" AppliesTo="Property">

        <!-- <Annotation Term="Common.IsFunctionImport" /> -->

        <Annotation Term="Core.Description">

          <String>Function import to derive a default value for the property from a given context.</String>

        </Annotation>

        <Annotation Term="Core.LongDescription">

          <String>

            Function import has two parameters of complex types:

            - `parameters`, a structure resembling the entity type the parameter entity set related to the entity set of the annotated property

            - `properties`, a structure resembling the type of the entity set of the annotated property

            The return type must be of the same type as the annotated property.

            Arguments passed to the function import are used as context for deriving the default value.

            The function import returns this default value, or null in case such a value could not be determined.

          </String>

        </Annotation>

      </Term>

[18:30] Michael Pizzo: <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>

[18:37] Michael Pizzo: Proposal:

1) Add a new OptionalParameter annotation:

  <Term Name="OptionalParameter" Type="Core.OptionalParameterType" AppliesTo="Parameter">

    <Annotation Term="Core.Description" String="Supplying a value for the parameter is optional." />

  </Term>

<ComplexType Name="OptionalParameterType">

  <Property Name="IsOptional" Type="Edm.Boolean" DefaultValue = "true"/>

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

    <Annotation Term="Core.Description" String="Default value for an optional parameter, using the same rules for the default value facet of a property." />

  </Property>

</Term>

2) All parameters marked optional must come after any parameters not marked optional

3) Keep existing rules for function overloads.

4) In function resolution:

    I) If the set of specified params exactly matches a function overload, chose it.

    ii) If the set of specified params matches a subset of parameters that includes all required parameters for exactly one function overload, choose it

5) Services should avoid ambiguity. If there is ambiguity then services may return 400 with an error stating that request was ambiguous

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

[18:39] Martin Zurmuehl (SAP SE): I second

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

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

a.Thursday May 04, 2017 during 7-10 am PDT  already confirmed  one hour earlier, one hour longer

[18:59] Ralf Handl (SAP SE): a.Thursday May 04, 2017 during 8-11 am PDT one hour longer

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

[18:59] 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, 26. April 2017 10:33
To: odata@lists.oasis-open.org
Subject: [odata] Agenda for OData TC meeting on 2017-04-27

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

2. Approve agenda [8:05 am PT]

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

a. Minutes from April 20, 2017 TC meeting: https://www.oasis-open.org/committees/download.php/60560/odata-meeting-171_on-20170420-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. V4.01 [8:20 am PT]

a. Document walkthrough