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

Chat room record:

[7:48] Room information was updated by: Stefan

Please register at https://www.oasis-open.org/apps/org/workgroup/odata/event.php?event_id=41448 as usual. Thanks.

[7:48] Stefan: Voting Members: 1 of 13 (7%) (used for quorum calculation)

[7:49] Room information was updated by: Stefan

Please register at https://www.oasis-open.org/apps/org/workgroup/odata/event.php?event_id=41448 as usual. Thanks.

Link to current tentative agenda draft for today: https://www.oasis-open.org/apps/org/workgroup/odata/email/archives/201602/msg00006.html

[7:59] Stefan: Voting Members: 4 of 13 (30%) (used for quorum calculation)

[8:01] Stefan: We have quorum: Voting Members: 7 of 13 (53%) (used for quorum calculation)

[8:01] Mike Pizzo: Link to dial-in: https://sap.emea.pgiconnect.com/OData-TC/

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

[8:03] Ralf Handl (SAP): Voting Members: 9 of 13 (69%) (used for quorum calculation)

[8:03] Ralf Handl (SAP): Achieved quorum: yes

[8:07] Mike Pizzo: Woohoo!

[8:08] Ralf Handl (SAP): +1

[8:17] Ram (Microsoft): Minutes from previous meeting approved unanimously. No objections

[8:17] Ram (Microsoft): Agenda approved with one correction: We will wait for Gerald to discuss the issues on set operations.

[8:20] Ram (Microsoft): V4.01 issues

[8:20] Ram (Microsoft): Simplified Syntax: Proposal by Mike Pizzo: OData 4.1 URL Syntax Simplification Proposal

[8:20] Ram (Microsoft): https://www.oasis-open.org/apps/org/workgroup/odata/email/archives/201511/msg00007.html

Room Information:

Please register at https://www.oasis-open.org/apps/org/workgroup/odata/event.php?event_id=41448 as usual. Thanks.

Link to current tentative agenda draft for today: https://www.oasis-open.org/apps/org/workgroup/odata/email/archives/201602/msg00006.html

[9:06] Ram (Microsoft)1: ODATA-812  Allow omitting namespaces for unambiguous functions/actions

[9:06] Ram (Microsoft)1: ODATA-812  Allow omitting namespaces for unambiguous functions/actions

[9:06] Ram (Microsoft)1: Issue is now open. No objections.

[9:12] Ram (Microsoft)1: Mike to open separate issue for include annotations

[9:13] Mike Pizzo: I propose we approve ODATA-812 as proposed.

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

[9:17] Ram (Microsoft)1: Motion passes, no objections

[9:17] Ram (Microsoft)1: ODATA-834  Make type prefix optional for enumeration literals in URLs

[9:18] Ram (Microsoft)1: ODATA-834 is now open. No objections.

[9:19] Mike Pizzo: I move we approve ODATA-834 as proposed.

[9:19] Ralf Handl (SAP): I second

[9:19] Ram (Microsoft)1: Motion passes, no objections

[9:20] Ram (Microsoft)1: ODATA-834 has been resolved.

[9:20] Ram (Microsoft)1: ODATA-563  5.1.1.4.29: Allow casting strings to primitive types if the string contains the literal representation of an instance of the target type

[9:25] Ralf Handl (SAP): I move to resolve ODATA-563 as proposed

[9:25] Martin Zurmuehl (SAP): I second

[9:26] Ram (Microsoft)1: Motion passes, no objections, ODATA-563 is resolved.

[9:31] Ralf Handl (SAP): I move to extend ODATA-834 to also allow omitting the prefix for duration literals

[9:31] Mark Biamonte (Progress): I seceond

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

[9:34] Ralf Handl (SAP): I move to resolve ODATA-834 again with the scope extended to duration literals

[9:34] Ram (Microsoft)1: No objections, the scope of ODATA-834 has been extended.

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

[9:36] Ram (Microsoft)1: Motion passes, no objections, the change (addition) to ODATA-834 resolution has been approved as documented in the Jira ticket.

[9:37] Ram (Microsoft)1: ODATA-799  Define Key-As-Segment URL convention for resource paths

[9:45] Ram (Microsoft)1: ODATA-799 is now open. No objections.

[9:46] Martin Zurmuehl (SAP): I move to resolve ODATA-799 as proposed

[9:46] Mike Pizzo: I second.

[9:47] Ram (Microsoft)1: Motion passes, no objections, ODATA-799 has been resolved.

[9:47] Ram (Microsoft)1: ODATA-556  Add "in" operator as syntactic sugar for a chain of "or" expressions

[9:58] Ralf Handl (SAP): I move to resolve ODATA-556 as proposed

[9:58] Martin Zurmuehl (SAP): I second

[9:58] Ram (Microsoft)1: Motion passes, no objections, ODATA-556 has been resolved.

[9:59] Stefan3: @Ralf: The link to the dial-in does not work from within my corporate network (looping request on client certificate)

[10:00] Ram (Microsoft)1: next meeting Feb 11, 2016 as scheduled.

[10:00] Ram (Microsoft)1: meeting adjourned.

From: Ram Jeyaraman
Sent: February 3, 2016 5:42 PM
To: odata@lists.oasis-open.org
Subject: Agenda for OData TC meeting on 2016-02-04

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

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

Approve agenda [8:05am PT]

Approve minutes from previous meeting(s) [8:10am PT]
1. Minutes from Jan 28, 2016 TC meeting: https://www.oasis-open.org/apps/org/workgroup/odata/download.php/57436/odata-meeting-118_on-20160128-minutes.html

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]

OData v4 international standardization update [8:20am PT]

V4.01 [8:30am PT]
1. 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-812 Allow omitting namespaces for unambiguous functions/actions

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

4. ODATA-799 Define Key-As-Segment URL convention for resource paths

5. ODATA-834 Make type prefix optional for enumeration literals in URLs

6. ODATA-563 5.1.1.4.29: Allow casting strings to primitive types if the string contains the literal representation of an instance of the target type

7. ODATA-556 Add "in" operator as syntactic sugar for a chain of "or" expressions

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

vii. Other

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

2. ODATA-900 Cross-service navigation and service versioning

3. ODATA-889 Make edm.json a stand-alone schema

4. ODATA-898 Note the different sets of properties to be expected within atom:content

Next meeting [9:50am PT]
1. Thursday February 11, 2016 during 8-10am PT?

AOB and wrap up [9:55am PT]

odata message