← Prev in month ← Prev in thread

Agenda for OData TC meeting 2016-05-05

From
Ram Jeyaraman <>
Date
2016-05-05T05:46:50+00:00
ID
Thread
Agenda for OData TC meeting 2016-05-05
Here [1] is the agenda for the OData TC (Technical Committee) meeting
scheduled on Thursday May 5, 2016 during 8-10am Pacific Time. 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] 

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

 

Approve agenda [8:05am]

 

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

Minutes from April 21, 2016 TC meeting:

https://www.oasis-open.org/apps/org/workgroup/odata/download.php/58018/odata-meeting-129_on-20160421-minutes.html

 

Review action items [Action item list:

https://www.oasis-open.org/apps/org/workgroup/odata/members/action_items.php] [8:15am]

Action items due 

                                                   
i.     #0032:

Overview presentation on HTTP/2 features (due May 19, 2016)

                                                  
ii.     #0035:

Identify the right open source license for the OASIS Open Source repositories for vocabularies and libraries (due March 31, 2016)

 

5.     
Review of HTTP/2 features by Martin Zurmuehl  [8:20am]

 

V4.0 Errata 3 [8:40am]

a.     
ODATA-936: CSDL errata02 11.1.3 Type Definition Facets references nonexistent standard vocabulary

ODATA-934: Clarify invoking an action with no parameters

 

Data aggregation [8:50am]

a.     
Hierarchy discussion 

b.     
Issues

                                              
i.          ODATA-905 Example 67: result row for USA, Sugar missing, Example 68: last total
 should be 7

                                             
ii.          ODATA-904 Example 55: clarify groupby in combination with relationships of
 instance cardinality zero

                                            
iii.          ODATA-909 ABNF for pathPrefix should also allow qualified ComplexTypeName

V4.01 issues [9:20am]

a.     
Issues
 for V4.01_WD01 in New or Open state

                                                    
i.          Annotations

1.     
ODATA-516 - Add super type Edm.AnyPath for Edm.PropertyPath, Edm.NavigationPropertyPath, and Edm.AnnotationPath

2.     
ODATA-545 - Allow applying Capability terms CountRestrictions, TopSupported, SkipSupported etc. to all resources returning collections

3.     
ODATA-571 - Add annotation for properties that are (not) part of the default selection if no $select is specified

4.     
ODATA-631 - Allow expressing that a term can be applied any collection and is not restricted to entity sets

5.     
ODATA-735 - Enhance the CSDL for instance annotations

6.     
ODATA-811 - Define propagation and (partial) overriding of annotations

7.     
ODATA-816 - Add Capability term for filter _expression_ restrictions

8.     
ODATA-859 - Define term, semantics for inserting error information into a (mostly) successful
 response

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

                                                  
ii.           OData protocol

1.     
ODATA-920 Specify overflow for int data types

2.     
ODATA-919 Specify the result type for each operation based on operator types

3.     
ODATA-928: Allow client to use OData-SchemaVersion header to indicate the metadata version it is using

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

5.     
ODATA-846: Add version 4.01

                                                 
iii.           Simplified Payload

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

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

                                                 
iv.           New Query Capabilities

1.     
ODATA-614 Allow $expand, $select, ... with POST/PATCH/PUT in combination with return=representation to specify the response shape

2.     
ODATA-827 introduce $compute query option

3.     
ODATA-798 - Semantic Key or Alternate Key for entity types

                                                  
v.          Enumerations

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

2.     
ODATA-494 Define inheritance for enumeration types

3.     
ODATA-874 Allow Edm.String as underlying type for enumeration types

                                                 
vi.           OData CSDL

1.     
ODATA-923:
$expand for $metadata to include referenced schemas

2.     
ODATA-618: Allow using term names in positions that allow type names

3.     
ODATA-929: Nullable facet should default to false for collection types, rather than being unspecified

4.     
ODATA-674:
Specify navigation property binding combined with containment *

5.     
ODATA-935: Allow singletons to be members of an entity set

                                               
vii.           JSON Format

1.     
ODATA-868 - Describe format for In-Stream errors

                                              
viii.          Batch

1.     
ODATA-541 - Allow the If-Match header to reference the ETag that resulted from an earlier operation in a batch request

                                                 
ix.          Complex Types

1.     
ODATA-560 - Allow arbitrary properties in referential constraints

                                                  
x.          Decimal

1.     
ODATA-557 - Allow exponential notation for Edm.Decimal

2.     
ODATA-747 - Allow IEEE 754 constants [-]INF and NaN also for Edm.Decimal and integer types

                                                  
ii.          URL Conventions

1.     
ODATA-933: Allow using instance annotations in $filter

                                                 
iii.          Interfaces

1.     
ODATA-619: Attach action and function signatures to terms, i.e. make a term definition an interface definition

2.     
ODATA-696: Support "interfaces" for casting entities to multiple different types

                                                 
iv.          Set operations

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

 

9.     
OData CSDL JSON [9:40am] 

a.     
Parked issues

                                                   
i.     ODATA-906 Consider how to specify an included namespace as a default in JSON CSDL

                                                  
ii.     ODATA-890 Specify how to get from a JSON message to a JSON schema for validating this
 message

                                                 
iii.     ODATA-863 Represent Terms similar to Types

 

Next meeting [9:50am]

b.     
Thursday May 12, 2016? 

 

AOB and wrap up [9:55am]

 

[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
← Prev in month ← Prev in thread