Next in thread →
Next in month →
RE: Agenda for OData TC Face-to-Face meeting part 2 on 2018-09-28
Moved Data Aggregation issues to last position From: <> On Behalf Of Handl, Ralf Sent: Donnerstag, 27. September 2018 15:58 To: Subject: [CAUTION] [odata] Agenda for OData TC Face-to-Face meeting part 2 on 2018-09-28 Here [1] is a draft agenda for the OData TC (Technical Committee) Face-to-Face meeting Part 2 scheduled on Friday September 28, 2018 during 9 am to 3 pm PDT (18:00 to 00:00+1 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. Friday Morning [9:00 am PT] Approve agenda [9:05 am PT] V4.01: NEW or OPEN [09:10 am PT] 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-1168 Clarify the use of ETags for Avoiding Update Conflicts iii. ODATA-1148 PATCH with nested nav props should not remove omitted resources iv. ODATA-1141 Upsert: clarify upsert along nullable single-valued navigation path v. ODATA-1114 If-Then-Else in $batch requests vi. ODATA-1135 Document use of JSON $schema vii. ODATA-1088 Clarify effect of applying an Annotation to an element viii. ODATA-1064 Add ability to annotate collections to return only count and NextLink ix. ODATA-1143 Extend the Property metatype to allow a type that is an EntityType. x. ODATA-1187 No way to bind nav prop on recursively nested (contained or complex) type xi. ODATA-1191 Make sure that all model elements are annotatable 2. Friday Afternoon [1:30 pm PT] Vocabularies: V4.01-related issues i. ODATA-1227 Improve description of filter _expression_ restrictions ii. ODATA-1229 Introduce LocalTime annotation to apply to string datatype iii. ODATA-1226 Ambiguity with Capabilities.ChangeTracking annotation iv. ODATA-1216 Terms for POST/PATCH/PUT with system query options to shape response v. ODATA-1176 Capabilities: add new term SelectSupported vi. ODATA-1005 Make sure we have capabilities for all new 4.01 functionality OpenAPI-related vocabulary issues i. ODATA-1214 Annotate constructor actions ii. ODATA-884 Add term ErrorCodes to describe possible codes in error messages (public comment c201510e00019) iii. ODATA-1200 ODATA-884 / Support sample values for types, parameters, request/response bodies iv. ODATA-1194 Add term Core.Example to allow including annotation examples in term definitions v. ODATA-1140 ODATA-884 / Add details to HTTPResponseCode term vi. ODATA-1099 Add annotations to describe custom query options and custom headers Data Aggregation: NEW or OPEN i. ODATA-945 Correct examples 53 and 54 ii. ODATA-1207 Clarify need for @odata.id in nested response structures iii. ODATA-947 Transformation for computing ratios with aggregated values Miscellaneous 3. Next meetings [2:50 pm PT] Thursday October 04, 2018 during 8-10 am PDT (17:00-19:00 CEST) Thursday October 11, 2018 during 8-10 am PDT (17:00-19:00 CEST) 4. AOB and wrap up [2:55 pm 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
Next in thread →
Next in month →