Agenda for OData TC meeting on 2016-01-21

Here [1] is a draft agenda for the OData TC (Technical Committee) meeting
scheduled on Thursday January 21, 2016 during 8-10am 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

 

Roll call [8:00am PT] 

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

 

Approve agenda [8:05am PT]

 

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

Minutes from Jan 7, 2015 TC meeting:

https://www.oasis-open.org/apps/org/workgroup/odata/download.php/57258/odata-meeting-116_on-20160107-minutes.html  

 

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

 

Next TC F2F meeting [8:20am PT]

Confirmed - In Zürich during March 02 (Wednesday) and March 03 (Thursday), 2016.

Proposed agenda topics: JSON Schema, v4 errata 3, OData 4.1, OData Extensions for Data Aggregation and Temporal Data

Hubert will soon provide information about logistics (location information and related information)

 

Timeline (preferred state of various docs by June 2016) [8:30am PT]

OData v4 Errata (Approved Errata)

OData v4.1 (Committee Specification Draft 01)

Extensions for Data Aggregation (Committee Specification 02) – already in projected state

Extensions for Temporal Data (Committee Specification Draft 01)

OData JSON Schema for CSDL (Committee Specification 01)

 

V4.01 [8:40am PT] 

Issues
 for V4.01_WD01 in New or Open state

                                                   
i.     Simplified Syntax

1.     
ODATA-664             Consider supporting parameterless function imports with no parens

2.     
ODATA-812             Allow omitting namespaces for unambiguous functions/actions

3.     
ODATA-763             Allowing implicit aliasing of parameters (public comment c201412e00001)

4.     
ODATA-799             Define Key-As-Segment URL convention for resource paths

5.     
ODATA-834             Make type prefix optional for enumeration literals in URLs

                                                  
ii.     Adoption Blocker

1.     
ODATA-881             Add support for Edm.Untyped

2.     
ODATA-876             Allow services to return contained entities inline for delta responses

                                                 
iii.     Simplified Payload

1.     
ODATA-561             odata.type shouldn't require "#" for primitive types

2.     
ODATA-630             Consider making odata the default namespace for annotations

3.     
ODATA-813             Allow no metadata for non-OData clients

4.     
ODATA-814             Don't need TargetId in a deleted link for a to 0..1 relationship

5.     
ODATA-818             Omit properties whose value is null or the $metadata-defined default value

6.     
ODATA-809             Define non-message format for final response of async request

                                                 
iv.     Set Operations

1.     
ODATA-666             Define Deep Update and Deep Upsert operations

2.     
ODATA-836             Allow applying actions to a filtered collection of entities

3.     
ODATA-613             Allow POST to entity sets using the delta-response format

4.     
ODATA-615             Allow PATCH and DELETE with $filter on collections to modify or delete all (and only) the matching entities

5.     
ODATA-616             Allow POST to collections of complex and primitive types, and DELETE with $filter

6.     
ODATA-820             Allow indexing into collections

                                                  
v.     Enum Types

1.     
Proposal by Ken Baclawski: 
https://www.oasis-open.org/committees/download.php/56805/DerivationForEnumerations_KenBaclawski.html

2.     
ODATA-494             Define inheritance for enumeration types

3.     
ODATA-849             Add possibility for enumeration types to "extend" another enumeration type

                                                 
vi.     OData CSDL

1.     
ODATA-887:
Should we allow multi-part namespace alias names?

 

V4.0 ERRATA03 [9:40am PT] 

Issues
 for V4.0_ERRATA03 in New or Open state

                                                   
i.     OData Protocol

1.     
ODATA-882: Mismatch between 11.2.6 Requesting Related Entities and 11.2.7 Requesting Entity References [Open]

                                                  
ii.     OData URL Conventions

1.     
ODATA-784:
Need to specify the behaviour of arithmetic operators on Decimal type [Open] [Proposed]

2.     
ODATA-785:
Numeric promotion (on overflow) across "number type families" is undesirable. [Open] [Proposed]

                                                 
iii.     Vocabularies

1.     
ODATA-886:
Need a stable reference to latest/current OASIS OData vocabularies  [Open] [Proposed]

2.     
ODATA-885:
Permissions should apply to more than just properties [Open]

 

Next meeting [9:50am PT] 

Thursday January 28, 2015 during 8-10am PT?

 

AOB and wrap up [9:55am 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/document.php?document_id=56024&wg_abbrev=odata