RE: Agenda for OData TC meeting on 2018-12-05 - chat transcript

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

[17:00] Room information was updated by: Ralf Handl

Here [1] is a draft agenda for the OData TC (Technical Committee) meeting scheduled on Thursday December 05, 2018 during 8-10 am PST (17:00-19: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=46285 

2.Approve agenda [8:05 am PT]

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

a.Minutes from November 29, 2018 TC meeting: https://www.oasis-open.org/committees/download.php/64352/odata-meeting-238_on-20181129-minutes.html 

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  2018-12-06

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-1255 Correct usage of $count

1.https://github.com/oasis-tcs/odata-abnf/pull/12 

b.Data Aggregation:

i.ODATA-1244 Extend compute to work with aggregated values calculated from the input set

ii.ODATA-1072 Annotation to describe supported aggregation methods

c.Vocabularies: NEW or OPEN with concrete proposal

i.ODATA-1176 Capabilities: add new term SelectSupport

ii.ODATA-1099 Add annotations to describe custom query options and custom headers

d.V4.01: NEW or OPEN 

i.ODATA-1257 Do URLs within a Batch Request need to be URL Encoded?

ii.ODATA-1249 edm.xsd: ActionImport and IncludeInServiceDocument

iii.ODATA-1248 csdl.schema.json: add descriptions to all schema elements

iv.ODATA-1245 Extract _expression_ syntax into own sub-section next to $filter

v.ODATA-1263 Requirement for 204 (No Content) with 11.4.3 "Update an Entity" is not backwards compatible

vi.ODATA-1262 Reconsider name of type Edm.Untyped

vii.ODATA-1261 Allow $pagesize system query option

viii.ODATA-1260 Clarify read-write access via URLs differing from the canonical/read/edit URL

ix.ODATA-1259 Clarify @type (@odata.type) and metadata=full

x.ODATA-1250 GeoJSON, SRID, and LineString

xi.ODATA-1243 Clarify whether $orderby and string comparison with ge, gt, le, lt is language-specific

xii.ODATA-1242 Clarify that resolved relative URIs in batch responses cannot contain content-ID references

xiii.ODATA-1226 Ambiguity with Capabilities.ChangeTracking annotation

xiv.ODATA-1165 Describe $expand and $select via prose text and examples, remove ABNF snippets

xv.ODATA-1253 Abstract type definition Core.Number as a super-type of all numeric types

xvi.ODATA-1246 Allow BaseType to be a ComplexType

xvii.ODATA-1239 Define a mechanism to distinguish between inserted and updated entities in a Delta Response

xviii.ODATA-1238 Clarifications for select-list in ContextUrl

xix.ODATA-1198 ETag handling deviations from RFC7232 are avoidable if we consider two kinds of ETag (ETag in response header and ETag in response payload)

xx.ODATA-1168 Clarify the use of ETags for Avoiding Update Conflicts

xxi.ODATA-1135 Document use of JSON $schema

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

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

e.Data Aggregation: NEW or OPEN

i.ODATA-1256 Harmonize usage of custom aggregates with structured aggregatable properties

ii.ODATA-1218 Transformations for recursive hierarchy processing

iii.ODATA-1207 Clarify need for @odata.id in nested response structures

iv.ODATA-945 Correct examples 53 and 54

f.Vocabularies: NEW or OPEN that need more discussion

i.ODATA-1264 CRUD descriptions on entity sets

ii.ODATA-1214 Annotate constructor actions

iii.ODATA-1177 Allow referencing a (JSON) schema for Edm.Untyped properties

iv.ODATA-1140 ODATA-884 / Add details to HTTPResponseCode term

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

vi.ODATA-1060 Improve specification of element response requirements

vii.ODATA-884 Enable enumerating the valid requests and responses for a particular resource.

6.Next meetings [9:50 am PT]

a.Thursday December 13, 2018 during 8-10 am PST (17:00-19:00 CET)

b.Thursday December 20, 2018 during 8-10 am PST (17:00-19:00 CET)

c.Thursday January 03, 2019 during 8-10 am PST (17:00-19:00 CET)  moderated by Mike Pizzo

d.Thursday January 10, 2019 during 8-10 am PST (17:00-19:00 CET)  moderated by Mike Pizzo

e.Thursday January 17, 2019 during 8-10 am PST (17:00-19:00 CET)

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

[2] References

Chat room: http://webconf.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/62637/TC%20Timeline-2018-03-02.docx

 

[17:01] Ralf Handl: Voting Members: 4 of 10 (40%) (used for quorum calculation)

[17:02] Ralf Handl: Voting Members: 5 of 10 (50%) (used for quorum calculation)

[17:02] Ralf Handl: Voting Members: 6 of 10 (60%) (used for quorum calculation)

[17:03] Ralf Handl: Quorum achieved: yes

[17:03] Ralf Handl: Voting Members: 7 of 10 (70%) (used for quorum calculation)

[17:04] Ralf Handl: 2.Approve agenda [8:05 am PT]

[17:05] Ralf Handl: Want to discuss a problem with https://issues.oasis-open.org/browse/ODATA-1221

[17:06] Ralf Handl: After 5.b, before 5.c

[17:07] Ralf Handl: Agenda is approved

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

a.Minutes from November 29, 2018 TC meeting: https://www.oasis-open.org/committees/download.php/64352/odata-meeting-238_on-20181129-minutes.html

[17:07] Ralf Handl: Minutes are approved

[17:08] Ralf Handl: 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  2018-12-06

b.In progress

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

[17:16] Ralf Handl: Move #0037 to 2019-03-28

[17:18] Ralf Handl: #0037: Chet Ensign suggested a change to the registration document, Mark provided a new version

[17:18] Ralf Handl: Chet to send the updated document to IANA

[17:18] Ralf Handl: 5.Issues [8:20 am PT]

a.APPLIED

i.ODATA-1255 Correct usage of $count

1.https://github.com/oasis-tcs/odata-abnf/pull/12

 

[17:33] George Ericson (Dell): For Binary Encoded JSON (BEJ).  This referenced document is a published work in progress spec from DMTF.  It is not final, so could be influenced.  Binary Encoded Json (BEJ) is defined in Clause 8.  See: https://www.dmtf.org/sites/default/files/standards/documents/DSP0218_0.8.0a.pdf.  The context here is Redfish Device Enablement (i.e. very small footprint devices.)

 

[17:36] Ralf Handl: Example in testcase in line 427:    <Input>$apply=groupby((Name),aggregate(Sales($count as SalesCount),Sales(Amount with sum as Total)))</Input>

[17:36] Ralf Handl: Hubert wants to forbid this

 

[17:38] Hubert Heijkers (IBM): I move to reopen ODATA-1255

 

[17:38] George Ericson (Dell): I second the motion to reopen OData 1255.

 

[17:38] Ralf Handl: ODATA-1255 is OPEN again

[17:49] Ralf Handl: Two options

[17:49] Ralf Handl: - forbid $count as a shortcut for "1 with sum"

[17:50] Ralf Handl: - restrict $count as a shortcut for "1 with sum" to the top level of aggregate()

[17:51] Ralf Handl: Side-discussion on $it: not yet defined within $apply, Mike and Hubert hope it will not mean the input collection

[17:53] Ralf Handl: Sales?$apply=groupby((Product/Name),aggregate($count as SalesCount,Amount with sum as Total))

[17:55] Ralf Handl: $count is NOT a synonym for "1 with sum" because $count is 0 for the empty input set, whereas "1 with sum" is null

[17:56] Ralf Handl: Product(42)/Sales?$apply=aggregate($count as Count)

[18:02] Ralf Handl: Product(42)/Sales?$apply=aggregate($it/$count as Count)

 

[18:06] George Ericson (Dell): The values of $count should range from 0 to n.

[18:06] George Ericson (Dell): Never null.

 

[18:09] Ralf Handl: I propose we use option 2

[18:09] Ralf Handl: - restrict $count as a shortcut for "1 with sum" to the top level of aggregate()

[18:09] Ralf Handl: No, wrong

[18:10] Ralf Handl: - restrict $count to the top level of aggregate() with the meaning of "put the number of input records into the result record and name it ..."

[18:11] Ralf Handl: Note: it is NOT "1 with sum"

[18:12] Ralf Handl: $apply=groupby((Name),aggregate(Sales($count as SalesCount),Sales(Amount with sum as Total)))

[18:12] Ralf Handl: This will not be allowed any more

[18:14] Ralf Handl: Make sure that $apply=groupby((Name),aggregate($count as SalesCount,Sales(Amount with sum as Total))) still is allowed

[18:14] Ralf Handl: Make sure that $apply=groupby((Name),aggregate($count as ProductCount,Sales(Amount with sum as Total))) still is allowed

 

[18:17] Hubert Heijkers (IBM): I move to resolve ODATA-1255 as per the amended proposal

 

[18:18] George Ericson (Dell): Second the motion to approve OData-1255 as proposed.

 

[18:18] Ralf Handl: ODATA-1255 is RESOLVED with modified proposal

[18:18] Ralf Handl: b.Data Aggregation:

i.ODATA-1244 Extend compute to work with aggregated values calculated from the input set

[18:20] Ralf Handl: https://issues.oasis-open.org/browse/ODATA-1244

[18:21] Ralf Handl: Issue title changed to: Add a function to determine aggregated values within common expressions

[18:47] Ralf Handl: Rule 

  pathPrefix primitiveProperty aggregateWith [ aggregateFrom ] asAlias

was introduced in https://issues.oasis-open.org/browse/ODATA-1206

 

[19:00] Mike Pizzo: I believe this would *NOT* be supported: $filter=Products/any(p/Sales gt aggregate(Sales with average))

 

[19:01] Ralf Handl: Hubert: aggregate() function would be allowed in /$filter(...) path segment if supported in filter _expression_

 

[19:01] Mike Pizzo: We should discuss this...

 

[19:01] Ralf Handl: 6.Next meetings [9:50 am PT]

a.Thursday December 13, 2018 during 8-10 am PST (17:00-19:00 CET)

b.Thursday December 20, 2018 during 8-10 am PST (17:00-19:00 CET)

c.Thursday January 03, 2019 during 8-10 am PST (17:00-19:00 CET)  moderated by Mike Pizzo

d.Thursday January 10, 2019 during 8-10 am PST (17:00-19:00 CET)  moderated by Mike Pizzo

e.Thursday January 17, 2019 during 8-10 am PST (17:00-19:00 CET)

[19:02] Ralf Handl: Mike not able to moderate January 03

[19:02] Ralf Handl: Hubert cannot attend on January 03

[19:02] Ralf Handl: So skip this one

[19:02] Ralf Handl: 7.AOB and wrap up [9:55 am PT]

[19:03] Ralf Handl: Meeting is adjourned

[19:03] Ralf Handl: Thanks!

 

 

From: odata@lists.oasis-open.org <odata@lists.oasis-open.org> On Behalf Of Handl, Ralf
Sent: Mittwoch, 5. Dezember 2018 11:28
To: odata@lists.oasis-open.org
Subject: [CAUTION] [odata] Agenda for OData TC meeting on 2018-12-05

 

Here [1] is a draft agenda for the OData TC (Technical Committee) meeting scheduled on Thursday December 05, 2018 during 8-10 am PST (17:00-19: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=46285

 

2.        Approve agenda [8:05 am PT]

 

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

1. Minutes from November 29, 2018 TC meeting: https://www.oasis-open.org/committees/download.php/64352/odata-meeting-238_on-20181129-minutes.html

 

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 – 2018-12-06

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-1255 Correct usage of $count

1. https://github.com/oasis-tcs/odata-abnf/pull/12

 

2. Data Aggregation:

                                  i.    ODATA-1244 Extend compute to work with aggregated values calculated from the input set

                                 ii.    ODATA-1072 Annotation to describe supported aggregation methods

 

3. Vocabularies: NEW or OPEN with concrete proposal

                                  i.    ODATA-1176 Capabilities: add new term SelectSupport

                                 ii.    ODATA-1099 Add annotations to describe custom query options and custom headers

 

4. V4.01: NEW or OPEN

                                  i.    ODATA-1257 Do URLs within a Batch Request need to be URL Encoded?

                                 ii.    ODATA-1249 edm.xsd: ActionImport and IncludeInServiceDocument

                                iii.    ODATA-1248 csdl.schema.json: add descriptions to all schema elements

                                iv.    ODATA-1245 Extract _expression_ syntax into own sub-section next to $filter

 

                                 v.    ODATA-1263 Requirement for 204 (No Content) with 11.4.3 "Update an Entity" is not backwards compatible

                                vi.    ODATA-1262 Reconsider name of type Edm.Untyped

                               vii.    ODATA-1261 Allow $pagesize system query option

                              viii.    ODATA-1260 Clarify read-write access via URLs differing from the canonical/read/edit URL

                                ix.    ODATA-1259 Clarify @type (@odata.type) and metadata=full

                                 x.    ODATA-1250 GeoJSON, SRID, and LineString

                                xi.    ODATA-1243 Clarify whether $orderby and string comparison with ge, gt, le, lt is language-specific

                               xii.    ODATA-1242 Clarify that resolved relative URIs in batch responses cannot contain content-ID references

                              xiii.    ODATA-1226 Ambiguity with Capabilities.ChangeTracking annotation

                              xiv.    ODATA-1165 Describe $expand and $select via prose text and examples, remove ABNF snippets

 

                               xv.    ODATA-1253 Abstract type definition Core.Number as a super-type of all numeric types

                              xvi.    ODATA-1246 Allow BaseType to be a ComplexType

                             xvii.    ODATA-1239 Define a mechanism to distinguish between inserted and updated entities in a Delta Response

                            xviii.    ODATA-1238 Clarifications for select-list in ContextUrl

                              xix.    ODATA-1198 ETag handling deviations from RFC7232 are avoidable if we consider two kinds of ETag (ETag in response header and ETag in response payload)

                               xx.    ODATA-1168 Clarify the use of ETags for Avoiding Update Conflicts

                              xxi.    ODATA-1135 Document use of JSON $schema

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

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

 

5. Data Aggregation: NEW or OPEN

                                  i.    ODATA-1256 Harmonize usage of custom aggregates with structured aggregatable properties

                                 ii.    ODATA-1218 Transformations for recursive hierarchy processing

                                iii.    ODATA-1207 Clarify need for @odata.id in nested response structures

                                iv.    ODATA-945 Correct examples 53 and 54

 

6. Vocabularies: NEW or OPEN that need more discussion

                                  i.    ODATA-1264 CRUD descriptions on entity sets

                                 ii.    ODATA-1214 Annotate constructor actions

                                iii.    ODATA-1177 Allow referencing a (JSON) schema for Edm.Untyped properties

                                iv.    ODATA-1140 ODATA-884 / Add details to HTTPResponseCode term

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

                                vi.    ODATA-1060 Improve specification of element response requirements

                               vii.    ODATA-884 Enable enumerating the valid requests and responses for a particular resource.

 

6.        Next meetings [9:50 am PT]

1. Thursday December 13, 2018 during 8-10 am PST (17:00-19:00 CET)
2. Thursday December 20, 2018 during 8-10 am PST (17:00-19:00 CET)
3. Thursday January 03, 2019 during 8-10 am PST (17:00-19:00 CET) – moderated by Mike Pizzo
4. Thursday January 10, 2019 during 8-10 am PST (17:00-19:00 CET) – moderated by Mike Pizzo
5. Thursday January 17, 2019 during 8-10 am PST (17:00-19:00 CET)

 

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

 

[2] References

• Chat room: http://webconf.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/62637/TC%20Timeline-2018-03-02.docx