[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: RE: Agenda for OData TC meeting on 2018-10-04
New agena item 4 1/2: Request TC GitHub Repository for ANTLR grammar for URL Conventions:
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 04, 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-09-27
i. #0036
Register the OData- headers and preferences with IANA – Mark Biamonte – 2018-07-26
5.
Issues [8:20 am PT]
i. ODATA-1212:
Validation.AllowedTerms - https://github.com/oasis-tcs/odata-vocabularies/pull/18
i. ODATA-1237
How to specify static result entity set for bound actions/functions?
ii. ODATA-1236
What should be returned for inserted non-entity value?
iii. ODATA-1064
Add ability to annotate collections to return only count and NextLink
iv. 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)
v. ODATA-1168
Clarify the use of ETags for Avoiding Update Conflicts
vi. ODATA-1165
Describe $expand and $select via prose text and examples, remove ABNF snippets
vii. ODATA-1135
Document use of JSON $schema
viii. ODATA-1005
Make sure we have capabilities for all new 4.01 functionality
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-1218
Transformations for recursive hierarchy processing
ii. ODATA-1207
Clarify need for @odata.id in nested response structures
iii. ODATA-947
Transformation for computing ratios with aggregated values
iv. ODATA-945
Correct examples 53 and 54
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]