Agenda for OData TC meeting on 2019-01-31

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

Self-registration link:

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

 

2.       
Approve agenda [8:05 am PT]

 

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

Minutes from January 24, 2019 TC meeting:

https://www.oasis-open.org/committees/download.php/64630/Minutes%20of%202019-01-24%20Meeting%20%23244.docx

 

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]

Upcoming

                                 
i.    #0037

Concept for Google Protocol Buffers as a data format – Hubert Heijkers – 2019-03-28

In progress

                                 
i.    #0036

Register the OData- headers and preferences with IANA – Mark Biamonte – 2018-07-26

 

5.       
Issues [8:20 am PT]

APPLIED

                                 
i.    ODATA-1188 Allow using instance annotations
 in $select and $expand – left-over

https://github.com/oasis-tcs/odata-abnf/pull/15

 

                                
ii.    ODATA-1221
 Apply, as much as possible, our JSON Format to our annotations as well

https://github.com/oasis-tcs/odata-csdl-schemas/pull/6 

https://github.com/oasis-tcs/odata-vocabularies/pull/34

 

V4.01: 
NEW or OPEN 

                                 
i.    ODATA-1278 Deleted Entity: @odata.removed
 possible in addition to @removed?

                                
ii.    ODATA-1277 null and empty paths in
 Annotation Path, Property Path, Navigation Property Path

                               
iii.    ODATA-1276 Explicitly allow the
 minus sign / dash in a search term

                               
iv.    ODATA-1263 Requirement for 204 (No
 Content) with 11.4.3 "Update an Entity" is not backwards compatible

                                
v.    ODATA-1260 Clarify read-write access
 via URLs differing from the canonical/read/edit URL

                               
vi.    ODATA-1259 Clarify @type (@odata.type)
 and metadata=full

                              
vii.    ODATA-1250 GeoJSON, SRID, and LineString

                             
viii.    ODATA-1243 Clarify whether $orderby
 and string comparison with ge, gt, le, lt is language-specific

                               
ix.    ODATA-1242 Clarify that resolved
 relative URIs in batch responses cannot contain content-ID references

                                
x.    ODATA-1238 Clarifications for select-list
 in ContextUrl

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

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

 

                             
xiii.    ODATA-1267 URL Conventions example
 in 5.1.1.5.1 has "bad" whitespace

                             
xiv.    ODATA-1226 Ambiguity with Capabilities.ChangeTracking
 annotation

                              
xv.    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)

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

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

 

Data Aggregation: 
NEW or OPEN

                                 
i.    ODATA-1256 Harmonize usage of custom
 aggregates with structured aggregatable properties

                                
ii.    ODATA-1218 Transformations for recursive
 hierarchy processing

                               
iii.    ODATA-945 Correct examples 53 and
 54

 

Vocabularies: 
NEW or OPEN with concrete proposal

                                 
i.    ODATA-1176 Capabilities: add new term
 SelectSupport

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

 

Vocabularies: 
NEW or OPEN that need more discussion

                                 
i.    ODATA-1275 Describing and querying
 "JSON properties"

                                
ii.    ODATA-1273 Define mapping of permission
 scopes to resources

                               
iii.    ODATA-1264 CRUD descriptions on
 entity sets

                               
iv.    ODATA-1214 Annotate constructor actions

                                
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-1060 Improve specification
 of element response requirements

                             
viii.    ODATA-884 Enable enumerating the
 valid requests and responses for a particular resource.

 

6.       
Next meetings [9:50 am PT]

Thursday Febuary 07, 2019 during 8-10 am PST (17:00-19:00 CET)

Thursday Febuary 14, 2019 during 8-10 am PST (17:00-19:00 CET)

 

7.       
AOB and wrap up [9:55 am 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/64563/TC%20Timeline%202019-01-23.docx