RE: Agenda for OData TC meeting on 2018-04-19 - chat transcript

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

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

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

- Thursday, 19 April 2018, 08:00am to 10:00am PDT

  - i.e. 2018-04-19 17:00 to 19:00 CEST (UTC+2)

  - other timezone? Try eg.:

   - https://www.timeanddate.com/worldclock/meetingdetails.html?year=2018&month=4&day=19&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 April 26, 2018 during 8-10 am PDT (17:00-18:00 CEST)

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

- Thursday May 03, 2018 during 8-10 am PDT (17:00-19:00 CEST)

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

Agenda-Draft E-Mail URL:

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

Minutes Draft Public URLs (previous meetings):

- URL = "" href="https://www.oasis-open.org/committees/download.php/62930/odata-meeting-210_on-20180412-minutes-informal.html" target="_blank">https://www.oasis-open.org/committees/download.php/62930/odata-meeting-210_on-20180412-minutes-informal.html

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

 - 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 #211):

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

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

2. Approve agenda [8:05 am PT]

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

 3.1 Minutes from April 05, 2018 TC meeting:

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

   none

5. Timeline

 5.1 Vocabularies

   5.1.1 Publish CSD02 soon, or rather continue with issue processing and publishing on GitHub?

 5.2 OData to OpenAPI Mapping

   5.2.1 Publish CND02 soon, or rather postpone it after REST Profile and/or Compact JSON?

 5.3 REST Profile / Essential OData

   5.3.1 Before or after Compact JSON?

 5.4 Compact JSON

   5.4.1 Before or after REST Profile?

   5.4.2 Hubert has contributed a proposal

         URL = "" href="https://www.oasis-open.org/committees/document.php?document_id=62898&wg_abbrev=odata" target="_blank">https://www.oasis-open.org/committees/document.php?document_id=62898&wg_abbrev=odata 

6. Issues [8:20 am PT]

 6.1 V4.01: NEW or OPEN

   i.    ODATA-1171 Consider using matrix parameters for filter segments

   ii.    ODATA-1168 Clarify the use of ETags for Avoiding Update Conflicts

   iii.    ODATA-1163 A Case for Common Expressions

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

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

 6.2 Vocabularies: NEW or OPEN with concrete proposal

   i.    ODATA-1167 Add way to specify which batch formats (if any) are supported by a service

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

 6.3 Data Aggregation: NEW or OPEN

   i.    ODATA-1169 Transformation for nesting the result of another transformation within a single entity

   ii.    ODATA-1162 Fix data type in example model

   iii.    ODATA-1161 Clarify how to process hybrid results of a transformation in subsequent transformations

   iv.    ODATA-1160 Clarify example 66 in section 7.5

   v.    ODATA-1159 Clarify context URLs for aggregated result sets

   vi.    ODATA-1158 Transformations for limiting the number of entities in the result of a $apply transformation

   vii.    ODATA-1157 Transformation for sorting entities created by a $apply transformation

   viii.    ODATA-1137 Clarify type information for dynamic properties in the aggregated result set

   ix.    ODATA-1073 Conformance section references wrong annotation term

   x.    ODATA-1068 3.12 Transformation expand: require at least two parameters, with innermost expansion requiring a filter()

   xi.    ODATA-1041 Broaden definitions of transformations topcount and bottomcount

   xii.    (and 16 more)

7. Next meetings [9:50 am PT]

 7.1 Thursday April 26, 2018 during 8-10 am PDT (17:00-19:00 CEST)?

 7.2 Thursday May 03, 2018 during 8-10 am PDT (17:00-19:00 CEST)

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

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

Room Information:

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

- Thursday, 19 April 2018, 08:00am to 10:00am PDT

  - i.e. 2018-04-19 17:00 to 19:00 CEST (UTC+2)

  - other timezone? Try eg.:

   - https://www.timeanddate.com/worldclock/meetingdetails.html?year=2018&month=4&day=19&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 April 26, 2018 during 8-10 am PDT (17:00-18:00 CEST)

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

- Thursday May 03, 2018 during 8-10 am PDT (17:00-19:00 CEST)

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

Agenda-Draft E-Mail URL:

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

Minutes Draft Public URLs (previous meetings):

- URL = "" href="https://www.oasis-open.org/committees/download.php/62930/odata-meeting-210_on-20180412-minutes-informal.html" target="_blank">https://www.oasis-open.org/committees/download.php/62930/odata-meeting-210_on-20180412-minutes-informal.html

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

 - 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 #211):

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

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

2. Approve agenda [8:05 am PT]

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

 3.1 Minutes from April 05, 2018 TC meeting:

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

   none

5. Timeline

 5.1 Vocabularies

   5.1.1 Publish CSD02 soon, or rather continue with issue processing and publishing on GitHub?

 5.2 OData to OpenAPI Mapping

   5.2.1 Publish CND02 soon, or rather postpone it after REST Profile and/or Compact JSON?

 5.3 REST Profile / Essential OData

   5.3.1 Before or after Compact JSON?

 5.4 Compact JSON

   5.4.1 Before or after REST Profile?

   5.4.2 Hubert has contributed a proposal

         URL = "" href="https://www.oasis-open.org/committees/document.php?document_id=62898&wg_abbrev=odata" target="_blank">https://www.oasis-open.org/committees/document.php?document_id=62898&wg_abbrev=odata 

6. Issues [8:20 am PT]

 6.1 V4.01: NEW or OPEN

   i.    ODATA-1171 Consider using matrix parameters for filter segments

   ii.    ODATA-1168 Clarify the use of ETags for Avoiding Update Conflicts

   iii.    ODATA-1163 A Case for Common Expressions

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

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

 6.2 Vocabularies: NEW or OPEN with concrete proposal

   i.    ODATA-1167 Add way to specify which batch formats (if any) are supported by a service

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

 6.3 Data Aggregation: NEW or OPEN

   i.    ODATA-1169 Transformation for nesting the result of another transformation within a single entity

   ii.    ODATA-1162 Fix data type in example model

   iii.    ODATA-1161 Clarify how to process hybrid results of a transformation in subsequent transformations

   iv.    ODATA-1160 Clarify example 66 in section 7.5

   v.    ODATA-1159 Clarify context URLs for aggregated result sets

   vi.    ODATA-1158 Transformations for limiting the number of entities in the result of a $apply transformation

   vii.    ODATA-1157 Transformation for sorting entities created by a $apply transformation

   viii.    ODATA-1137 Clarify type information for dynamic properties in the aggregated result set

   ix.    ODATA-1073 Conformance section references wrong annotation term

   x.    ODATA-1068 3.12 Transformation expand: require at least two parameters, with innermost expansion requiring a filter()

   xi.    ODATA-1041 Broaden definitions of transformations topcount and bottomcount

   xii.    (and 16 more)

7. Next meetings [9:50 am PT]

 7.1 Thursday April 26, 2018 during 8-10 am PDT (17:00-19:00 CEST)?

 7.2 Thursday May 03, 2018 during 8-10 am PDT (17:00-19:00 CEST)

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

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

[17:01] Ralf Handl (SAP SE): Voting Members: 5 of 11 (45%) (used for quorum calculation)

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

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

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

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

[17:04] Ralf Handl (SAP SE): New V4.01 issue: ODATA-1172 - 4.5.3: use $schemaversion query option instead of SchemaVersion header

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

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

a.Minutes from April 05, 2018 TC meeting: https://www.oasis-open.org/committees/download.php/62839/odata-meeting-209_on-20180405-minutes.html

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

[17:06] 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:06] Ralf Handl (SAP SE): 5.Timeline

a.Vocabularies

i.Publish CSD02 soon, or rather continue with issue processing and publishing on GitHub?

b.OData to OpenAPI Mapping

i.Publish CND02 soon, or rather postpone it after REST Profile and/or Compact JSON?

c.REST Profile / Essential OData

i.Before or after Compact JSON?

d.Compact JSON

i.Before or after REST Profile?

ii.Hubert has contributed a proposal

1.https://www.oasis-open.org/committees/document.php?document_id=62898&wg_abbrev=odata

[17:09] Ralf Handl (SAP SE): George: no pushback from Redfish on Github as publishing point for vocabularies

[17:10] Ralf Handl (SAP SE): Mike: no reason to publish legacy documents

[17:12] Michael Pizzo: I move that we continue processing Vocabulary issues through GitHub and do not plan to publish a legacy CSD02 document for the accumulated changes.

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

[17:12] Ralf Handl (SAP SE): No objection, motion passes

[17:16] Ralf Handl (SAP SE): b.OData to OpenAPI Mapping

[17:17] Ralf Handl (SAP SE): Mike: review latest changes next

[17:17] Ralf Handl (SAP SE): Open issues affecting OpenAPI Mapping:

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

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

[17:20] Ralf Handl (SAP SE): Mike to follow up on ODATA-884

[17:20] Ralf Handl (SAP SE): Ralf to amend ODATA-1099 with schema/examples for custom header/option values

[17:27] Ralf Handl (SAP SE): Example values in primitive property definitions in OpenAPI are used by Swagger UI for drawing example payloads

[17:28] Ralf Handl (SAP SE): See http://petstore.swagger.io/?url="">

[17:28] Ralf Handl (SAP SE): Example Value:

{

  "value": [

    {

      "UserName": "string",

      "FirstName": "string",

      "LastName": "string",

      "Emails": [

        "string"

      ],

      "AddressInfo": [

        {

          "Address": "string",

          "City": {

            "CountryRegion": "string",

            "Name": "string",

            "Region": "string"

          }

        }

      ],

      "Concurrency": "42",

      "Friends": [

        null

      ],

      "Trips": [

        {

          "TripId": 0,

          "ShareId": "01234567-89ab-cdef-0123-456789abcdef",

          "Description": "string",

          "Name": "string",

          "Budget": 3.14,

          "StartsAt": "2017-04-13T15:51:04Z",

          "EndsAt": "2017-04-13T15:51:04Z",

          "Tags": [

            "string"

          ],

          "Photos": [

            {

              "Id": "42",

              "Name": "string"

            }

          ],

          "PlanItems": [

            {

              "PlanItemId": 0,

              "ConfirmationCode": "string",

              "StartsAt": "2017-04-13T15:51:04Z",

              "EndsAt": "2017-04-13T15:51:04Z",

              "Duration": "P4DT15H51M04.217S"

            }

          ]

        }

      ]

    }

  ]

}

[17:35] Ralf Handl (SAP SE): After resolving these two issues update document and walk through again

[17:36] Ralf Handl (SAP SE): Next: REST Profile or Compact JSON

[17:37] Ralf Handl (SAP SE): "REST Profile" or "OData Light" or "Essential OData": Overview/cookbook for adopting OData step by step

[17:38] Ralf Handl (SAP SE): Option: don't use "OData" to avoid confusion around data-centric/non-data-centric APIs

[17:41] Ralf Handl (SAP SE): Idea: OpenAPI instead of CSDL as metadata/service description

[17:43] George Ericson (Dell): RestLite doesn't have any hits

[17:46] Ralf Handl (SAP SE): Unfortunately it does:

- GitHub - theintencity/restlite: Light-weight RESTful server tools in Python

- GitHub - ncribt/restlite: A _javascript_ Microframework to make Single ...

[17:46] Ralf Handl (SAP SE): and more

[17:49] Ralf Handl (SAP SE): Compact JSON: walk-through next week

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

[17:52] Ralf Handl (SAP SE): ODATA-1172 - 4.5.3: use $schemaversion query option instead of SchemaVersion header

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

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

Current text: 

---- 

If the URI references a metadata document (that is, its not just a fragment), and refers to a specific version of that metadata, then the object or name/value pair MUST also be annotated with the Core.SchemaVersion annotation, defined in [OData-VocCore], to indicate the version of the metadata document containing the corresponding version of the type. For streamed JSON responses, this annotation MUST immediately follow the type annotation. If the Core.SchemaVersion annotation is present, the Core.SchemaVersion header, defined in [OData-Protocol], SHOULD be used when retrieving the referenced metadata document. 

---- 

Change to 

---- 

If the URI references a metadata document (that is, its not just a fragment), it MAY refer to a specific version of that metadata document using the $schemaversion system query option defined in [OData-Protocol]. 

---- 

That is: no need for an additional annotation with Core.SchemaVersion, just follow the @odata.type URL.

[17:54] Ralf Handl (SAP SE): ODATA-1172 is OPEN

[17:55] Michael Pizzo: I move we resolve ODATA-1172 as proposed.

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

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

[17:55] Ralf Handl (SAP SE): i.ODATA-1171 Consider using matrix parameters for filter segments

[17:57] Michael Pizzo: Current filter segment syntax: Customers/$filter=@q/myns.action?$@q=Age gt 18

[17:59] Michael Pizzo: Syntax using Matrix Parameters: Customers;$filter=@q?$@q=name eq 'Smith'

[18:00] Michael Pizzo: Customers;$filter=@q/myns.action?$@q=name eq 'Smith'

[18:04] Ralf Handl (SAP SE): According to "Restful Java with JAX-RS 2.0", a request like "GET /mercedes/e55;color=black/2006/interior;color=tan" would have an ambiguous definition of the color matrix param.

[18:08] Ralf Handl (SAP SE): ODATA-1171 is OPEN

[18:09] Ralf Handl (SAP SE): Mike to get feedback from implementation team regarding concerns of IETF specifications and HTTP-related tools being unable to cope with semicolons in URL paths

[18:11] Ralf Handl (SAP SE): Mike: don't have both syntax variants, decide for exactly one soon

[18:18] Ralf Handl (SAP SE): iii.ODATA-1163 A Case for Common Expressions

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

The case function has the following signatures: 

_expression_ case(Edm.Boolean:_expression_, ..., Edm.Boolean:_expression_) 

_expression_ case(Edm.Boolean:_expression_, ..., Edm.Boolean:_expression_,_expression_) 

Each Edm.Boolean:_expression_ parameter is a tuple separated by a colon, where the first component evaluates to a Boolean value, and the second component may be an _expression_ of any type. 

The case function returns the _expression_ value of the leftmost parameter, whose first component evaluates to true. If none of the parameters match, case returns null, unless the last parameter is an _expression_, whose value is returned otherwise. 

If all parameters are of the same type, the type of the _expression_ is of that type. If all parameter expressions are of numeric type, the return value has a numeric type capable of representing any of these expressions. Otherwise, the return value is the result of casting the _expression_ of the matching parameter to Edm.String.

[18:20] Michael Pizzo: (From ODATA-1171: George: Note that putting a filter in the Path is problematic for some implementations that serve hard-coded paths or do routing based on fixed path templates. Also, it breaks the hypermedia-driven model of services providing URLs and the client only affecting query string parameters.)

[18:22] Ralf Handl (SAP SE): Mike: agree that type-compatible result expressions lead to that type using existing OData rules

[18:23] Michael Pizzo: From 2018-4-5: All parameter expressions must be compatible. If all parameters are of the same type, the type of the case _expression_ is of that type. If all parameter expressions are of numeric type, then the type of the case _expression_ is a numeric type capable of representing any of these expressions according to standard type promotion rules. If types of parameter expressions are not compatible, then they must be cast to compatible types.

[18:28] Ralf Handl (SAP SE): Mike: could use Edm.Untyped instead of forcing cast in case the parameter expressions aren't compatible

[18:28] Ralf Handl (SAP SE): Mike: can start with the stricter rule and relax it later to resulting in Edm.Untyped.

[18:31] Ralf Handl (SAP SE): George: be strict and make client responsible for formulating consistent requests

[18:44] Ralf Handl (SAP SE): Side-discussion on wording in CSDL "14.4.11 Null", George to open separate issue with proposal for improved wording

[18:50] Michael Pizzo: One option: Clients SHOULD ensure that the type of the _expression_ is well defined. Services MAY support case expressions containing parameters of different types, in which case the type of the _expression_ is UnTyped.

[18:53] George Ericson (Dell): OData-1173 addresses 14.4.11

[18:53] Ralf Handl (SAP SE): @George: thanks!

[18:54] Michael Pizzo: Revised proposal: The client SHOULD ensure that all expressions are compatible. If all parameters are of the same type, the type of the case _expression_ is of that type. If all parameter expressions are of numeric type, then the type of the case _expression_ is a numeric type capable of representing any of these expressions according to standard type promotion rules.

Services MAY support case expressions containing parameters of incompatible types, in which case the _expression_ is treated as Edm.Untyped.

[18:55] Ralf Handl (SAP SE): Perfect

[19:01] Michael Pizzo: Revised last statement: Services MAY support case expressions containing parameters of incompatible types, in which case the _expression_ is treated as Edm.Untyped and its value is the type of the parameter _expression_ taken selected by the case statement..

[19:03] Michael Pizzo: Reworded: 

The client SHOULD ensure that all parameter expressions are compatible. If all parameter expressions are of the same type, the type of the case _expression_ is of that type. If all parameter expressions are of numeric type, then the type of the case _expression_ is a numeric type capable of representing any of these expressions according to standard type promotion rules.

Services MAY support case expressions containing parameters of incompatible types, in which case the _expression_ is treated as Edm.Untyped and its value is the type of the parameter _expression_ selected by the case statement.

[19:04] Mark Biamonte (Progress): I like this latest proposal

[19:04] Ralf Handl (SAP SE): Me too

[19:07] Mark Biamonte (Progress): I move that OData-1163 be resolved as proposed

[19:07] Michael Pizzo: I second

[19:07] Ralf Handl (SAP SE): ODATA-1163 is RESOLVED with the amended proposal

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

a.Thursday April 26, 2018 during 8-10 am PDT (17:00-19:00 CEST)

b.Thursday May 03, 2018 during 8-10 am PDT (17:00-19:00 CEST)

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

[19:08] 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, 17. April 2018 13:54
To: odata@lists.oasis-open.org
Subject: [CAUTION] [odata] Agenda for OData TC meeting on 2018-04-19

 

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

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

 

2.        Approve agenda [8:05 am PT]

 

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

1. Minutes from April 05, 2018 TC meeting: https://www.oasis-open.org/committees/download.php/62839/odata-meeting-209_on-20180405-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.        Timeline

1. Vocabularies

                                  i.    Publish CSD02 soon, or rather continue with issue processing and publishing on GitHub?

2. OData to OpenAPI Mapping

                                  i.    Publish CND02 soon, or rather postpone it after REST Profile and/or Compact JSON?

3. REST Profile / Essential OData

                                  i.    Before or after Compact JSON?

4. Compact JSON

                                  i.    Before or after REST Profile?

                                 ii.    Hubert has contributed a proposal

1. https://www.oasis-open.org/committees/document.php?document_id=62898&wg_abbrev=odata

 

6.        Issues [8:20 am PT]

1. V4.01: NEW or OPEN

                                  i.    ODATA-1171 Consider using matrix parameters for filter segments

                                 ii.    ODATA-1168 Clarify the use of ETags for Avoiding Update Conflicts

                                iii.    ODATA-1163 A Case for Common Expressions

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

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

 

2. Vocabularies: NEW or OPEN with concrete proposal

                                  i.    ODATA-1167 Add way to specify which batch formats (if any) are supported by a service

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

 

3. Data Aggregation: NEW or OPEN

                                  i.    ODATA-1169 Transformation for nesting the result of another transformation within a single entity

                                 ii.    ODATA-1162 Fix data type in example model

                                iii.    ODATA-1161 Clarify how to process hybrid results of a transformation in subsequent transformations

                                iv.    ODATA-1160 Clarify example 66 in section 7.5

                                 v.    ODATA-1159 Clarify context URLs for aggregated result sets

                                vi.    ODATA-1158 Transformations for limiting the number of entities in the result of a $apply transformation

                               vii.    ODATA-1157 Transformation for sorting entities created by a $apply transformation

                              viii.    ODATA-1137 Clarify type information for dynamic properties in the aggregated result set

                                ix.    ODATA-1073 Conformance section references wrong annotation term

                                 x.    ODATA-1068 3.12 Transformation expand: require at least two parameters, with innermost expansion requiring a filter()

                                xi.    ODATA-1041 Broaden definitions of transformations topcount and bottomcount

                               xii.    (and 16 more)

 

7.        Next meetings [9:50 am PT]

1. Thursday April 26, 2018 during 8-10 am PDT (17:00-19:00 CEST)?
2. Thursday May 03, 2018 during 8-10 am PDT (17:00-19:00 CEST)

 

8.        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/62637/TC%20Timeline-2018-03-02.docx