OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

odata message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: Agenda for OData TC meeting on 2018-08-16


Here [1] is a draft agenda for the OData TC (Technical Committee) meeting scheduled on Thursday August 16, 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]

    1. Self-registration link: https://www.oasis-open.org/apps/org/workgroup/odata/event.php?event_id=46269

 

2.        Approve agenda [8:05 am PT]

 

3.        Approve minutes from previous meeting(s) [8:10 am PT]

    1. Minutes from August 09, 2018 TC meeting: https://www.oasis-open.org/committees/download.php/63694/odata-meeting-224_on-20180809-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]

    1. Done – to be closed

                                  i.    #0038 Prepare proposal for REST Profile / OData Essentials – Mike Pizzo – 2018-08-08

    1. Upcoming

                                  i.    #0037 Concept for Google Protocol Buffers as a data format – Hubert Heijkers – 2018-09-27

    1. Pending

                                  i.    #0036 Register the OData- headers and preferences with IANA – Mark Biamonte – 2018-07-26

 

5.        Face-to-Face Meeting [8:20 am PT]

    1. Location

                                  i.    Redmond – Mike to confirm

    1. Schedule - proposed

                                  i.    Tuesday September 25 to Wednesday September 26, 2018: Pre-Meeting – does not count towards voter eligibility

                                 ii.    Thursday September 27 to Friday September 28, 2018: TC Meeting – counts towards voter eligibility!

    1. Agenda – proposed

                                  i.    Resolve V4.01 issues

                                 ii.    Next steps for V4.01

                                iii.    Data Aggregation

                                iv.    OData-OpenAPI Mapping

                                 v.    REST-EZ

                                vi.    Vocabularies

 

6.        Issues [8:50 am PT]

    1. Data Aggregation: NEW or OPEN

                                  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

 

    1. Vocabularies: Annotation Examples and Example Values for types, parameters, request/response bodies

                                  i.    ODATA-1194 Add term Core.Example to allow including annotation examples in term definitions

                                 ii.    ODATA-1200 ODATA-884 / Support sample values for types, parameters, request/response bodies

 

    1. V4.01: NEW or OPEN

                                  i.    ODATA-1213 Address use of 201 Created for Create Link Requests

                                 ii.    ODATA-1212 Validation term for allowed terms in Annotation Paths

                                iii.    ODATA-1211 ODATA-681 4.2 and 5.1: Explicitly state that an alias MUST NOT be identical to any other alias or namespace in the same document.

                                iv.    ODATA-1210 CSDL ReturnType element needs to specify rules for Nullable and Collection with entity types

                                 v.    ODATA-1203 Allow numeric indexes in Path constructs within annotations

                                vi.    ODATA-1202 Deep update with nested delta items should allow Core.ContentID

                               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-1197 Chapter 21 Error Response: replace misleading "code" values with FOO or BAR

                                ix.    ODATA-1196 Clarify update of media streams

                                 x.    ODATA-1195 11.2.6.6: value of $search is search _expression_, not boolean _expression_

                                xi.    ODATA-1191 Make sure that all model elements are annotatable

                               xii.    ODATA-1190 Add matchesPattern as a $filter function

                              xiii.    ODATA-1189 Conformance: Nullable for collections

                              xiv.    ODATA-1188 Allow using instance annotations in $select and $expand

                               xv.    ODATA-1187 No way to bind nav prop on recursively nested (contained or complex) type

                              xvi.    ODATA-1183 Allow Singletons to be null

                             xvii.    ODATA-1180 Cast between enumeration types and integer types

                            xviii.    ODATA-1177 Core: add term SchemaLocation

                              xix.    ODATA-1171 Consider using matrix parameters for filter segments

                               xx.    ODATA-1168 Clarify the use of ETags for Avoiding Update Conflicts

                              xxi.    ODATA-1165 Describe $expand and $select via prose text and examples, remove ABNF snippets

                             xxii.    ODATA-1148 PATCH with nested nav props should not remove omitted resources

                            xxiii.    ODATA-1143 Extend the Property metatype to allow a type that is an EntityType.

                           xxiv.    ODATA-1141 Upsert: clarify upsert along nullable single-valued navigation path

                            xxv.    ODATA-1135 Document use of JSON $schema

                           xxvi.    ODATA-1088 Clarify effect of applying an Annotation to an element

 

    1. Vocabularies: NEW or OPEN with concrete proposal

                                  i.    ODATA-1212 Validation term for allowed terms in Annotation Paths

                                 ii.    ODATA-1209 Term for original OData version of (auto-)converted $metadata

                                iii.    ODATA-1204 Vocabularies Document references OData Version 4.01. Part 3: Common Schema Definition Language (CSDL)

                                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

 

    1. Vocabularies: NEW or OPEN that need more discussion

                                  i.    ODATA-1208 Specify the finest possible granularity for Duration

                                 ii.    ODATA-1199 ODATA-884 / Add property SystemQueryOptions to call out supported system query options per request method

                                iii.    ODATA-1193 Automated vocabulary checks indicate some potential issues

                                iv.    ODATA-1177 Allow referencing a (JSON) schema for Edm.Untyped properties

                                 v.    ODATA-1140 ODATA-884 / Add details to HTTPResponseCode term

                                vi.    ODATA-1107 Introduce instance annotation to specify which types an instance "implements"

                               vii.    ODATA-1099 Add annotations to describe custom query options and custom headers

                              viii.    ODATA-1005 Make sure we have capabilities for all new 4.01 functionality

                                ix.    ODATA-884 Add term ErrorCodes to describe possible codes in error messages (public comment c201510e00019)

 

7.        Next meetings [9:50 am PT]

    1. Thursday August 23, 2018 during 8-10 am PDT (17:00-19:00 CEST)
    2. Thursday August 30, 2018 during 8-10 am PDT (17:00-19:00 CEST)

 

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]