[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Agenda for OData TC meeting on 2018-07-19
Here [1] is a draft agenda for the OData TC (Technical Committee) meeting
scheduled on
Thursday July 19, 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.
Face-to-Face Meeting
i. Resolve V4.01 issues
ii. Next steps for V4.01: “only” CS02 or also OS?
iii. Data Aggregation
iv. OData-OpenAPI Mapping
v. REST-EZ
vi. Vocabularies
i. September (one of CW 36 to 39)
ii. 2 days F2F with optional pre-meeting for doc/issue authors
i. Ottawa
ii. Seattle
5.
Review action items [Action item list:
https://www.oasis-open.org/apps/org/workgroup/odata/members/action_items.php] [8:15am PT]
i. None
i. #0037
Concept for Google Protocol Buffers as a data format – Hubert Heijkers – 2018-07-26
i. #0038
Prepare proposal for REST Profile / OData Essentials – Mike Pizzo – 2018-05-03
ii. #0036
Register the OData- headers and preferences with IANA – Mark Biamonte – 2017-11-30
6.
Issues [8:20 am PT]
i. ODATA-1040 Clarification of term "_expression_"
ii. ODATA-1038 Clarify term "simple value"
iii. ODATA-977 Allow POST with $apply
to invoke an action to an aggregated result
iv. ODATA-972 Example 30: wrong result
v. ODATA-971 7.1: Add example for grouping
by single-valued navigation property
vi. ODATA-968 3.1.4: add example for from
in aggregate() with multiple arguments
vii. ODATA-947 Transformation for computing
ratios with aggregated values
viii. ODATA-945 Correct examples 53 and
54
i. 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)
ii. ODATA-1197 Chapter 21 Error Response:
replace misleading "code" values with FOO or BAR
iii. ODATA-1196 Clarify update of media
streams
iv. ODATA-1195 11.2.6.6: value of $search
is search _expression_, not boolean _expression_
v. ODATA-1191 Make sure that all model
elements are annotatable
vi. ODATA-1190 Add matchesPattern as
a $filter function
vii. ODATA-1189 Conformance: Nullable
for collections
viii. ODATA-1188 Allow using instance
annotations in $select and $expand
ix. ODATA-1187 No way to bind nav prop
on recursively nested (contained or complex) type
x. ODATA-1183 Allow Singletons to be
null
xi. ODATA-1180 Cast between enumeration
types and integer types
xii. ODATA-1177 Core: add term SchemaLocation
xiii. ODATA-1171 Consider using matrix
parameters for filter segments
xiv. ODATA-1168 Clarify the use of ETags
for Avoiding Update Conflicts
xv. ODATA-1165 Describe $expand and $select
via prose text and examples, remove ABNF snippets
xvi. ODATA-1148 PATCH with nested nav
props should not remove omitted resources
xvii. ODATA-1143 Extend the Property
metatype to allow a type that is an EntityType.
xviii. ODATA-1141 Upsert: clarify upsert
along nullable single-valued navigation path
xix. ODATA-1135 Document use of JSON
$schema
xx. ODATA-1088 Clarify effect of applying
an Annotation to an element
i. ODATA-1194 Add term Core.Example to
allow including annotation examples in term definitions
ii. ODATA-1192 Capabilities vocabulary:
invalid DefaultValue for KeyAsSegmentSupported
iii. ODATA-1176 Capabilities: add new
term SelectRestrictions
iv. ODATA-1167 Add way to specify which
batch formats (if any) are supported by a service
v. ODATA-1064 Add ability to annotate
collections to return only count and NextLink
i. ODATA-1199 ODATA-884 Add property
SystemQueryOptions to call out supported system query options per request method
ii. ODATA-1193 Automated vocabulary checks
indicate some potential issues
iii. ODATA-1099 Add annotations to describe
custom query options and custom headers
iv. ODATA-1005
Make sure we have capabilities for all new 4.01 functionality
v. 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]