[odata] Agenda for OData TC meeting on 2017-08-31

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

Self-registration link:

https://www.oasis-open.org/apps/org/workgroup/odata/event.php?event_id=43993 

 

2.       
Approve agenda [8:05 am PT]

 

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

Minutes from August 24, 2017 TC meeting:

https://www.oasis-open.org/apps/org/workgroup/odata/download.php/61447/latest/odata-meeting-184_on-20170824-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]

Action items due

                                 
i.    None

 

5.       
Data Aggregation [8:20 am PT]

Gerald to walk us through the proposal on

                                 
i.    Grid-Like
 Access to Aggregated Data.docx

 

6.       
Version 4.01 Public Review - 05 July 2017 to 03 August 2017 [9:20 am PT]

Issues

                                 
i.    ODATA-1100 Add mechanism for specifying
 match type for $search

                                
ii.    ODATA-1105 Simplify selection of
 properties of complex type

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

                               
iv.    ODATA-1108 Disallow empty parens
 for implicit parameter syntax

                                
v.    ODATA-1109 Clarify that 'parameter'
 aliases can also be used to substitute expressions

 

7.       
Issues [9:40 am PT]

Vocabularies: 
NEW or OPEN

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

META 1: use issue-specific branches for new terms, types, properties, or add them to master branch and mark them as experimental?

META 2: add examples to term definitions as shown here via annotation Core.Example?

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

                               
iii.    ODATA-1060 Improve specification
 of element response requirements

                               
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)

 

Vocabularies: 
APPLIED

                                 
i.     ODATA-958 Capabilities: FilterRestrictions
 and SortRestrictions for navigation properties

                                
ii.     ODATA-1055 DeepInsertSupport: allow
 applying to entity sets and collection-valued navigation properties

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

                               
iv.    ODATA-1069 New term Core.OperationAvailable

                                
v.    ODATA-1079 Several issues with latest
 standard vocabularies

                               
vi.    ODATA-1082 Add term Constraint to
 Validation vocabulary

                              
vii.    ODATA-1089 Org.OData.Aggregation.V1
 missing Nullable="false" for Function ReturnType

                             
viii.    ODATA-1098 xxxRestrictions can
 be applied more broadly 

 

8.       
Next meetings [9:50 am PT]

Thursday September 07, 2017 during 8-10 am PDT

 

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

 

[2]
References

Conference call details:

https://www.oasis-open.org/apps/org/workgroup/odata/download.php/56760/TC%20meeting%20dial-in%20details.htm

Chat room:
http://webconf.soaphub.org/conf/room/odatatc

 

[3]
Timeline

https://www.oasis-open.org/committees/download.php/59862/TC%20Timeline-2017-01-25.docx