RE: Agenda for OData TC meeting 2016-03-31

One additional item on timeline added inline below – see section 6.

From: odata@lists.oasis-open.org [mailto:odata@lists.oasis-open.org] On Behalf Of Ram Jeyaraman
Sent: March 30, 2016 5:15 PM
To: odata@lists.oasis-open.org
Subject: [odata] Agenda for OData TC meeting 2016-03-31

Here [1] is the agenda for the OData TC (Technical Committee) meeting scheduled on Thursday March 31, 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]
1. Self-registration link: https://www.oasis-open.org/apps/org/workgroup/odata/event.php?event_id=41456

Approve agenda [8:05am]

Approve minutes from previous meeting(s) [8:10am]
1. Minutes from March 24, 2016 TC meeting: https://www.oasis-open.org/apps/org/workgroup/odata/download.php/57830/odata-meeting-125_on-20160324-minutes.html

Review action items [Action item list: https://www.oasis-open.org/apps/org/workgroup/odata/members/action_items.php] [8:15am]
1. 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)

OData v4 international standards [8:20am]

Let’s discuss current status and next steps

Timeline review (deliverables leading up to end of June)

a. March 2016

i. Publish OData v4 International Standards

ii. OData v4 Errata 03 (Committee Specification Draft 01)

iii. OData v4.01 (Working Draft 01) [address key issues]

iv. OData Extensions for Temporal Data (Working Draft 01)

b. April 2016

i. OData JSON Schema for CSDL (Committee Specification Draft 02)

c. May 2016

i. OData v4.01 (Working Draft 02) [address all remaining issues]

ii. OData Extensions for Temporal Data (Working Draft 02)

d. June 2016: Advance OData specs

i. OData v4 Errata 03 (Approved Errata)

ii. OData v4.01 (Committee Specification Draft 01 and start public review)

iii. OData Extensions for Data Aggregation (Committee Specification 02) [identify implementations]

iv. OData Extensions for Temporal Data (Committee Specification Draft 01 and start public review)

v. OData JSON Schema for CSDL (Committee Specification 01)

V4.01 issues [8:30am]

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

i. OData protocol

1. ODATA-480 $batch: remove restriction "within the same change set " for Content-ID referencing

2. ODATA-921 Specify operations for keyless nav props

3. ODATA-920 Specify overflow for int data types

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

5. ODATA-918 Add operator "divideby" that always results in a decimal.

6. ODATA-921: Specify operations for keyless nav props

7. ODATA-926: OData should not require 202 response to be empty

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

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

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

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

v. OData CSDL

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

8. OData JSON CSDL [9:20am]

b. New issues

i. ODATA-925: Define Core term for service/schema/model version

c. Parked issues

i. ODATA-910: Consider format that is tailored for programmatic access (public comment c201602e00002)

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

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

iv. ODATA-863 Represent Terms similar to Types

d. Next steps

i. Discuss next steps for alignment with Swagger JSON schema

Data aggregation [9:30am]

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

OData extension for Temporal Data [9:40am]

Next meeting [9:50am]

b. Thursday April 14, 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

odata message