RE: Agenda for OData TC meeting on 2019-03-21 - chat transcript

["Handl, Ralf" <ralf.handl@sap.com>]

[15:57] Room information was updated by: Ralf Handl (SAP)

Here [1] is a draft agenda for the OData TC (Technical Committee) meeting scheduled on Thursday March 21, 2019 during 8-10 am PDT (16:00-18:00 CET). 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:00 am PT]

a.Self-registration link: https://www.oasis-open.org/apps/org/workgroup/odata/event.php?event_id=47978 

2.Approve agenda [8:05 am PT]

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

a.Minutes from March 07, 2019 TC meeting: not yet available

b.Minutes from March 14, 2019 TC meeting: https://www.oasis-open.org/committees/download.php/64918/Minutes%20of%202019-03-14%20Meeting%20%23251.docx 

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

a.Upcoming

i.#0037 Concept for Google Protocol Buffers as a data format  Hubert Heijkers  2019-03-28

b.In progress

i.#0036 Register the OData- headers and preferences with IANA  Mark Biamonte  2018-07-26

5.Issues [8:20 am PT]

a.APPLIED

i.ODATA-1291 ETags for Collections

1.https://github.com/oasis-tcs/odata-vocabularies/pull/43/files 

2.Only merge pull request

ii.ODATA-1273 Define mapping of permission scopes to resources

1.https://github.com/oasis-tcs/odata-vocabularies/pull/35/files 

b.V4.01: NEW or OPEN

i.ODATA-1284 Allow referencing properties of "outer" entity in expressions nested within $expand

ii.ODATA-1295 Clarify whether new annotation target syntax requires Version=4.01

iii.ODATA-1294 Explicitly state what is returned on create and update

iv.ODATA-1293 Clarify use of etags for optimistic concurrency versus conditional fetch

v.ODATA-1286 What is the meaning of year 0, and negative years

vi.ODATA-1064 Add ability to annotate collections to return only count and NextLink

vii.ODATA-1005 Make sure we have capabilities for all new 4.01 functionality

c.Data Aggregation: NEW or OPEN

i.ODATA-1218 Transformations for recursive hierarchy processing

ii.ODATA-945 Correct examples 53 and 54

d.Vocabularies: NEW or OPEN with concrete proposal

i.ODATA-1287 Annotate a property as "late updatable"

1.https://github.com/oasis-tcs/odata-vocabularies/pull/44/files 

ii.ODATA-1285 ODATA-1099 / Add ReadByKeyRestrictions similar to ReadRestrictions

1.https://github.com/oasis-tcs/odata-vocabularies/pull/41/files 

iii.ODATA-1264 CRUDQ descriptions on entity sets

1.https://github.com/oasis-tcs/odata-vocabularies/pull/40/files 

e.Vocabularies: NEW or OPEN that need more discussion

i.ODATA-1275 Describing and querying "JSON properties"

ii.ODATA-1214 Annotate constructor actions

iii.ODATA-1140 ODATA-884 / Add details to HttpResponse

iv.ODATA-1107 Introduce instance annotation to specify which types an instance "implements"

v.ODATA-1060 Improve specification of element response requirements

vi.ODATA-884 Allow describing possible responses to requests for a particular resource (public comment c201510e00019)

6.Next meetings [9:50 am PT]

a.Thursday March 28, 2019 during 8-10 am PDT (16:00-18:00 CET)  Europe still on winter time

b.Thursday April 04, 2019 during 8-10 am PDT (17:00-19:00 CET)

c.Thursday April 11, 2019 during 8-10 am PDT (17:00-19:00 CET)

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

[2] References

Chat room: https://soaphub.org/conf/room/odatatc 

Conference call & Screen sharing: https://lync.co.sap.com/meet/ralf.handl/Q4QB1098 

Conference call details: https://www.oasis-open.org/apps/org/workgroup/odata/download.php/63673/latest/TC%20meeting%20dial-in%20details.htm 

[3] Timeline

https://www.oasis-open.org/committees/download.php/64563/TC%20Timeline%202019-01-23.docx

 

[15:57] Ralf Handl (SAP): 1.Roll call [8:00 am PT]

a.Self-registration link: https://www.oasis-open.org/apps/org/workgroup/odata/event.php?event_id=47978

[15:58] Ralf Handl (SAP): Voting Members: 1 of 9 (11%) (used for quorum calculation)

 

[15:58] Ted Jones (Red Hat): Hi Ralf.. you may notice two versions of minutes. The second version has corrected attendee information.

 

[16:00] Ralf Handl (SAP): Ok, thanks

[16:00] Ralf Handl (SAP): Voting Members: 4 of 9 (44%) (used for quorum calculation)

[16:03] Ralf Handl (SAP): Voting Members: 7 of 9 (77%) (used for quorum calculation)

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

[16:04] Ralf Handl (SAP): 2.Approve agenda [8:05 am PT]

[16:05] Ralf Handl (SAP): Skip ODATA-1064 for today

[16:05] Ralf Handl (SAP): Skip ODATA-1005

[16:06] Ralf Handl (SAP): Process 5.d after 5.b, skip 5.b for today

[16:06] Ralf Handl (SAP): George: briefly discuss ODATA-1064

[16:07] Ralf Handl (SAP): Agenda is approved with these changes

[16:08] Ralf Handl (SAP): End 15 minutes earlier today

[16:08] Ralf Handl (SAP): 3.Approve minutes from previous meeting(s) [8:10 am PT]

a.Minutes from March 07, 2019 TC meeting: not yet available

b.Minutes from March 14, 2019 TC meeting: https://www.oasis-open.org/committees/download.php/64918/Minutes%20of%202019-03-14%20Meeting%20%23251.docx

[16:09] Ralf Handl (SAP): George will provide minutes for March 07, 2019

[16:09] Ralf Handl (SAP): Minutes from March 14, 2019 are approved

[16:09] Ralf Handl (SAP): 4.Review action items [Action item list: https://www.oasis-open.org/apps/org/workgroup/odata/members/action_items.php?sort_field=due_closed_date] [8:15am PT]

a.Upcoming

i.#0037 Concept for Google Protocol Buffers as a data format  Hubert Heijkers  2019-03-28

[16:10] Ralf Handl (SAP): Shift to April 25, 2019

[16:10] Ralf Handl (SAP): b.In progress

i.#0036 Register the OData- headers and preferences with IANA  Mark Biamonte  2018-07-26

[16:11] Ralf Handl (SAP): Mark to give update next week

[16:11] Ralf Handl (SAP): 5.Issues [8:20 am PT]

a.APPLIED

i.ODATA-1291 ETags for Collections

1.https://github.com/oasis-tcs/odata-vocabularies/pull/43/files 

2.Only merge pull request

[16:13] Ralf Handl (SAP): I move to merge pull request https://github.com/oasis-tcs/odata-vocabularies/pull/43

 

[16:13] Hubert Heijkers (IBM): I second

 

[16:13] Ralf Handl (SAP): No objections, motion passes

[16:13] Ralf Handl (SAP): ii.ODATA-1273 Define mapping of permission scopes to resources

1.https://github.com/oasis-tcs/odata-vocabularies/pull/35/files

 

[16:19] Mike Pizzo (Microsoft): I move to merge https://github.com/oasis-tcs/odata-vocabularies/pull/35/files and close ODATA-1273 as applied

 

[16:19] Hubert Heijkers (IBM): I second

 

[16:20] Ralf Handl (SAP): No objections, motion passed

[16:20] Ralf Handl (SAP): b.V4.01: NEW or OPEN

i.ODATA-1284 Allow referencing properties of "outer" entity in expressions nested within $expand

[16:22] Ralf Handl (SAP): I move to resolve ODATA-1284 as proposed

 

[16:22] Mike Pizzo (Microsoft): I second (for discussion)

 

[16:22] Ralf Handl (SAP): Hubert: concerns regarding "lookback" introduced by $outer

[16:23] Ralf Handl (SAP): Ralf: $alias is more powerful, and more complicated

 

[16:24] Mike Pizzo (Microsoft): Mike: similar concerns, although I do like that $outer addresses the specific scenario without adding a more powerful syntax that may be difficult to support in the general case.

[16:24] Mike Pizzo (Microsoft): Ralf: one problem with alias is that it could conflict with a property. would have to take precedence over the property.

[16:25] Mike Pizzo (Microsoft): Mike: We could address this by specifying the alias names as prefixed by "@"

 

[16:26] Ralf Handl (SAP): GET Foo?$expand=Bar($alias=b;$expand=Baz($filter=Qux eq @b/Qux))

 

[16:27] Mike Pizzo (Microsoft): I think it would be: GET Foo?$expand=Bar($alias=@b;$expand=Baz($filter=Qux eq @b/Qux))

 

[16:28] Ralf Handl (SAP): Alias MUST NOT collide with parameter aliases

[16:28] Ralf Handl (SAP): GET http://host/service/EmployeesByManager(ManagerID=@p1)?@p1=3

 

[16:29] Mike Pizzo (Microsoft): or: GET Foo?$expand=Bar(@b=$it;$expand=Baz($filter=Qux eq @b/Qux))

 

[16:29] Ralf Handl (SAP): GET Foo?$expand=Bar(@b=$this;$expand=Baz($filter=Qux eq @b/Qux))

 

[16:29] Mike Pizzo (Microsoft): three thumbs up

[16:30] Mike Pizzo (Microsoft): Ralf: What is the scope of the alias? Can it be referenced within $expand?

 

[16:31] Ralf Handl (SAP): <TestCase Name="4.11 Inheritance - $expand" Rule="odataRelativeUri">

    <Input>Categories?$expand=Products(@foo=$this)</Input>

  </TestCase>

 

[16:32] Mike Pizzo (Microsoft): Test case passes; it must be good! 

 

[16:32] Ralf Handl (SAP): <TestCase Name="4.11 Inheritance - $expand" Rule="odataRelativeUri">

    <Input>Categories?$expand=Products(@foo=$this;$filter=@foo/Age gt 3)</Input>

  </TestCase>

[16:35] Ralf Handl (SAP): All other parameter alias values are evaluated in the context of the resource identified by the path segment in which they are assigned and passed as literals into the _expression_. Parameter alias value assignments MAY be nested within $expand and $select, in which case they are evaluated relative to the resource context of the $expand or $select.

[16:43] Ralf Handl (SAP): I move to amend the proposal of ODATA-1284

[16:43] Ralf Handl (SAP): as discussed

[16:43] Ralf Handl (SAP): Parameter aliases can be defined within $expand, and as they are evaluated upon assignment $this can be assigned to a "parameter" alias to solve the problem at hand:

GET Foo?$expand=Bar(@b=$this;$expand=Baz($filter=Qux eq @b/Qux))

Add an example in Protocol 11.2.6.1.3 Parameter Aliases

Change "literals" to "values" in last paragraph of 11.2.6.1.3

 

[16:43] Mike Pizzo (Microsoft): I second

 

[16:43] Ralf Handl (SAP): No objection, motion passes

 

[16:44] Mike Pizzo (Microsoft): (motion is amended)

 

[16:44] Ralf Handl (SAP): No objection to the motion to resolve ODATA-1284 with the amended proposal

[16:44] Ralf Handl (SAP): ODATA-1284 is RESOLVED with the amended proposal

[16:46] Ralf Handl (SAP): ii.ODATA-1295 Clarify whether new annotation target syntax requires Version=4.01

[16:46] Ralf Handl (SAP): ODATA-1295 is OPEN

[16:47] Ralf Handl (SAP): Mike: this is stretching the current wording

[16:53] Ralf Handl (SAP): Mike: clients should silently ignore annotations as long as the CSDL document is still well-formed.

 

[16:56] Mike Pizzo (Microsoft): Suggest: wording that conveys our intention. Something like:

[16:56] Mike Pizzo (Microsoft): Unknown or invalid annotations should never result in an error, as long as the payload remains well-formed. Clients SHOULD ignore unknown terms and silently treat unexpected or invalid values (including invalid type, invalid literal _expression_, invalid targets, etc.) as an unknown value for the term.

[16:58] Mike Pizzo (Microsoft): Proposal updated with suggested wording.

[16:59] Mike Pizzo (Microsoft): I move we approve ODATA-1295 with the updated proposal.

 

[16:59] Ted Jones (Red Hat): I second

 

[17:00] Ralf Handl (SAP): ODATA-1295 is RESOLVED with the amended proposal

[17:00] Ralf Handl (SAP): iii.ODATA-1294 Explicitly state what is returned on create and update

[17:01] Ralf Handl (SAP): ODATA-1294 is OPEN

 

[17:01] Hubert Heijkers (IBM): I move to resolve ODATA-1294 as proposed.

 

[17:02] Ted Jones (Red Hat): I second

 

[17:02] Mike Pizzo (Microsoft): I third.

 

[17:02] Ralf Handl (SAP): ODATA-1294 is RESOLVED as proposed

[17:02] Ralf Handl (SAP): iv.ODATA-1293 Clarify use of etags for optimistic concurrency versus conditional fetch

[17:05] Ralf Handl (SAP): ODATA-1293 is OPEN

 

[17:05] Mike Pizzo (Microsoft): I move to resolve ODATA-1293 as proposed

[17:17] Mike Pizzo (Microsoft): I agree to the friendly amendment.

 

[17:17] Hubert Heijkers (IBM): I second

 

[17:19] Ralf Handl (SAP): ODATA-1293 is RESOLVED with the amended proposal

[17:20] Ralf Handl (SAP): v.ODATA-1286 What is the meaning of year 0, and negative years

 

[17:23] Mike Pizzo (Microsoft): Note that support for negative years is service-dependent, but where supported must have the defined semantics.

[17:24] Mike Pizzo (Microsoft): I move to resolve ODATA-1286 as proposed.

 

[17:24] Hubert Heijkers (IBM): I second

 

[17:24] Ralf Handl (SAP): ODATA-1286 is RESOLVED as proposed

[17:24] Ralf Handl (SAP): vi.ODATA-1064 Add ability to annotate collections to return only count and NextLink

 

[17:32] George Ericson (Dell): Motion to close ODATA-1064 without action

 

[17:33] Mike Pizzo (Microsoft): I second

 

[17:33] Ralf Handl (SAP): ODATA-1064 is CLOSED without action

[17:34] Ralf Handl (SAP): Ralf will delete Github branch ODATA-1064 in the vocabs repository

[17:34] Ralf Handl (SAP): d.Vocabularies: NEW or OPEN with concrete proposal

[17:34] Ralf Handl (SAP): ii.ODATA-1285 ODATA-1099 / Add ReadByKeyRestrictions similar to ReadRestrictions

1.https://github.com/oasis-tcs/odata-vocabularies/pull/41/files

 

[17:36] Saurabh Madan: https://github.com/madansr7/readbykeyscopes

 

[17:38] Ralf Handl (SAP): ODATA-1285 is OPEN

 

[17:39] Mike Pizzo (Microsoft): I move to resolve ODATA-1285 as proposed.

 

[17:41] Hubert Heijkers (IBM): I second

 

[17:41] Ralf Handl (SAP): ODATA-1285 is RESOLVED as proposed

[17:41] Ralf Handl (SAP): i.ODATA-1287 Annotate a property as "late updatable"

1.https://github.com/oasis-tcs/odata-vocabularies/pull/44/files

[17:44] Ralf Handl (SAP): Mike: mention "structural" in description

[17:47] Ralf Handl (SAP): ODATA-1287 is OPEN

 

[17:49] Mike Pizzo (Microsoft): I move to resolve ODATA_1287 as proposed.

 

[17:49] George Ericson (Dell): Second

 

[17:49] Ralf Handl (SAP): ODATA-1287 is RESOLVED as proposed

 

[17:50] George Ericson (Dell): Move to close ODATA-1287 as applied

 

[17:50] Hubert Heijkers (IBM): I second

 

[17:50] Ralf Handl (SAP): ODATA-1287 is CLOSED as applied, pull request to be merged

[17:50] Ralf Handl (SAP): 6.Next meetings [9:50 am PT]

a.Thursday March 28, 2019 during 8-10 am PDT (16:00-18:00 CET)  Europe still on winter time

b.Thursday April 04, 2019 during 8-10 am PDT (17:00-19:00 CET)

c.Thursday April 11, 2019 during 8-10 am PDT (17:00-19:00 CET)

[17:51] Ralf Handl (SAP): 7.AOB and wrap up [9:55 am PT]

[17:51] Ralf Handl (SAP): Mike may not make March 28

[17:51] Ralf Handl (SAP): Ted can't make it

[17:52] Ralf Handl (SAP): Ramesh also can't make it

[17:52] Ralf Handl (SAP): Skip meeting on March 28

[17:53] Ralf Handl (SAP): Walk through V4.01 documents on April 04

[17:53] Ralf Handl (SAP): No other business, meeting is adjourned

 

 

From: odata@lists.oasis-open.org <odata@lists.oasis-open.org> On Behalf Of Handl, Ralf
Sent: Donnerstag, 21. März 2019 10:44
To: odata@lists.oasis-open.org
Subject: [CAUTION] [odata] Agenda for OData TC meeting on 2019-03-21

 

Here [1] is a draft agenda for the OData TC (Technical Committee) meeting scheduled on Thursday March 21, 2019 during 8-10 am PDT (16:00-18:00 CET). 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:00 am PT]

1. Self-registration link: https://www.oasis-open.org/apps/org/workgroup/odata/event.php?event_id=47978

 

2.        Approve agenda [8:05 am PT]

 

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

1. Minutes from March 07, 2019 TC meeting: not yet available
2. Minutes from March 14, 2019 TC meeting: https://www.oasis-open.org/committees/download.php/64918/Minutes%20of%202019-03-14%20Meeting%20%23251.docx

 

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

1. Upcoming

                                  i.    #0037 Concept for Google Protocol Buffers as a data format – Hubert Heijkers – 2019-03-28

2. In progress

                                  i.    #0036 Register the OData- headers and preferences with IANA – Mark Biamonte – 2018-07-26

 

5.        Issues [8:20 am PT]

1. APPLIED

                                  i.    ODATA-1291 ETags for Collections

1. https://github.com/oasis-tcs/odata-vocabularies/pull/43/files
2. Only merge pull request

                                 ii.    ODATA-1273 Define mapping of permission scopes to resources

1. https://github.com/oasis-tcs/odata-vocabularies/pull/35/files

 

2. V4.01: NEW or OPEN

                                  i.    ODATA-1284 Allow referencing properties of "outer" entity in expressions nested within $expand

                                 ii.    ODATA-1295 Clarify whether new annotation target syntax requires Version=4.01

                                iii.    ODATA-1294 Explicitly state what is returned on create and update

                                iv.    ODATA-1293 Clarify use of etags for optimistic concurrency versus conditional fetch

                                 v.    ODATA-1286 What is the meaning of year 0, and negative years

                                vi.    ODATA-1064 Add ability to annotate collections to return only count and NextLink

                               vii.    ODATA-1005 Make sure we have capabilities for all new 4.01 functionality

 

3. Data Aggregation: NEW or OPEN

                                  i.    ODATA-1218 Transformations for recursive hierarchy processing

                                 ii.    ODATA-945 Correct examples 53 and 54

 

4. Vocabularies: NEW or OPEN with concrete proposal

                                  i.    ODATA-1287 Annotate a property as "late updatable"

1. https://github.com/oasis-tcs/odata-vocabularies/pull/44/files

                                 ii.    ODATA-1285 ODATA-1099 / Add ReadByKeyRestrictions similar to ReadRestrictions

1. https://github.com/oasis-tcs/odata-vocabularies/pull/41/files

                                iii.    ODATA-1264 CRUDQ descriptions on entity sets

1. https://github.com/oasis-tcs/odata-vocabularies/pull/40/files

 

5. Vocabularies: NEW or OPEN that need more discussion

                                  i.    ODATA-1275 Describing and querying "JSON properties"

                                 ii.    ODATA-1214 Annotate constructor actions

                                iii.    ODATA-1140 ODATA-884 / Add details to HttpResponse

                                iv.    ODATA-1107 Introduce instance annotation to specify which types an instance "implements"

                                 v.    ODATA-1060 Improve specification of element response requirements

                                vi.    ODATA-884 Allow describing possible responses to requests for a particular resource (public comment c201510e00019)

 

6.        Next meetings [9:50 am PT]

1. Thursday March 28, 2019 during 8-10 am PDT (16:00-18:00 CET) – Europe still on winter time
2. Thursday April 04, 2019 during 8-10 am PDT (17:00-19:00 CET)
3. Thursday April 11, 2019 during 8-10 am PDT (17:00-19:00 CET)

 

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

 

[2] References

• Chat room: https://soaphub.org/conf/room/odatatc
• Conference call & Screen sharing: https://lync.co.sap.com/meet/ralf.handl/Q4QB1098
• Conference call details: https://www.oasis-open.org/apps/org/workgroup/odata/download.php/63673/latest/TC%20meeting%20dial-in%20details.htm

 

[3] Timeline

• https://www.oasis-open.org/committees/download.php/64563/TC%20Timeline%202019-01-23.docx