Raw transcript from chat: [7:18] Room information was updated by: Stefan Hagen OASIS Open Data Protocol (OData) TC OData TC Weekly Meeting (Conference Call) #207 - Thursday, 15 March 2018, 08:00am to 10:00am PDT - i.e. 2018-03-15 16:00 to 18:00 CET (UTC+1) - other timezone? Try eg.: -
https://www.timeanddate.com/worldclock/meetingdetails.html?year=2018&month=3&day=15&hour=15&min=0&sec=0&p1=47&p2=69&p3=179 TimezoneInterferences: - In North America, daylight savings time began on March 11th. (Ends November 4th if you want to be proactive.) - In Europe (by and large), daylight savings time begins later on March 25th. - Note as always that different locales do this differently. - (For example, Mexico starts on April 1st.) So folks may want to check to be sure. 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 March 22, 2018 during 8-10 am PDT (16:00-18:00 CET) - Daylight Saving Time in North America -
https://www.oasis-open.org/apps/org/workgroup/odata/event.php?event_id=46248 - Thursday March 29, 2018 during 8-10 am PDT (17:00-18:00 CEST) Daylight Saving Time for All -
https://www.oasis-open.org/apps/org/workgroup/odata/event.php?event_id=46249 Agenda-Draft E-Mail URL: - E-Mail Public URL = href=
https://lists.oasis-open.org/archives/odata/201803/msg00055.html target= _blank >
https://lists.oasis-open.org/archives/odata/201803/msg00055.html Minutes Draft Public URL (previous meeting): - URL = href=
https://www.oasis-open.org/committees/download.php/62674/odata-meeting-206_on-20180308-minutes.html target= _blank >
https://www.oasis-open.org/committees/download.php/62674/odata-meeting-206_on-20180308-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 #207): ============================================================== 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=46247 target= _blank >
https://www.oasis-open.org/apps/org/workgroup/odata/event.php?event_id=46247 2. Approve agenda [8:05 am PT] 3. Approve minutes from previous meeting(s) [8:10 am PT] 3.1 Minutes from March 08, 2018 TC meeting: URL = href=
https://www.oasis-open.org/committees/download.php/62674/odata-meeting-206_on-20180308-minutes.html target= _blank >
https://www.oasis-open.org/committees/download.php/62674/odata-meeting-206_on-20180308-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-1166 Update JSON references to RFC8259 5.1.2 ODATA-1165 Describe $expand and $select via prose text and examples, remove ABNF snippets 5.1.3 ODATA-1164 List of use cases for canonical functions is incomplete 5.1.4 ODATA-1163 A Case for Common Expressions 5.1.5 ODATA-1154 Clarify which OData-Version a service should return 5.1.6 ODATA-1149 Support Delta responses for Singletons 5.1.7 ODATA-1148 PATCH with nested nav props should not remove omitted resources 5.1.8 ODATA-1143 Extend the Property metatype to allow a type that is an EntityType. 5.1.9 ODATA-1141 Upsert: clarify upsert along nullable single-valued navigation path 5.1.10 ODATA-1135 Document use of JSON $schema 5.1.11 ODATA-1088 Clarify affect of applying an Annotation to an element 5.2 Vocabularies: NEW or OPEN with concrete proposal 5.2.1 ODATA-1167 Add way to specify which batch formats (if any) are supported by a service 5.2.2 ODATA-1064 Add ability to annotate collections to return only count and NextLink 5.3 Vocabularies: NEW or OPEN that need more discussion 5.3.1 ODATA-1099 Add annotations to describe custom query options and custom headers 5.3.2 ODATA-1005 Make sure we have capabilities for all new 4.01 functionality 5.3.3 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 March 22, 2018 during 8-10 am PDT (16:00-18:00 CET) Daylight Saving Time in Noth America Europe 6.2 Thursday March 29, 2018 during 8-10 am PDT (17:00-19:99 CEST) back to normal time difference, Easter is coming 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=46247 target= _blank >
https://www.oasis-open.org/apps/org/workgroup/odata/event.php?event_id=46247 - 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=46247&confirmed=1 [7:48] Stefan Hagen: keep_alive [7:49] Stefan Hagen: H4Q::Voting Members: 1 of 11 (9%) (used for quorum calculation) Room Information: OASIS Open Data Protocol (OData) TC OData TC Weekly Meeting (Conference Call) #207 - Thursday, 15 March 2018, 08:00am to 10:00am PDT - i.e. 2018-03-15 16:00 to 18:00 CET (UTC+1) - other timezone? Try eg.: -
https://www.timeanddate.com/worldclock/meetingdetails.html?year=2018&month=3&day=15&hour=15&min=0&sec=0&p1=47&p2=69&p3=179 TimezoneInterferences: - In North America, daylight savings time began on March 11th. (Ends November 4th if you want to be proactive.) - In Europe (by and large), daylight savings time begins later on March 25th. - Note as always that different locales do this differently. - (For example, Mexico starts on April 1st.) So folks may want to check to be sure. 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 March 22, 2018 during 8-10 am PDT (16:00-18:00 CET) - Daylight Saving Time in North America -
https://www.oasis-open.org/apps/org/workgroup/odata/event.php?event_id=46248 - Thursday March 29, 2018 during 8-10 am PDT (17:00-18:00 CEST) Daylight Saving Time for All -
https://www.oasis-open.org/apps/org/workgroup/odata/event.php?event_id=46249 Agenda-Draft E-Mail URL: - E-Mail Public URL = href=
https://lists.oasis-open.org/archives/odata/201803/msg00055.html target= _blank >
https://lists.oasis-open.org/archives/odata/201803/msg00055.html Minutes Draft Public URL (previous meeting): - URL = href=
https://www.oasis-open.org/committees/download.php/62674/odata-meeting-206_on-20180308-minutes.html target= _blank >
https://www.oasis-open.org/committees/download.php/62674/odata-meeting-206_on-20180308-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 #207): ============================================================== 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=46247 target= _blank >
https://www.oasis-open.org/apps/org/workgroup/odata/event.php?event_id=46247 2. Approve agenda [8:05 am PT] 3. Approve minutes from previous meeting(s) [8:10 am PT] 3.1 Minutes from March 08, 2018 TC meeting: URL = href=
https://www.oasis-open.org/committees/download.php/62674/odata-meeting-206_on-20180308-minutes.html target= _blank >
https://www.oasis-open.org/committees/download.php/62674/odata-meeting-206_on-20180308-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-1166 Update JSON references to RFC8259 5.1.2 ODATA-1165 Describe $expand and $select via prose text and examples, remove ABNF snippets 5.1.3 ODATA-1164 List of use cases for canonical functions is incomplete 5.1.4 ODATA-1163 A Case for Common Expressions 5.1.5 ODATA-1154 Clarify which OData-Version a service should return 5.1.6 ODATA-1149 Support Delta responses for Singletons 5.1.7 ODATA-1148 PATCH with nested nav props should not remove omitted resources 5.1.8 ODATA-1143 Extend the Property metatype to allow a type that is an EntityType. 5.1.9 ODATA-1141 Upsert: clarify upsert along nullable single-valued navigation path 5.1.10 ODATA-1135 Document use of JSON $schema 5.1.11 ODATA-1088 Clarify affect of applying an Annotation to an element 5.2 Vocabularies: NEW or OPEN with concrete proposal 5.2.1 ODATA-1167 Add way to specify which batch formats (if any) are supported by a service 5.2.2 ODATA-1064 Add ability to annotate collections to return only count and NextLink 5.3 Vocabularies: NEW or OPEN that need more discussion 5.3.1 ODATA-1099 Add annotations to describe custom query options and custom headers 5.3.2 ODATA-1005 Make sure we have capabilities for all new 4.01 functionality 5.3.3 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 March 22, 2018 during 8-10 am PDT (16:00-18:00 CET) Daylight Saving Time in Noth America Europe 6.2 Thursday March 29, 2018 during 8-10 am PDT (17:00-19:99 CEST) back to normal time difference, Easter is coming 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=46247 target= _blank >
https://www.oasis-open.org/apps/org/workgroup/odata/event.php?event_id=46247 - 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=46247&confirmed=1 Meeting called to order [8:12] Michael Pizzo: Agenda approved with no changes [8:13] Michael Pizzo: Minutes are approved. [8:14] Michael Pizzo: Reviewed action items. None due; heads up on approaching deadlines. [8:17] Michael Pizzo: 5. Issues [8:17] Michael Pizzo: 5.1.1 i.ODATA-1166 Update JSON references to RFC8259 [8:17] Michael Pizzo: reference to new RFC:
https://tools.ietf.org/html/rfc8259 Michael Pizzo: 1166 is open [8:17] Michael Pizzo: Question: are there any updates that would affect us? [8:19] Michael Pizzo: From RFC8529: Appendix A. Changes from RFC 7159 This section lists changes between this document and the text in RFC 7159. o Section 1.2 has been updated to reflect the removal of a JSON specification from ECMA-262, to make ECMA-404 a normative reference, and to explain the particular meaning of "normative". o Section 1.3 has been updated to reflect errata filed against RFC 7159, not RFC 4627. o Section 8.1 was changed to require the use of UTF-8 when transmitted over a network. o Section 12 has been updated to increase the precision of the description of the security risk that follows from using the ECMAScript "eval()" function. o Section 14.1 has been updated to include ECMA-404 as a normative reference. o Section 14.2 has been updated to remove ECMA-404, update the version of ECMA-262, and refresh the errata list. [8:20] Michael Pizzo: Does not appear that any of these changes would have an impact on our use of JSON. [8:23] Michael Pizzo: Note: JSON apparently requires JSON readers to support escaped forward slashes, though writers are not required to escape. Our examples do not escape, which is fine. [8:24] Hubert Heijkers (IBM): I move to resolve ODATA-1166 as proposed. [8:25] Ted Jones (Red Hat): I second [8:25] Michael Pizzo: Motion approved by unanimous consent. [8:26] Michael Pizzo: ii.ODATA-1165 Describe $expand and $select via prose text and examples, remove ABNF snippets [8:30] Michael Pizzo: We will wait on ODATA-1166 until ralf can explain the overly restrictive nature of the ABNF. [8:30] Michael Pizzo: (that is, we will wait on ODATA-1165) [8:30] Michael Pizzo: iii.ODATA-1164 List of use cases for canonical functions is incomplete [8:33] Michael Pizzo: 1164 is open [8:33] Michael Pizzo: 5.1.1.4 Canonical Functions In addition to operators, a set of functions is also defined for use with the $filter or $orderby system query options. The following sections describe the available functions. Note: ISNULL or COALESCE operators are not defined. Instead, OData defines a null literal that can be used in comparisons. [8:35] Michael Pizzo: Statement should be more general, but current wording does help people understand where functions can be used. [8:35] Gerald Krause (SAP): The set of functions can be used anywhere a common _expression_ is applied such as $filter or $orderby. [8:35] Michael Pizzo: Perhaps make the statement more specific, but include filter and orderby as examples... [8:36] Michael Pizzo: Gerald has updated the proposal. [8:36] Hubert Heijkers (IBM): I move to resolve ODATA-1164 as per the updated proposal. [8:37] Matt Borges (SAP): I second [8:39] Michael Pizzo: ODATA 1164 is approved as proposed. [8:39] Michael Pizzo: iv.ODATA-1163 A Case for Common Expressions [8:41] Michael Pizzo: 1. Core OData: Ad-hoc calculations with logic on the current property values: Example: Signum(x) GET ~/XValues?$compute=case(X > 0 : 1,X < 0 : -1, 0) as SignumX&$select=X,SignumX 2. Data Aggregation extension: Restricting aggregation to those values that occur in combination with certain groupable property values: Example: Comparing company revenues for years 2000 and 2017 GET ~/Sales?$apply=groupby((Company), aggregate(case(Time/Year eq 2000 : Revenue) with sum as TotalRevenue2000, case(Time/Year eq 2017 : Revenue) with sum as TotalRevenue2017)) 3. Data Aggregation extension: Defining dynamic groupable properties Example: From a collection of incidents with fine-grained state model (e.g., new, assigned, resolved, verified, reopened, closed) retrieve the aggregated count of open and closed incidents: GET ~/Incidents?$apply=compute(case(Status eq Closed : Closed, Open) as ProcessingStatus)/groupby((ProcessingStatus), aggregate($count as IncidentCount)) [8:45] Michael Pizzo: RESO was asking for this just last week. [8:50] Michael Pizzo: is case(X > 0 : 1,X < 0 : -1, 0) equivalent to if(X>0,1,if(X<0,-1,0)? [9:04] Michael Pizzo: Would it be equally expressive to use something like if-then-else? Would that be more intuitive to a programmer? [9:05] Michael Pizzo: Or would switch be more similar for programmers? [9:06] Michael Pizzo: George: are we trying to put too much in the expressions, making it hard on services to implement? [9:07] Michael Pizzo: Would we need a way to tell whether services support the new _expression_? [9:09] Michael Pizzo: (add to existing capabilities for supported canonical functions) [9:13] Michael Pizzo: could be done as a custom function if(condition,value-if-true,value-if-false), but that would be more verbose and less standardized. [9:14] Michael Pizzo: Gerald: how do we define the type of the _expression_ result? [9:16] Michael Pizzo: Easiest would be to force all result expressions to be of the same type. [9:16] Michael Pizzo: Alternative would be to cast to common type; i.e., if one _expression_ returned an integer and one a string, the type of the _expression_ would be a string. [9:28] Michael Pizzo: OData 1163 is open. Gerald will flesh out a complete proposal. [9:28] Michael Pizzo: v.ODATA-1154 Clarify which OData-Version a service should return [9:29] Michael Pizzo: Discussed in meeting march 1st. Open questions: [9:29] Michael Pizzo: Questions: 1) What if no OData-MaxVersion is specified? 2) Does specifying an OData-Version limit the constructs that the request can use in the URL? i.e., if I have a 4.0 payload, am I restricted to 4.0 URL constructs, even if I know the service supports them? 3) What if the client *only* support 4.01? Do we have a way to specify NOT to return 4.0? 4) Does a service have to return a 4.01 payload if the request uses a 4.01 construct? [9:42] Michael Pizzo: The following is a legal delta payload for describing changes to a collection of customers: { "@context":"#$delta", "value": [ { "CustomerID": "EASTC", "CompanyName": "Eastern Connection", "ContactName": "Ann Devon", "ContactTitle": "Sales Agent" }, { "CustomerID": "ALFKI", "Orders@delta": [ { "OrderID": 11011, "CustomerID": "ALFKI", "EmployeeID": 3, "OrderDate": "1998-04-09T00:00:00Z", "RequiredDate": "1998-05-07T00:00:00Z", "ShippedDate": "1998-04-13T00:00:00Z" } ] } ] } [9:46] Michael Pizzo: This could be a delta response from an initial query of GET ~Customers, or to a PATCH Customers [9:49] Michael Pizzo: Similarly, changes to a single item *within the customers collection* [9:49] Michael Pizzo: { "@context":"#$delta", "value": [ { "CustomerID": "ALFKI", "Orders@delta": [ { "OrderID": 11011, "CustomerID": "ALFKI", "EmployeeID": 3, "OrderDate": "1998-04-09T00:00:00Z", "RequiredDate": "1998-05-07T00:00:00Z", "ShippedDate": "1998-04-13T00:00:00Z" } ] } ] } [9:50] Michael Pizzo: Today, we can patch an individual customer (PATCH ~Customers('ALFKI'): { "@context":"#$delta", "CustomerID": "ALFKI", "Name": "Bob" } [9:51] Michael Pizzo: I would expect you could also PATCH ~Customers('ALFKI'): { "Name": "Bob", "Orders@delta": [ { "OrderID": 11011, "CustomerID": "ALFKI", "EmployeeID": 3, "OrderDate": "1998-04-09T00:00:00Z", "RequiredDate": "1998-05-07T00:00:00Z", "ShippedDate": "1998-04-13T00:00:00Z" } ] } [9:54] Michael Pizzo: So, if I did a GET ~Customers('ALFKI')?$expand=Orders, and asked for a delta link, that delta link could return this same payload. [9:54] Michael Pizzo: (with the addition of the context url) [9:56] Michael Pizzo: In a response, the context url would be "@context":"#$delta" [9:58] Michael Pizzo: GET ~Customers('ALFKI') = > context: ...Customers/$entity [9:59] Michael Pizzo: GET ~CustomerSingleton => context: ...CustomerSingleton (with no trailing /$entity) [10:00] Michael Pizzo: same thing for a single valued nav prop... [10:01] Michael Pizzo: (strike that; Hubert points out that, for a single valued nav prop bound to a collection, the contextUrl is the bound set with /$entity) Mike to update issue with conversation [10:04] Michael Pizzo: a.Thursday March 22, 2018 during 8-10 am PST (16:00-18:00 CEST) Daylight Saving Time in Central Europe b.Thursday March 29, 2018 during 8-10 am PDT (17:00-19:99 CEST) back to normal time difference, Easter is coming [10:05] Michael Pizzo: 7.AOB and wrap up [9:55 am PT] [10:07] Michael Pizzo: Meeting adjourned. Thanks everyone! From:
odata@lists.oasis-open.org <
odata@lists.oasis-open.org> On Behalf Of Handl, Ralf Sent: Tuesday, March 13, 2018 6:07 AM To:
odata@lists.oasis-open.org Subject: [odata] Agenda for OData TC meeting on 2018-03-15 Here [1] is a draft agenda for the OData TC (Technical Committee) meeting scheduled on Thursday March 15, 2018 during 8-10 am PST ( 16:00-18: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= 46247 2. Approve agenda [8:05 am PT] 3. Approve minutes from previous meeting(s) [8:10 am PT] Minutes from March 08, 2018 TC meeting:
https://www.oasis-open.org/committees/download.php/62674/odata-meeting-206_on-20180308-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-1166 Update JSON references to RFC8259 ii. ODATA-1165 Describe $expand and $select via prose text and examples, remove ABNF snippets iii. ODATA-1164 List of use cases for canonical functions is incomplete iv. ODATA-1163 A Case for Common Expressions v. ODATA-1154 Clarify which OData-Version a service should return vi. ODATA-1149 Support Delta responses for Singletons vii. ODATA-1148 PATCH with nested nav props should not remove omitted resources viii. ODATA-1143 Extend the Property metatype to allow a type that is an EntityType. ix. ODATA-1141 Upsert: clarify upsert along nullable single-valued navigation path x. ODATA-1135 Document use of JSON $schema xi. ODATA-1088 Clarify affect of applying an Annotation to an element 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 Vocabularies: NEW or OPEN that need more discussion i. ODATA-1099 Add annotations to describe custom query options and custom headers ii. ODATA-1005 Make sure we have capabilities for all new 4.01 functionality iii. ODATA-884 Add term ErrorCodes to describe possible codes in error messages (public comment c201510e00019) 6. Next meetings [9:50 am PT] Thursday March 22, 2018 during 8-10 am PST (16:00-18:00 CEST) – Daylight Saving Time in Central Europe Thursday March 29, 2018 during 8-10 am PDT (17:00-19:99 CEST) – back to normal time difference, Easter is coming 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/62637/TC%20Timeline-2018-03-02.docx