[odata] Agenda for OData TC meeting on 2018-02-15

["Handl, Ralf" <ralf.handl@sap.com>]

Here [1] is a draft agenda for the OData TC (Technical Committee) meeting scheduled on Thursday February 15, 2018 during 8-10 am PST (17:00-19:00 CET). 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=46243

 

2.        Approve agenda [8:05 am PT]

 

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

1. Minutes from February 08, 2018 TC meeting: https://www.oasis-open.org/committees/download.php/62475/odata-meeting-202_on-20180208-minutes.html

 

4.        Review action items [Action item list: https://www.oasis-open.org/apps/org/workgroup/odata/members/action_items.php] [8:15am PT]

1. Action items due

                                  i.    none

 

5.        V4.01 Committee Specification 01

1. Documents are published

 

6.        V4.0 Errata 04

1. ABNF: cross-apply issues such as “ODATA-987 Allow digits in search phrases”, or just copy V4.01 ABNF over to V4 Errata 04?

                                  i.    Pro: URL Conventions state that ABNF is overly generous and prose specification describes valid constructs, and V4.01 ABNF is super-set of V4

                                 ii.    Pro: removes mental barrier for “downporting” V4.01 features to V4 services/frameworks

                                iii.    Pro: we did the same with the CSDL XML namespaces: http://docs.oasis-open.org/odata/ns/edmx and http://docs.oasis-open.org/odata/ns/edm describe the V4.01 superset.

2. XML Schemas for CSDL: pack latest (V4.01) versions into Errata 04?

                                  i.    Pro: see iii. above, XML namespace documents reference V4.01

3. Prose Specifications

                                  i.    Any issues that need to be (cross-) applied to the prose specification documents?

                                 ii.    Any need to publish Errata 04 for JSON Format?

 

7.        Issues [8:20 am PT]

1. APPLIED

                                  i.    ODATA-1144 Allow percent-encoded colon in time values in URLs

 

2. Vocabularies: NEW or OPEN

                                  i.    ODATA-1121 Add FilterExpressionType values "MultiRange" and "MultiRangeOrSearchExpression"

                                 ii.    ODATA-1138 Facilitate processing of aggregated results created with concat

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

                                iv.    ODATA-1067 Consider ability to define computed default values

                                 v.    ODATA-1064 Add ability to annotate collections to return only count and NextLink

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

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

 

8.        Next meetings [9:50 am PT]

1. Thursday February 22, 2018 during 8-10 am PST?
2. Thursday March 01, 2018 during 8-10 am PST?

 

9.        AOB and wrap up [9:55 am PT]

 

[2] References

• Chat room: http://webconf.soaphub.org/conf/room/odatatc
• Conference call & Screen sharing: https://sap.emea.pgiconnect.com/OData-TC
• Conference call details: https://www.oasis-open.org/apps/org/workgroup/odata/download.php/56760/TC%20meeting%20dial-in%20details.htm

 

[3] Timeline

• https://www.oasis-open.org/committees/download.php/61677/TC%20Timeline-2017-09-29.docx