[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: RE: Agenda for OData TC meeting on 2018-10-25 - chat transcript
[17:00] Room information was updated by: Ralf Handl (SAP SE)1 Here [1] is a draft agenda for the OData TC (Technical Committee) meeting scheduled on Thursday October 25, 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]
a.Self-registration link: https://www.oasis-open.org/apps/org/workgroup/odata/event.php?event_id=46279
2.Approve agenda [8:05 am PT]
3.Approve minutes from previous meeting(s) [8:10 am PT]
a.Minutes from October 18, 2018 TC meeting: https://www.oasis-open.org/committees/download.php/64115/odata-meeting-234_on-20181018-minutes.html
4.Review action items [Action item list: https://www.oasis-open.org/apps/org/workgroup/odata/members/action_items.php?sort_field=due_closed_date] [8:15am PT]
a.Upcoming
i.#0037 Concept for Google Protocol Buffers as a data format Hubert Heijkers 2018-12-06
b.In progress
i.#0036 Register the OData- headers and preferences with IANA Mark Biamonte 2018-07-26
5.Issues [8:20 am PT]
a.APPLIED
i.ODATA-1241 Support common expressions as values in URL-JSON
1.https://github.com/oasis-tcs/odata-abnf/pull/5
2.https://www.oasis-open.org/committees/download.php/64118/odata-v4.01-wd06-part2-url-conventions-2018-10-19.docx
ii.ODATA-1230 /$filter(...) segments in paths and expressions
1.https://github.com/oasis-tcs/odata-abnf/pull/6
2.https://www.oasis-open.org/committees/download.php/64118/odata-v4.01-wd06-part2-url-conventions-2018-10-19.docx
3.https://www.oasis-open.org/committees/download.php/64119/odata-v4.01-wd06-part1-protocol-2018-10-19.docx
iii.ODATA-1228 Support non-batch mechanism for long URLs
1.https://github.com/oasis-tcs/odata-abnf/pull/9
2.https://www.oasis-open.org/committees/download.php/64118/odata-v4.01-wd06-part2-url-conventions-2018-10-19.docx
iv.ODATA-1223 Add OData- prefix back to EntityId header
1.https://github.com/oasis-tcs/odata-abnf/pull/3
2.https://www.oasis-open.org/committees/download.php/64119/odata-v4.01-wd06-part1-protocol-2018-10-19.docx
v.ODATA-1190 Add matchesPattern as a $filter function
1.https://github.com/oasis-tcs/odata-abnf/pull/8
2.https://www.oasis-open.org/committees/download.php/64118/odata-v4.01-wd06-part2-url-conventions-2018-10-19.docx
3.https://www.oasis-open.org/committees/download.php/64119/odata-v4.01-wd06-part1-protocol-2018-10-19.docx
vi.ODATA-1188 Allow using instance annotations in $select and $expand
1.https://github.com/oasis-tcs/odata-vocabularies/pull/24
2.https://github.com/oasis-tcs/odata-abnf/pull/7
3.https://www.oasis-open.org/committees/download.php/64118/odata-v4.01-wd06-part2-url-conventions-2018-10-19.docx
4.https://www.oasis-open.org/committees/download.php/64119/odata-v4.01-wd06-part1-protocol-2018-10-19.docx
vii.ODATA-868 Describe HTTP encoding for streamed requests and responses
1.https://github.com/oasis-tcs/odata-abnf/pull/4
2.https://www.oasis-open.org/committees/download.php/64119/odata-v4.01-wd06-part1-protocol-2018-10-19.docx
3.https://www.oasis-open.org/committees/download.php/64120/odata-json-format-v4.01-wd06-2018-10-19.docx
viii.ODATA-1203 Allow numeric indexes in Path constructs within annotations
1.https://tools.oasis-open.org/version-control/browse/wsvn/odata/trunk/4.01%20spec/schemas/edm.xsd?op=diff&rev=1031
2.https://github.com/oasis-tcs/odata-csdl-schemas/pull/1
3.https://www.oasis-open.org/committees/download.php/64129/odata-csdl-json-v4.01-wd05-2018-10-22.docx
4.https://www.oasis-open.org/committees/download.php/64130/odata-csdl-xml-v4.01-wd06-2018-10-22.docx
ix.ODATA-1183
1. https://github.com/oasis-tcs/odata-csdl-schemas/pull/2
2.https://www.oasis-open.org/committees/download.php/64129/odata-csdl-json-v4.01-wd05-2018-10-22.docx
3.https://www.oasis-open.org/committees/download.php/64130/odata-csdl-xml-v4.01-wd06-2018-10-22.docx
x.ODATA-1170 Allow @odata.type for isomorphy to CSDL XML
1.https://github.com/oasis-tcs/odata-csdl-schemas/pull/3
2.https://www.oasis-open.org/committees/download.php/64129/odata-csdl-json-v4.01-wd05-2018-10-22.docx
xi.ODATA-1232 Support Union types
1.https://github.com/oasis-tcs/odata-vocabularies/pull/27
xii.ODATA-1229 Introduce LocalDateTime TypeDef to apply to string datatype
1.https://github.com/oasis-tcs/odata-vocabularies/pull/23
2.https://www.oasis-open.org/committees/download.php/64118/odata-v4.01-wd06-part2-url-conventions-2018-10-19.docx
xiii.ODATA-1208 Specify the finest possible granularity for Duration
1.https://github.com/oasis-tcs/odata-vocabularies/pull/22
2.https://www.oasis-open.org/committees/download.php/64129/odata-csdl-json-v4.01-wd05-2018-10-22.docx
3.https://www.oasis-open.org/committees/download.php/64130/odata-csdl-xml-v4.01-wd06-2018-10-22.docx
xiv.ODATA-1202 Deep update with nested delta items should allow Core.ContentID
1.https://github.com/oasis-tcs/odata-vocabularies/pull/25
2.https://www.oasis-open.org/committees/download.php/64119/odata-v4.01-wd06-part1-protocol-2018-10-19.docx
xv.ODATA-1114 If-Then-Else in $batch requests
1.https://github.com/oasis-tcs/odata-vocabularies/pull/26
2.https://www.oasis-open.org/committees/download.php/64120/odata-json-format-v4.01-wd06-2018-10-19.docx
b.V4.01: NEW or OPEN
i.ODATA-1246 Allow BaseType to be a ComplexType
ii.ODATA-1245 Extract _expression_ syntax into own sub-section next to $filter
iii.ODATA-1243 Clarify whether $orderby and string comparison with ge, gt, le, lt is language-specific
iv.ODATA-1242 Clarify that resolved relative URIs in batch responses cannot contain content-ID references
v.ODATA-1239 Define a mechanism to distinguish between inserted and updated entities in a Delta Response
vi.ODATA-1238 Clarifications for select-list in ContextUrl
vii.ODATA-1198 ETag handling deviations from RFC7232 are avoidable if we consider two kinds of ETag (ETag in response header and ETag in response payload)
viii.ODATA-1168 Clarify the use of ETags for Avoiding Update Conflicts
ix.ODATA-1165 Describe $expand and $select via prose text and examples, remove ABNF snippets
x.ODATA-1135 Document use of JSON $schema
xi.ODATA-1064 Add ability to annotate collections to return only count and NextLink
xii.ODATA-1005 Make sure we have capabilities for all new 4.01 functionality
c.Data Aggregation: NEW or OPEN
i.ODATA-1244 Extend compute to work with aggregated values calculated from the input set
ii.ODATA-1218 Transformations for recursive hierarchy processing
iii.ODATA-1207 Clarify need for @odata.id in nested response structures
iv.ODATA-947 Transformation for computing ratios with aggregated values
v.ODATA-945 Correct examples 53 and 54
d.Vocabularies: NEW or OPEN
i.ODATA-1226 Ambiguity with Capabilities.ChangeTracking annotation
ii.ODATA-1216 Terms for POST/PATCH/PUT with system query options to shape response
iii.ODATA-1214 Annotate constructor actions
iv.ODATA-1200 ODATA-884 / Support sample values for types, parameters, request/response bodies
v.ODATA-1194 Add term Core.Example to allow including annotation examples in term definitions
vi.ODATA-1176 Capabilities: add new term SelectSupported
vii.ODATA-1140 ODATA-884 / Add details to HTTPResponseCode term
viii.ODATA-1099 Add annotations to describe custom query options and custom headers
ix.ODATA-884 Add term ErrorCodes to describe possible codes in error messages (public comment c201510e00019)
e.Vocabularies: NEW or OPEN that need more discussion
i.ODATA-1177 Allow referencing a (JSON) schema for Edm.Untyped properties
ii.ODATA-1107 Introduce instance annotation to specify which types an instance "implements"
iii.ODATA-1060 Improve specification of element response requirements
6.Next meetings [9:50 am PT]
a.Thursday November 01, 2018 during 8-10 am PST (16:00-18:00 CEST) public holiday in Germany no meeting?
b.Thursday November 08, 2018 during 8-10 am PST (17:00-19:00 CET)
c.Thursday November 15, 2018 during 8-10 am PST (17:00-19:00 CET)
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://lync.co.sap.com/meet/ralf.handl/Q4QB1098
Conference call details: https://www.oasis-open.org/apps/org/workgroup/odata/download.php/63673/latest/TC%20meeting%20dial-in%20details.htm
[3] Timeline
https://www.oasis-open.org/committees/download.php/62637/TC%20Timeline-2018-03-02.docx
[17:00] Ralf Handl (SAP SE)1 morphed into Ralf Handl (SAP SE) [17:01] Ralf Handl (SAP SE): Voting Members: 2 of 9 (22%) (used for quorum calculation) [17:02] Ralf Handl (SAP SE): Voting Members: 4 of 9 (44%) (used for quorum calculation) [17:02] anonymous morphed into Mark Biamonte (Progress) [17:05] Ralf Handl (SAP SE): Voting Members: 5 of 9 (55%) (used for quorum calculation) [17:05] Ralf Handl (SAP SE): Quorum achieved: yes [17:05] Ralf Handl (SAP SE): 2.Approve agenda [8:05 am PT] [17:06] Ralf Handl (SAP SE): Mike to close ODATA-1247 [17:07] Ralf Handl (SAP SE): Agenda is approved [17:07] Ralf Handl (SAP SE): 3.Approve minutes from previous meeting(s) [8:10 am PT] a.Minutes from October 18, 2018 TC meeting: https://www.oasis-open.org/committees/download.php/64115/odata-meeting-234_on-20181018-minutes.html
[17:07] Ralf Handl (SAP SE): Minutes are approved [17:08] Ralf Handl (SAP SE): 4.Review action items [Action item list: https://www.oasis-open.org/apps/org/workgroup/odata/members/action_items.php?sort_field=due_closed_date] [8:15am PT] a.Upcoming
i.#0037 Concept for Google Protocol Buffers as a data format Hubert Heijkers 2018-12-06
b.In progress
i.#0036 Register the OData- headers and preferences with IANA Mark Biamonte 2018-07-26
[17:08] Ralf Handl (SAP SE): No updates [17:08] Ralf Handl (SAP SE): 5.Issues [8:20 am PT] a.APPLIED
i.ODATA-1241 Support common expressions as values in URL-JSON
1.https://github.com/oasis-tcs/odata-abnf/pull/5
2.https://www.oasis-open.org/committees/download.php/64118/odata-v4.01-wd06-part2-url-conventions-2018-10-19.docx
[17:14] George Ericson (Dell): Having trouble getting Skype up. [17:25] Ralf Handl (SAP SE): Mike: approve this application and open new issue for possible changes to "in" and listExpr [17:28] Ralf Handl (SAP SE): Discussed issues: in [...] is sufficient, why a synonym in (...) that is restricted to primitive values? [17:28] Ralf Handl (SAP SE): If we keep in (...) why not allow expressions in addition to primitive literals? [17:29] Ralf Handl (SAP SE): Arbitrary expressions or only ones resulting in primitive values? [17:29] Michael Pizzo: I move to close ODATA-1241 as applied [17:29] Mark Biamonte (Progress): isecond [17:30] Ralf Handl (SAP SE): ODATA-1241 is CLOSED as applied [17:30] Ralf Handl (SAP SE): ii.ODATA-1230 /$filter(...) segments in paths and expressions 1.https://github.com/oasis-tcs/odata-abnf/pull/6
2.https://www.oasis-open.org/committees/download.php/64118/odata-v4.01-wd06-part2-url-conventions-2018-10-19.docx
3.https://www.oasis-open.org/committees/download.php/64119/odata-v4.01-wd06-part1-protocol-2018-10-19.docx
[17:35] George Ericson (Dell): Reinstalled Skype... I'm back. [17:38] Michael Pizzo: welcome back George! [17:39] Michael Pizzo: I move we close ODATA-1230 as applied. [17:39] Mark Biamonte (Progress): I second [17:39] Ralf Handl (SAP SE): ODATA-1230 is CLOSED as applied [17:39] Ralf Handl (SAP SE): iii.ODATA-1228 Support non-batch mechanism for long URLs 1.https://github.com/oasis-tcs/odata-abnf/pull/9
2.https://www.oasis-open.org/committees/download.php/64118/odata-v4.01-wd06-part2-url-conventions-2018-10-19.docx
[18:04] Michael Pizzo: discussion on having query options in both the URL and the body. We originally proposed only one or the other, for simplicity, but found that some query options are required to be in the URL for routing (i.e., jsessionid). [18:05] Michael Pizzo: Rather than craft wording around what can and can't be in the url versus the body, or any precedents between them, we should just say that they are combined. [18:10] Ralf Handl (SAP SE): Simplified paragraph 3 of section 4.17 to: Requests to paths ending in /$query MUST use the POST verb. Query options specified in the request body and query options specified in the request URL are processed together.
[18:11] George Ericson (Dell): Move to resolve ODATA-1228 as simplified. [18:11] Mark Biamonte (Progress): I second [18:12] George Ericson (Dell): Move to Close ODATA-1228 as applied. [18:12] Mark Biamonte (Progress): I second [18:13] Ralf Handl (SAP SE): ODATA-1228 is CLOSED as applied with the simplified text [18:13] Ralf Handl (SAP SE): iv.ODATA-1223 Add OData- prefix back to EntityId header 1.https://github.com/oasis-tcs/odata-abnf/pull/3
2.https://www.oasis-open.org/committees/download.php/64119/odata-v4.01-wd06-part1-protocol-2018-10-19.docx
[18:15] George Ericson (Dell): I move to close ODATA-1223 as applied. [18:15] Michael Pizzo: I second [18:16] Ralf Handl (SAP SE): ODATA-1223 is CLOSED as applied [18:16] Ralf Handl (SAP SE): v.ODATA-1190 Add matchesPattern as a $filter function 1.https://github.com/oasis-tcs/odata-abnf/pull/8
2.https://www.oasis-open.org/committees/download.php/64118/odata-v4.01-wd06-part2-url-conventions-2018-10-19.docx
3.https://www.oasis-open.org/committees/download.php/64119/odata-v4.01-wd06-part1-protocol-2018-10-19.docx
[18:28] Ralf Handl (SAP SE): Modified text in URL Conventions to: 5.1.1.7.1 matchesPattern
The matchesPattern function has the following signature:
Edm.Boolean matchesPattern(Edm.String,Edm.String)
The second parameter MUST evaluate to a string containing an [ECMAScript] (_javascript_) regular _expression_. The matchesPattern function returns true if the first parameter evaluates to a string matching that regular _expression_, using syntax and semantics of [ECMAScript] regular expressions, otherwise it returns false.
Example 79: all customers with a CompanyName that match the (percent-encoded) regular _expression_ ^A.*e$
http://host/service/Customers?$filter=matchesPattern(CompanyName,'%5EA.*e$')
[18:29] George Ericson (Dell): I move to close OData-1190 as modified. [18:29] Mark Biamonte (Progress): I second [18:30] Ralf Handl (SAP SE): ODATA-1190 is CLOSED as applied [18:30] Ralf Handl (SAP SE): vi.ODATA-1188 Allow using instance annotations in $select and $expand 1.https://github.com/oasis-tcs/odata-vocabularies/pull/24
2.https://github.com/oasis-tcs/odata-abnf/pull/7
3.https://www.oasis-open.org/committees/download.php/64118/odata-v4.01-wd06-part2-url-conventions-2018-10-19.docx
4.https://www.oasis-open.org/committees/download.php/64119/odata-v4.01-wd06-part1-protocol-2018-10-19.docx
[18:44] Ralf Handl (SAP SE): ABNF needs to be refined: differentiate between entityAnnotation and complexAnnotation [18:46] Michael Pizzo: I move we approve the application of ODATA-1188 to the url conventions, protocol, and vocabularies documents. [18:47] Mark Biamonte (Progress): I second [18:47] Ralf Handl (SAP SE): ODATA-1188 is partially approved, pending only the changes to the ABNF [18:48] Ralf Handl (SAP SE): vii.ODATA-868 Describe HTTP encoding for streamed requests and responses 1.https://github.com/oasis-tcs/odata-abnf/pull/4
2.https://www.oasis-open.org/committees/download.php/64119/odata-v4.01-wd06-part1-protocol-2018-10-19.docx
3.https://www.oasis-open.org/committees/download.php/64120/odata-json-format-v4.01-wd06-2018-10-19.docx
[19:06] Michael Pizzo: I move to close ODATA-868 as applied. [19:06] Mark Biamonte (Progress): I second [19:06] Ralf Handl (SAP SE): ODATA-868 is CLOSED as applied [19:06] Ralf Handl (SAP SE): 6.Next meetings [9:50 am PT] a.Thursday November 01, 2018 during 8-10 am PST (16:00-18:00 CEST) public holiday in Germany no meeting?
b.Thursday November 08, 2018 during 8-10 am PST (17:00-19:00 CET)
c.Thursday November 15, 2018 during 8-10 am PST (17:00-19:00 CET)
[19:07] Ralf Handl (SAP SE): 7.AOB and wrap up [9:55 am PT] [19:07] Ralf Handl (SAP SE): Meeting is adjourned [19:07] Stefan Hagen: Minutes are ready From: odata@lists.oasis-open.org <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 October 25, 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]
2.
Approve agenda [8: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?sort_field=due_closed_date] [8:15am PT]
i. #0037
Concept for Google Protocol Buffers as a data format – Hubert Heijkers – 2018-12-06
i. #0036
Register the OData- headers and preferences with IANA – Mark Biamonte – 2018-07-26
5.
Issues [8:20 am PT]
i. ODATA-1241
Support common expressions as values in URL-JSON
ii. ODATA-1230
/$filter(...) segments in paths and expressions
iii. ODATA-1228
Support non-batch mechanism for long URLs
iv. ODATA-1223
Add OData- prefix back to EntityId header
v. ODATA-1190
Add matchesPattern as a $filter function
vi. ODATA-1188
Allow using instance annotations in $select and $expand
vii. ODATA-868
Describe HTTP encoding for streamed requests and responses
viii. ODATA-1203
Allow numeric indexes in Path constructs within annotations
ix. ODATA-1183
x. ODATA-1170
Allow @odata.type for isomorphy to CSDL XML
xi. ODATA-1232
Support Union types
xii. ODATA-1229
Introduce LocalDateTime TypeDef to apply to string datatype
xiii. ODATA-1208
Specify the finest possible granularity for Duration
xiv. ODATA-1202
Deep update with nested delta items should allow Core.ContentID
xv. ODATA-1114
If-Then-Else in $batch requests
i. ODATA-1246
Allow BaseType to be a ComplexType
ii. ODATA-1245
Extract _expression_ syntax into own sub-section next to $filter
iii. ODATA-1243
Clarify whether $orderby and string comparison with ge, gt, le, lt is language-specific
iv. ODATA-1242
Clarify that resolved relative URIs in batch responses cannot contain content-ID references
v. ODATA-1239
Define a mechanism to distinguish between inserted and updated entities in a Delta Response
vi. ODATA-1238
Clarifications for select-list in ContextUrl
vii. ODATA-1198
ETag handling deviations from RFC7232 are avoidable if we consider two kinds of ETag (ETag in response header and ETag in response payload)
viii. ODATA-1168
Clarify the use of ETags for Avoiding Update Conflicts
ix. ODATA-1165
Describe $expand and $select via prose text and examples, remove ABNF snippets
x. ODATA-1135
Document use of JSON $schema
xi. ODATA-1064
Add ability to annotate collections to return only count and NextLink
xii. ODATA-1005
Make sure we have capabilities for all new 4.01 functionality
i. ODATA-1244
Extend compute to work with aggregated values calculated from the input set
ii. ODATA-1218
Transformations for recursive hierarchy processing
iii. ODATA-1207
Clarify need for @odata.id in nested response structures
iv. ODATA-947
Transformation for computing ratios with aggregated values
v. ODATA-945
Correct examples 53 and 54
i. ODATA-1226
Ambiguity with Capabilities.ChangeTracking annotation
ii. ODATA-1216
Terms for POST/PATCH/PUT with system query options to shape response
iii. ODATA-1214
Annotate constructor actions
iv. ODATA-1200
ODATA-884 / Support sample values for types, parameters, request/response bodies
v. ODATA-1194
Add term Core.Example to allow including annotation examples in term definitions
vi. ODATA-1176
Capabilities: add new term SelectSupported
vii. ODATA-1140
ODATA-884 / Add details to HTTPResponseCode term
viii. ODATA-1099
Add annotations to describe custom query options and custom headers
ix. ODATA-884
Add term ErrorCodes to describe possible codes in error messages (public comment c201510e00019)
i. ODATA-1177
Allow referencing a (JSON) schema for Edm.Untyped properties
ii. ODATA-1107
Introduce instance annotation to specify which types an instance "implements"
iii. ODATA-1060
Improve specification of element response requirements
6.
Next meetings [9:50 am PT]
7.
AOB and wrap up [9:55 am PT] [2]
References
[3]
Timeline |
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]