[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: RE: [odata] Agenda for OData TC meeting on 2017-09-21 - chat transcript
[12:37] Room information was updated by: Stefan Hagen OASIS Open Data Protocol (OData) TC OData TC Weekly Meeting (Conference Call) #188
- Thursday, 21 September 2017, 06:00am to 9:00am PDT
- i.e. 2017-09-21 15:00 to 18:00 CEST (UTC+2)
- other timezone? Try eg.:
- https://www.timeanddate.com/worldclock/meetingdetails.html?year=2017&month=9&day=21&hour=13&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/
i
Next Planned meetings (tentative):
- Thursday September 28, 2017 during 8-10 am PDT?
- https://www.oasis-open.org/apps/org/workgroup/odata/event.php?event_id=43997
- Thursday October 05, 2017 during 8-10 am PDT?
- https://www.oasis-open.org/apps/org/workgroup/odata/event.php?event_id=43998
Agenda-Draft E-Mail URL:
- E-Mail Public URL = "" href="https://lists.oasis-open.org/archives/odata/201709/msg00056.html" target="_blank">https://lists.oasis-open.org/archives/odata/201709/msg00056.html
Minutes Draft Public URL (previous meeting):
- URL = "" href="https://www.oasis-open.org/committees/download.php/61567/odata-meeting-187_on-20170914-minutes.html" target="_blank">https://www.oasis-open.org/committees/download.php/61567/odata-meeting-187_on-20170914-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:
- URL = "" href="https://www.oasis-open.org/committees/download.php/59862/TC%20Timeline-2017-01-25.docx" target="_blank">https://www.oasis-open.org/committees/download.php/59862/TC%20Timeline-2017-01-25.docx
Agenda Draft (for meeting #188):
==============================================================
1. Roll call [6:00 am PT]
1.1 Self-registration link: https://www.oasis-open.org/apps/org/workgroup/odata/event.php?event_id=43996
2. Approve agenda [6:05 am PT]
3. Approve minutes from previous meeting(s) [8:10 am PT]
3.1 Minutes from September 14, 2017 TC meeting: https://www.oasis-open.org/committees/download.php/61567/odata-meeting-187_on-20170914-minutes.html
4. Review action items [Action item list: https://www.oasis-open.org/apps/org/workgroup/odata/members/action_items.php] [6:15am PT]
4.1 Action items due
4.1.1 None
5. Version 4.01 Public Review - 05 July 2017 to 03 August 2017 - Issues [6:20 am PT]
5.1 ODATA-1105 Simplify selection of properties of complex type
5.2 ODATA-1109 Clarify that 'parameter' aliases can also be used to substitute expressions
5.3 ODATA-1111 Structural properties: default for $Nullable is false in CSDL JSON feedback from implementation teams
6. Issues [8:20 am PT]
6.1 Vocabularies: NEW or OPEN
6.1.1 ODATA-1099 Add annotations to describe custom query options and custom headers
META 1: use issue-specific branches for new terms, types, properties, or add them to master branch and mark them as experimental?
META 2: add examples to term definitions as shown here via annotation Core.Example?
6.1.2 ODATA-1112 Default page size for server-driven paging
6.1.3 ODATA-1067 Consider ability to define computed default values
6.1.4 ODATA-1060 Improve specification of element response requirements
6.1.5 ODATA-1005 Make sure we have capabilities for all new 4.01 functionality
6.1.6 ODATA-884 Add term ErrorCodes to describe possible codes in error messages (public comment c201510e00019)
6.2 Vocabularies: APPLIED
6.2.1 ODATA-958 Capabilities: FilterRestrictions and SortRestrictions for navigation properties
6.2.2 ODATA-1055 DeepInsertSupport: allow applying to entity sets and collection-valued navigation properties
6.2.3 ODATA-1064 Add ability to annotate collections to return only count and NextLink
6.2.4 ODATA-1069 New term Core.OperationAvailable
6.2.5 ODATA-1079 Several issues with latest standard vocabularies
6.2.6 ODATA-1082 Add term Constraint to Validation vocabulary
6.2.7 ODATA-1089 Org.OData.Aggregation.V1 missing Nullable="false" for Function ReturnType
6.2.8 ODATA-1098 xxxRestrictions can be applied more broadly
7. Next meetings [8:50 am PT]
7.1 Thursday September 28, 2017 during 8-10 am PDT
7.2 Thursday October 05, 2017 during 8-10 am PDT
8. AOB and wrap up [8:55 am PT]
==============================================================
Meeting Member URL:
- URL = "" href="https://www.oasis-open.org/apps/org/workgroup/odata/event.php?event_id=43996" target="_blank">https://www.oasis-open.org/apps/org/workgroup/odata/event.php?event_id=43996
- 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=43996&confirmed=1
[12:37] Stefan Hagen: H4Q::Voting Members: 1 of 12 (8%) (used for quorum calculation) Room Information:
OASIS Open Data Protocol (OData) TC OData TC Weekly Meeting (Conference Call) #188
- Thursday, 21 September 2017, 06:00am to 9:00am PDT
- i.e. 2017-09-21 15:00 to 18:00 CEST (UTC+2)
- other timezone? Try eg.:
- https://www.timeanddate.com/worldclock/meetingdetails.html?year=2017&month=9&day=21&hour=13&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/
i
Next Planned meetings (tentative):
- Thursday September 28, 2017 during 8-10 am PDT?
- https://www.oasis-open.org/apps/org/workgroup/odata/event.php?event_id=43997
- Thursday October 05, 2017 during 8-10 am PDT?
- https://www.oasis-open.org/apps/org/workgroup/odata/event.php?event_id=43998
Agenda-Draft E-Mail URL:
- E-Mail Public URL = "" href="https://lists.oasis-open.org/archives/odata/201709/msg00056.html" target="_blank">https://lists.oasis-open.org/archives/odata/201709/msg00056.html
Minutes Draft Public URL (previous meeting):
- URL = "" href="https://www.oasis-open.org/committees/download.php/61567/odata-meeting-187_on-20170914-minutes.html" target="_blank">https://www.oasis-open.org/committees/download.php/61567/odata-meeting-187_on-20170914-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:
- URL = "" href="https://www.oasis-open.org/committees/download.php/59862/TC%20Timeline-2017-01-25.docx" target="_blank">https://www.oasis-open.org/committees/download.php/59862/TC%20Timeline-2017-01-25.docx
Agenda Draft (for meeting #188):
==============================================================
1. Roll call [6:00 am PT]
1.1 Self-registration link: https://www.oasis-open.org/apps/org/workgroup/odata/event.php?event_id=43996
2. Approve agenda [6:05 am PT]
3. Approve minutes from previous meeting(s) [8:10 am PT]
3.1 Minutes from September 14, 2017 TC meeting: https://www.oasis-open.org/committees/download.php/61567/odata-meeting-187_on-20170914-minutes.html
4. Review action items [Action item list: https://www.oasis-open.org/apps/org/workgroup/odata/members/action_items.php] [6:15am PT]
4.1 Action items due
4.1.1 None
5. Version 4.01 Public Review - 05 July 2017 to 03 August 2017 - Issues [6:20 am PT]
5.1 ODATA-1105 Simplify selection of properties of complex type
5.2 ODATA-1109 Clarify that 'parameter' aliases can also be used to substitute expressions
5.3 ODATA-1111 Structural properties: default for $Nullable is false in CSDL JSON feedback from implementation teams
6. Issues [8:20 am PT]
6.1 Vocabularies: NEW or OPEN
6.1.1 ODATA-1099 Add annotations to describe custom query options and custom headers
META 1: use issue-specific branches for new terms, types, properties, or add them to master branch and mark them as experimental?
META 2: add examples to term definitions as shown here via annotation Core.Example?
6.1.2 ODATA-1112 Default page size for server-driven paging
6.1.3 ODATA-1067 Consider ability to define computed default values
6.1.4 ODATA-1060 Improve specification of element response requirements
6.1.5 ODATA-1005 Make sure we have capabilities for all new 4.01 functionality
6.1.6 ODATA-884 Add term ErrorCodes to describe possible codes in error messages (public comment c201510e00019)
6.2 Vocabularies: APPLIED
6.2.1 ODATA-958 Capabilities: FilterRestrictions and SortRestrictions for navigation properties
6.2.2 ODATA-1055 DeepInsertSupport: allow applying to entity sets and collection-valued navigation properties
6.2.3 ODATA-1064 Add ability to annotate collections to return only count and NextLink
6.2.4 ODATA-1069 New term Core.OperationAvailable
6.2.5 ODATA-1079 Several issues with latest standard vocabularies
6.2.6 ODATA-1082 Add term Constraint to Validation vocabulary
6.2.7 ODATA-1089 Org.OData.Aggregation.V1 missing Nullable="false" for Function ReturnType
6.2.8 ODATA-1098 xxxRestrictions can be applied more broadly
7. Next meetings [8:50 am PT]
7.1 Thursday September 28, 2017 during 8-10 am PDT
7.2 Thursday October 05, 2017 during 8-10 am PDT
8. AOB and wrap up [8:55 am PT]
==============================================================
Meeting Member URL:
- URL = "" href="https://www.oasis-open.org/apps/org/workgroup/odata/event.php?event_id=43996" target="_blank">https://www.oasis-open.org/apps/org/workgroup/odata/event.php?event_id=43996
- 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=43996&confirmed=1
[15:02] anonymous morphed into George Ericson (Dell) [15:02] Ralf Handl (SAP SE): Voting Members: 6 of 12 (50%) (used for quorum calculation) [15:03] Ralf Handl (SAP SE): Voting Members: 8 of 12 (66%) (used for quorum calculation) [15:03] Ralf Handl (SAP SE): Quorum achieved: yes [15:05] Ralf Handl (SAP SE): Voting Members: 9 of 12 (75%) (used for quorum calculation) [15:07] Ralf Handl (SAP SE): 2.Approve agenda [6:05 am PT]
New issues:
- https://issues.oasis-open.org/browse/ODATA-1114 - If-Then-Else in $batch requests
- https://issues.oasis-open.org/browse/ODATA-1115 - Default values for $Precision and $Scale
[15:09] Ralf Handl (SAP SE): Document walkthrough if time permits [15:10] Ralf Handl (SAP SE): New issues added to 5.a, document walkthrough as 5.b [15:12] Ralf Handl (SAP SE): 3.Approve minutes from previous meeting(s) [8:10 am PT] a.Minutes from September 14, 2017 TC meeting: https://www.oasis-open.org/committees/download.php/61567/odata-meeting-187_on-20170914-minutes.html
[15:12] Ralf Handl (SAP SE): Minutes are approved [15:12] Ralf Handl (SAP SE): 4.Review action items [Action item list: https://www.oasis-open.org/apps/org/workgroup/odata/members/action_items.php] [6:15am PT] a.Action items due
i.None
[15:12] Ralf Handl (SAP SE): 5.Version 4.01 Public Review - 05 July 2017 to 03 August 2017 [6:20 am PT] a.Issues
[15:12] Ralf Handl (SAP SE): iii.ODATA-1111 Structural properties: default for $Nullable is false in CSDL JSON feedback from implementation teams [15:12] Ralf Handl (SAP SE): Mike: feedback in favor of ODATA-1111, false is the better default [15:14] Ralf Handl (SAP SE): Ralf: mixed feedback, often surprise, but no real pushback [15:14] Ralf Handl (SAP SE): Ralf: fits better to SAP mainstream data models [15:15] Ralf Handl (SAP SE): iv.https://issues.oasis-open.org/browse/ODATA-1115 - Default values for $Precision and $Scale [15:15] Ralf Handl (SAP SE): $Precision does not have a default value, omission means arbitrary precision, both for Edm.Decimal (already the case) and for temporal types. The latter is in line with the "date-time" format of OpenAPI and JSON Schema for timestamps. [15:16] Ralf Handl (SAP SE): $Scale defaults to "variable". This is in line with the "number" type of OpenAPI and JSON Schema. [15:17] Ralf Handl (SAP SE): ODATA-1115 is OPEN [15:18] Hubert Heijkers (IBM): I move to resolve ODATA-1115 as proposed. [15:18] Martin Z. SAP SE: I second [15:18] Mark Biamonte (Progress): I second [15:18] Ralf Handl (SAP SE): ODATA-1115 is RESOLVED as proposed [15:19] Ralf Handl (SAP SE): ii.ODATA-1109 Clarify that 'parameter' aliases can also be used to substitute expressions [15:19] Ralf Handl (SAP SE): Proposal:
Query parameters for $filter segment are always passed in as expressions (because that is the expected type of the parameter). All other parameters are evaluated in the context in which they are defined and passed as literals.
Open an issue to consider adding syntax for nesting parameters assignments within $expand (and, depending on ODATA-1105, to $select)
[15:35] Michael Pizzo: Revised proposal: Query parameters for $filter segment are always passed in as expressions (because that is the expected type of the parameter). All other parameters are evaluated in the context in which they are defined and passed as literals, where "Context in which they are defined" is the resource identified by the path segment in which they are defined.
Add ability to nest parameters definitions within $expand, in which case they are relative to the resource context of the $expand. Also consider adding to $select when considering ODATA-1105
[15:37] Michael Pizzo: Revised wording: Query parameters for $filter segment are always passed in as expressions (because that is the expected type of the parameter). All other parameters defined in query options are evaluated in the context of the resource identified by the path segment in which they are defined and passed as literals.
Add ability to nest parameters definitions within $expand, in which case they are relative to the resource context of the $expand. Also consider adding to $select when considering ODATA-1105
[15:44] Michael Pizzo: Revised/corrected: Query parameters for $filter segment are always passed in as expressions (because that is the expected type of the parameter). All other parameters defined as query options are evaluated in the context of the resource identified by the URL path segment in which they are used and passed as literals.
Add ability to assign values to parameter aliases within $expand, in which case they are evaluated relative to the resource context of the $expand. Also consider adding to $select when considering ODATA-1105.
[15:46] Michael Pizzo: I move we resolve ODATA-1109 as proposed. [15:47] Hubert Heijkers (IBM): I second [15:48] Ralf Handl (SAP SE): ODATA-1109 is RESOLVED as proposed [15:48] Ralf Handl (SAP SE): i.ODATA-1105 Simplify selection of properties of complex type [15:48] Ralf Handl (SAP SE): Proposal:
Harmonize syntax for complex properties within $select with syntax for navigation properties within $expand:
- complex property can be followed by parentheses containing
- $expand nested in $select. - $select with same recursive syntax
- $compute to place computed properties within the complex type
- for collection-valued complex properties also $filter, $search, $count, $orderby, $skip, and $top within the parentheses
Extended $select syntax also allowed for $select nested within $expand.
[15:49] Michael Pizzo: add: - support assigning values to parameter aliases within $select
[15:54] Ralf Handl (SAP SE): Example $select=Address($select=Street,City,Namespace.AddressWithLocation/Location)
[15:56] Ralf Handl (SAP SE): GET Customers(1)/Address?$select=Street,City,Namespace.AddressWithLocation/Location) [15:56] Ralf Handl (SAP SE): minus the trailing ) [15:57] Michael Pizzo: Revised proposal: Harmonize syntax for complex properties within $select with syntax for navigation properties within $expand:
- complex property can be followed by parentheses containing
- $expand nested in $select.
- $select with same recursive syntax
- $compute to place computed properties within the complex type
- for collection-valued structural properties also $filter, $search, $count, $orderby, $skip, and $top within the parentheses
- support assigning values to parameter aliases within $select
Extended $select syntax also allowed for $select nested within $expand.
[15:58] Hubert Heijkers (IBM): I move to resolve ODATA-1105 as per the amended proposal. [15:58] Michael Pizzo: I second [15:59] Ralf Handl (SAP SE): ODATA-1105 is RESOLVED with the amended proposal [16:00] Ralf Handl (SAP SE): v) https://issues.oasis-open.org/browse/ODATA-1114 - If-Then-Else in $batch [16:01] Ralf Handl (SAP SE): Mike: encountered situations where if-then-else or case would be useful within queries [16:02] Ralf Handl (SAP SE): Add an If-Then-Else construct to batch requests that allows executing a sequence of requests depending on a condition, typically the HTTP status code of a preceding request
Example 1:
1. Book specific seat for a sports event
2. if booking failed
2.a. book best-match seat for a sports event
endif
Example 2:
1. Modify shopping cart
2. Convert shopping cart to purchase order (bound action)
3. if success
3.a. GET newly created purchase order
else
3.b. GET modified shopping cart
endif
[16:09] Michael Pizzo: In the above scenario, it appears that statement 2a would be dependent upon response code (or success/failure) of statement 1, not on the return value from the statement 1 (unless statement 1 was an action that returned true/false). [16:09] Ralf Handl (SAP SE): Basic idea: define a new kind of request object with members "if", "then", and optionally "else". Value of "if" is a condition - use syntax of CSDL JSON logical expressions for annotations
Values of "then" and "else" are arrays of request objects - may contain further condition objects.
[16:12] Ralf Handl (SAP SE): Alternative: use $filter syntax for "if" [16:14] Ralf Handl (SAP SE): ODATA-1114 is OPEN [16:14] Ralf Handl (SAP SE): Defer it to V4.02 [16:16] Ralf Handl (SAP SE): Break until 16:30 [16:17] Ralf Handl (SAP SE): Then walk through JSON Format [16:32] Ralf Handl (SAP SE): Break is over [16:32] Ralf Handl (SAP SE): Next up: JSON Format [16:37] Ralf Handl (SAP SE): All changes accepted by the TC [17:00] Mark Biamonte (Progress): I need to drop off the call now [18:20] Ralf Handl (SAP SE): ODATA-958 ODATA-1086 ODATA-1087 ODATA-1090 ODATA-1091 ODATA-1092 ODATA-1094 ODATA-1095 ODATA-1096 ODATA-1097 ODATA-1102 ODATA-1103 ODATA-1104 ODATA-1105 ODATA-1108 ODATA-1109 ODATA-1111 ODATA-1115 [18:20] George Ericson (Dell): Move to close the listed issuesODATA-958 ODATA-1086 ODATA-1087 ODATA-1090 ODATA-1091 ODATA-1092 ODATA-1094 ODATA-1095 ODATA-1096 ODATA-1097 ODATA-1102 ODATA-1103 ODATA-1104 ODATA-1105 ODATA-1108 ODATA-1109 ODATA-1111 ODATA-1115 [18:20] Michael Pizzo: I second [18:21] Ralf Handl (SAP SE): The above listed issues are CLOSED [18:22] Ralf Handl (SAP SE): Topics for next meeting: [18:22] Ralf Handl (SAP SE): - progress documents for 4.012 [18:22] Ralf Handl (SAP SE): - discuss timeline and next steps [18:23] Ralf Handl (SAP SE): 7.Next meetings [8:50 am PT] a.Thursday September 28, 2017 during 8-10 am PDT
[18:23] Ralf Handl (SAP SE): 8.AOB and wrap up [8:55 am PT] From: odata@lists.oasis-open.org [mailto:odata@lists.oasis-open.org]
On Behalf Of Handl, Ralf Here [1] is a draft agenda for the OData TC (Technical Committee) meeting
scheduled on
Thursday September 21, 2017 during
6-9 am PDT (15:00-18:00 CEST).
Note: two hours earlier and one hour longer than usual! 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 [6:00 am PT]
2.
Approve agenda [6:05 am PT]
3.
Approve minutes from previous meeting(s) [8:10 am PT]
4.
Review action items [Action item list:
https://www.oasis-open.org/apps/org/workgroup/odata/members/action_items.php] [6:15am PT]
i. None
5.
Version 4.01 Public Review - 05 July 2017 to 03 August 2017 [6:20 am PT]
i. ODATA-1105
Simplify selection of properties of complex type
ii. ODATA-1109
Clarify that 'parameter' aliases can also be used to substitute expressions
iii. ODATA-1111
Structural properties: default for $Nullable is false in CSDL JSON – feedback from implementation teams
6.
Issues [8:20 am PT]
i. ODATA-1099
Add annotations to describe custom query options and custom headers
ii. ODATA-1112
Default page size for server-driven paging
iii. ODATA-1067
Consider ability to define computed default values
iv. ODATA-1060
Improve specification of element response requirements
v. ODATA-1005
Make sure we have capabilities for all new 4.01 functionality
vi. ODATA-884
Add term ErrorCodes to describe possible codes in error messages (public comment c201510e00019)
i. ODATA-958
Capabilities: FilterRestrictions and SortRestrictions for navigation properties
ii. ODATA-1055
DeepInsertSupport: allow applying to entity sets and collection-valued navigation properties
iii. ODATA-1064
Add ability to annotate collections to return only count and NextLink
iv. ODATA-1069
New term Core.OperationAvailable
v. ODATA-1079
Several issues with latest standard vocabularies
vi. ODATA-1082
Add term Constraint to Validation vocabulary
vii. ODATA-1089
Org.OData.Aggregation.V1 missing Nullable="false" for Function ReturnType
viii. ODATA-1098
xxxRestrictions can be applied more broadly
7.
Next meetings [8:50 am PT]
8.
AOB and wrap up [8:55 am PT] [2]
References
[3]
Timeline |
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]