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

[Michael Pizzo <mikep@microsoft.com>]

As I recall from the call last week, the main topic for today was to go over Ralph's JSON CSDL issues. I don't know that we were planning on taking the full 2 hours.

 

In any case, I am planning on calling in from my car for part of the call, but not all of it.

 

Also, any update on requests for quotes for the ISO approval?

Talk to you shortly,

 

-Mike

 

From: odata@lists.oasis-open.org [mailto:odata@lists.oasis-open.org] On Behalf Of Ram Jeyaraman
Sent: Wednesday, April 6, 2016 4:00 PM
To: odata@lists.oasis-open.org
Subject: [odata] Agenda for OData TC meeting 2016-04-07

 

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

 

2. Approve agenda [8:05am]

 

3. Approve minutes from previous meeting(s) [8:10am]
   1. Minutes from March 31, 2016 TC meeting: https://www.oasis-open.org/apps/org/workgroup/odata/download.php/57850/odata-meeting-126_on-20160331-minutes.html  

 

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

 

5. V4.01 issues [8:20am]

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

                                                               i.            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-918 Add operator "divideby" that always results in a decimal.

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

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

                                                             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

6.       OData JSON CSDL [9:20am]

a.       New issues

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

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

c.       Next steps

                                                               i.      Discuss next steps for alignment with Swagger JSON schema

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

8. Next meeting [9:50am]

b.       Thursday April 14, 2016?

 

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