RE: Agenda for OData TC meeting 2016-07-14

[7:35] Room information was updated by: Stefan Hagen

Please register yourself at

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

 

The agenda draft was sent by mail e.g. at

https://www.oasis-open.org/apps/org/workgroup/odata/email/archives/201607/msg00064.html

 

[7:49] Stefan Hagen: Registration is open
 currently: Voting Members: 1 of 13 (7%) (used for quorum calculation)

 

Room Information:

Please register yourself at

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

 

The agenda draft was sent by mail e.g. at

https://www.oasis-open.org/apps/org/workgroup/odata/email/archives/201607/msg00064.html

 

[7:57] Stefan Hagen: Update: Voting Members: 2 of 13 (15%) (used for quorum calculation)

[8:00] Stefan Hagen: Update: Voting Members: 5 of 13 (38%) (used for quorum calculation)

[8:02] Stefan Hagen: Update: Voting Members: 6 of 13 (46%) (used for quorum calculation)

[8:04] Stefan Hagen: Update: Voting Members: 7 of 13 (53%) (used for quorum calculation)

[8:04] Stefan Hagen: It seems we are quorate ...

[8:06] Stefan Hagen: (informative update for scribe): Voting Members: 10 of 13 (76%)
 (used for quorum calculation)

 

[8:07] anonymous morphed into Hubert Heijkers (IBM)

 

[8:07] Ram (Microsoft): Agenda approved, no corrections.

[8:07] Ram (Microsoft): Minutes from June 23rd approved, no corrections, no objections

[8:09] Ram (Microsoft): Action #0036 remains open.

[8:09] Ram (Microsoft): CSDL JSON Document review

[9:13] Ram (Microsoft): There was a side discussion about producing RAML description
 of OData services similar to what we are exploring today with Swagger 2.0. We should discuss this further and see if there is value in doing this.

[9:22] Ram (Microsoft): There was a discussion about the use of X- extensions to
 Swagger or Open API definitions, and how to minimize them. It was observed that it is impossible to fully avoid it. In order to reduce OData specific extensions, we could work with Swagger Open API folks to adopt some of these extensions, or work in IETF to
 enhance JSON Schema capabilities which would over time trickle down to Open API and RAML at some point.

[9:23] Ram (Microsoft): The JSON CSDL document is expected to get to CSD02 in the
 next few months. At that point, we will get more feedback from the Open API specification community.

 

[9:33] Stefan Hagen: meeting adjourned by chair

 

 

From:  [mailto:]
On Behalf Of Handl, Ralf

Sent: July 13, 2016 7:54 AM

To: 

Subject: [odata] Agenda for OData TC meeting 2016-07-14

 

Here [1] is the agenda for the OData TC (Technical Committee) meeting
scheduled on Thursday July 14, 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

 

1.     
Roll call [8:00am]

a.     
Self-registration link:

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

 

2.     
Approve agenda [8:05am]

 

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

b.     
Minutes from June 23, 2016 TC meeting:

https://www.oasis-open.org/committees/download.php/58470/odata-meeting-136_on-20160707-minutes.html

 

4.     
Review action items [Action item list:

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

c.     
Action items due

i.         
#0036:

Register the OData- headers and preferences with IANA (due July 31, 2016)

 

5.     
CSDL JSON

d.     
Document Walk-Through

ii.         
https://www.oasis-open.org/committees/download.php/58502/odata-json-csdl-v4.0-wd02-2016-07-13.docx

 

6.     
V4.01 issues [7:00am]

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

iii.         
Ripe for resolution

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

 

iv.         
OData Protocol

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

3.     
ODATA-942 How should headers applied to a batch affect statements
 within a batch?

 

v.         
Annotations

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

5.     
ODATA-735 Enhance the CSDL for instance annotations

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

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

8.     
ODATA-883 Validation Vocabulary: add MultipleOf term

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

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

11.  
ODATA-960 Absolute paths in annotations, e.g. capabilities depending
 on properties of a singleton

 

vi.         
New Query Capabilities

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

13.  
ODATA-827 introduce $compute query option

14.  
ODATA-933 Allow using instance annotations in $filter

15.  
ODATA-954 Key-As-Segment for multi-part keys

 

vii.         
Set Operations

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

 

viii.         
Enumerations

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

18.  
ODATA-494 Define inheritance for enumeration types

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

 

ix.         
OData CSDL

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

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

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

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

24.  
ODATA-959 Allow path in an edm:key to also use a primitive property
 of a non null-able navigation property (recursively) of the entity type.

 

x.         
JSON Format

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

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

 

xi.         
Interfaces

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

 

7.     
Next meeting [9:55am]

f.      
Thursday July 21, 2016 6-10am PT – again a longer meeting

 

8.     
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