[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: RE: Agenda for OData TC meeting on 2018-08-02
No quorum reached, meeting adjourned From: odata@lists.oasis-open.org <odata@lists.oasis-open.org>
On Behalf Of Handl, Ralf Update: 4.5 GitHub Pages sites have been linked from repository start pages:
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 August 02, 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.
Skype Experiment [8:10 am PT]
.........................................................................................................................................
Join by phone
+1 8552234162 "Canada" (SAP Dial-In)
+86 4008106069 "China All Cities" (SAP
Dial-In)
+49 8005891883 "Germany" (SAP Dial-In)
+49 6922227996 "Germany Frankfurt" (SAP
Dial-In)
+91 8071279160 "India Bangalore" (SAP
Dial-In)
0008004404099 "India" (SAP Dial-In)
+65 67041630 "Singapore All Cities" (SAP
Dial-In)
+44 3306068668 "United Kingdom All Cities"
(SAP Dial-In)
+1 8664100244 "United States" (SAP Dial-In)
+1 2106069508 "United States All Cities"
(SAP Dial-In)
Conference ID: 78320472 Forgot
your dial-in PIN?
| Help [!OC([1033])!]
[!OC([CUSTOMINVITE])!]
.........................................................................................................................................
4.
Approve minutes from previous meeting(s) [8:15 am PT]
5.
Review action items [Action item list:
https://www.oasis-open.org/apps/org/workgroup/odata/members/handlaction_items.php] [8:20 am PT]
i. None
i. #0037
Concept for Google Protocol Buffers as a data format – Hubert Heijkers – 2018-09-27
ii. #0038
Prepare proposal for REST Profile / OData Essentials – Mike Pizzo – 2018-08-08
i. #0036
Register the OData- headers and preferences with IANA – Mark Biamonte – 2018-07-26
6.
Issues [8:20 am PT]
i. ODATA-1207
Clarify need for @odata.id in nested response structures
ii. ODATA-1206
Explicitly note support for collection-valued navigation/complex properties in property paths in aggregate/groupby
iii. ODATA-1205
Examples 53, 54, and 59 are not compliant with Data Aggregation ABNF
iv. ODATA-947
Transformation for computing ratios with aggregated values
v. ODATA-945
Correct examples 53 and 54
i. ODATA-1209
Term for original OData version of (auto-)converted $metadata
ii. ODATA-1204
Vocabularies Document references OData Version 4.01. Part 3: Common Schema Definition Language (CSDL)
iii. ODATA-1194
Add term Core.Example to allow including annotation examples in term definitions
iv. ODATA-1176
Capabilities: add new term SelectRestrictions
v. ODATA-1167
Add way to specify which batch formats (if any) are supported by a service
vi. ODATA-1064
Add ability to annotate collections to return only count and NextLink
i. ODATA-1203
Allow numeric indexes in Path constructs within annotations
ii. ODATA-1202
Deep update with nested delta items should allow Core.ContentID
iii. 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)
iv. ODATA-1197
Chapter 21 Error Response: replace misleading "code" values with FOO or BAR
v. ODATA-1196
Clarify update of media streams
vi. ODATA-1195
11.2.6.6: value of $search is search _expression_, not boolean _expression_
vii. ODATA-1191
Make sure that all model elements are annotatable
viii. ODATA-1190
Add matchesPattern as a $filter function
ix. ODATA-1189
Conformance: Nullable for collections
x. ODATA-1188
Allow using instance annotations in $select and $expand
xi. ODATA-1187
No way to bind nav prop on recursively nested (contained or complex) type
xii. ODATA-1183
Allow Singletons to be null
xiii. ODATA-1180
Cast between enumeration types and integer types
xiv. ODATA-1177
Core: add term SchemaLocation
xv. ODATA-1171
Consider using matrix parameters for filter segments
xvi. ODATA-1168
Clarify the use of ETags for Avoiding Update Conflicts
xvii. ODATA-1165
Describe $expand and $select via prose text and examples, remove ABNF snippets
xviii. ODATA-1148
PATCH with nested nav props should not remove omitted resources
xix. ODATA-1143
Extend the Property metatype to allow a type that is an EntityType.
xx. ODATA-1141
Upsert: clarify upsert along nullable single-valued navigation path
xxi. ODATA-1135
Document use of JSON $schema
xxii. ODATA-1088
Clarify effect of applying an Annotation to an element
i. ODATA-1208
Specify the finest possible granularity for Duration
ii. ODATA-1200
ODATA-884 / Support sample values for types, parameters, request/response bodies
iii. ODATA-1199
ODATA-884 / Add property SystemQueryOptions to call out supported system query options per request method
iv. ODATA-1193
Automated vocabulary checks indicate some potential issues
v. ODATA-1177
Allow referencing a (JSON) schema for Edm.Untyped properties
vi. ODATA-1140
ODATA-884 / Add details to HTTPResponseCode term
vii. ODATA-1107
Introduce instance annotation to specify which types an instance "implements"
viii. ODATA-1099
Add annotations to describe custom query options and custom headers
ix. ODATA-1005
Make sure we have capabilities for all new 4.01 functionality
x. ODATA-884
Add term ErrorCodes to describe possible codes in error messages (public comment c201510e00019)
7.
Next meetings [9:50 am PT]
8.
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]