RE: Agenda for OData TC meeting on 2016-02-11

[Ram Jeyaraman <Ram.Jeyaraman@microsoft.com>]

Raw notes from the chat room:

[7:52] Ram (Microsoft): Self-registration link: https://www.oasis-open.org/apps/org/workgroup/odata/event.php?event_id=41449

[7:54] Ram (Microsoft): Dial-in info: https://www.oasis-open.org/apps/org/workgroup/odata/download.php/56760/latest

[8:02] Ram (Microsoft): We are awaiting the start of the conference bridge.

 

[8:03] anonymous morphed into Matt Borges (SAP)

 

[8:04] Ralf Handl (SAP): Voting Members: 8 of 13 (61%) (used for quorum calculation)

[8:04] Ralf Handl (SAP): Quorum achieved

[8:04] Ralf Handl (SAP): 2. Approve agenda

[8:04] Ralf Handl (SAP): Agenda is approved

[8:05] Ralf Handl (SAP): 3. Approve minutes from previous meeting(s)

[8:05] Ralf Handl (SAP): a.Minutes from Feb 4, 2016 TC meeting: https://www.oasis-open.org/apps/org/workgroup/odata/download.php/57480/odata-meeting-119_on-20160204-minutes.html

[8:05] Ralf Handl (SAP): Minutes are approved

[8:05] Ralf Handl (SAP): 4. Review action items [Action item list: https://www.oasis-open.org/apps/org/workgroup/odata/members/action_items.php]

[8:05] Ralf Handl (SAP): a.Action items due

i.#0034: Ram to put together the OData vocabularies doc [due: Feb 11, 2016]

[8:06] Ralf Handl (SAP): Ram has added initial content, looks good

 

[8:20] Ram (Microsoft): Ram to request starter docs for v4.01

[8:27] Ram (Microsoft): Editors to get the Errata03 docs ready for review and approval as CSD01.

[8:28] Ram (Microsoft): Section 6. Errata 03 issues

[8:28] Ram (Microsoft): ODATA-886

[8:28] Ram (Microsoft): We will wait for the vocabularies doc to be available (Action: Ram)

[8:28] Ram (Microsoft): ODATA-903: ABNF: should allow cast segment following collection of complex types

[8:30] Ram (Microsoft): Issue is open, no objections

 

[8:30] Mike Pizzo: I move we resolve ODATA-903 as proposed.

 

[8:30] Mark Biamonte (Progress): i second

 

[8:32] Ram (Microsoft): No objections, issue resolved as proposed.

[8:56] Ram (Microsoft): Gerald walks through the latest proposal on set operations (index based collections): https://www.oasis-open.org/apps/org/workgroup/odata/download.php/57438/2016-01-29%20Index-Based%20Operations%20on%20Collections.docx

[8:56] Ram (Microsoft): There is consensus building on the proposal with respect to primitive types, but the group decided to wait until we have consensus on how to treat entity type collections.

[8:57] Ram (Microsoft): This will be tackled at the F2F.

[8:57] Ram (Microsoft): On to issues on Simplified Syntax: Proposal by Mike Pizzo: OData 4.1 URL Syntax Simplification Proposal

[9:02] Ram (Microsoft): ODATA-763  Allowing implicit aliasing of parameters (public comment c201412e00001)

[9:02] Ram (Microsoft): Issue is open, no objections

 

[9:08] Mike Pizzo: Revised proposal: Support only when the function/action is the last segment:

A service may support invoking a function as the last segment in a path by omitting the parens and supplying the named parameters as query options prefixed with the "@" sign (ODATA-763 and ODATA-644). For maximum interoperability, services must continue to support the parens syntax as well.

Precedence rules apply for cases where the function name conflicts with a property name. In particular, the declared property wins over a function, and a function would win over a dynamic property.

[9:20] Mike Pizzo: I move we resolve ODATA-763 as proposed.

 

[9:20] Mark Biamonte (Progress): I second

 

[9:20] Ram (Microsoft): No objections, issue resolved as proposed.

[9:21] Ram (Microsoft): ODATA-664 Consider supporting parameterless function imports with no parens

[9:27] Ram (Microsoft): Issue open, no objections

 

[9:37] Mike Pizzo: Revised proposed wording: For function imports (only), if there are no parameters the service may support an alternate syntax of omitting the parens. For maximum interoperability, the service must still support calling function imports with the parens.

[9:39] Mike Pizzo: Further revised: For function imports with no parameters the service may support an alternate syntax of omitting the parens. For maximum interoperability, the service must still support calling function imports with the parens.

 

[9:40] Mark Biamonte (Progress): I move we resolve OData-664 per the revised proposal

 

[9:40] Ted Jones (Red Hat)2: I second

 

[9:41] Ram (Microsoft): No objections, issue resolved as proposed.

[9:41] Ram (Microsoft): ODATA-881   Add support for Edm.Untyped

[10:00] Ram (Microsoft): Issue needs further contemplation.

[10:01] Ram (Microsoft): Next meeting on Feb 25th. Meeting on Feb 18 canceled.

[10:01] Ram (Microsoft): Meeting adjourned.

 

 

From: Ram Jeyaraman
Sent: February 10, 2016 2:07 PM
To: 'odata@lists.oasis-open.org' <odata@lists.oasis-open.org>
Subject: Agenda for OData TC meeting on 2016-02-11

 

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

 

1. Roll call [8:00am PT]
   1. Self-registration link: https://www.oasis-open.org/apps/org/workgroup/odata/event.php?event_id=41449        

 

2. Approve agenda [8:05am PT]

 

3. Approve minutes from previous meeting(s) [8:10am PT]
   1. Minutes from Feb 4, 2016 TC meeting: https://www.oasis-open.org/apps/org/workgroup/odata/download.php/57480/odata-meeting-119_on-20160204-minutes.html  

                                                    i.     To do: Relating to ODATA-812, Mike to open a separate issue for include annotations

 

4. Review action items [Action item list: https://www.oasis-open.org/apps/org/workgroup/odata/members/action_items.php] [8:15am PT]
   1. Action items due

                                                    i.     #0034: Ram to put together the OData vocabularies doc [due: Feb 11, 2016]

 

5. Timeline (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)

 

6. V4.0 ERRATA03 [8:20am PT]

1. Issues for V4.0_ERRATA03 in New or Open state

                                                    i.     Vocabularies

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

                                                   ii.     ABNF

1.      ODATA-903: ABNF: should allow cast segment following collection of complex types [New]

7. V4.01 [8:30am PT]

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

                                                    i.     Set Operations

Revised proposal by Gerald Krause: https://www.oasis-open.org/apps/org/workgroup/odata/download.php/57438/2016-01-29%20Index-Based%20Operations%20on%20Collections.docx

1.      ODATA-820   Allow indexing into collections

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

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

                                                   ii.     Simplified Syntax

Proposal by Mike Pizzo: OData 4.1 URL Syntax Simplification Proposal

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

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

                                                  iii.     Adoption Blocker

1.      ODATA-881   Add support for Edm.Untyped

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

                                                   v.     OData CSDL

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

2.      ODATA-894 Support complex property overwriting in derived type [proposed]

3.      ODATA-895 Support keyless entities for singleton

                                                  vi.     URL Conventions

1.      ODATA-617Allow eq/ne comparison of instances of same structured (complex or entity) type, allow eq/ne comparison with null for 0..1 nav props

2.      ODATA-572Clarify that eq, ne can be used with complex type

3.      ODATA-897 Allow the count of a filtered/searched collection in common expressions (proposed)

4.      ODATA-888 Allow $search for all collections

5.      ODATA-482 Allow inlining stream properties and media resources

6.      ODATA-901 substring: Define negative index for substring function

8. Next meeting [9:50am PT]

3. Thursday February 18, 2016 during 8-10am PT?

 

9. AOB and wrap up [9:55am PT]