RE: Agenda for OData TC meeting on 2018-11-29

[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 November 29, 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=46284

2.Approve agenda [8:05 am PT]

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

a.Minutes from November 15, 2018 TC meeting: https://www.oasis-open.org/committees/download.php/64263/odata-meeting-237_on-20181115-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-1206 Explicitly note support for collection-valued navigation/complex properties in property paths in aggregate/groupby

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

ii.ODATA-1188 Allow using instance annotations in $select and $expand

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

iii.ODATA-1114 If-Then-Else in $batch requests

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

2.https://www.oasis-open.org/committees/download.php/64120/odata-json-format-v4.01-wd06-2018-10-19.docx

b.Vocabularies: NEW or OPEN with concrete proposal

i.ODATA-1200 ODATA-884 / Support sample values for types, parameters, request/response bodies

ii.ODATA-1194 Add term Core.Example to allow including annotation examples in term definitions

iii.ODATA-1176 Capabilities: add new term SelectSupport

c.V4.01: NEW or OPEN

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

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

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

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

v.ODATA-1261 Allow $pagesize system query option

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

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

viii.ODATA-1258 Should we allow arrays of primitive in term definitions?

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

x.ODATA-1254 Can the default set of properties change over time?

xi.ODATA-1250 GeoJSON, SRID, and LineString

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

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

xiv.ODATA-1226 Ambiguity with Capabilities.ChangeTracking annotation

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

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

xvii.ODATA-1246 Allow BaseType to be a ComplexType

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

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

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

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

xxii.ODATA-1135 Document use of JSON $schema

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

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

d.Data Aggregation: NEW or OPEN

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

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

iii.ODATA-1218 Transformations for recursive hierarchy processing

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

v.ODATA-945 Correct examples 53 and 54

e.Vocabularies: NEW or OPEN that need more discussion

i.ODATA-1214 Annotate constructor actions

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

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

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

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

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 06, 2018 during 8-10 am PST (17:00-19:00 CET)

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

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

d.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:03] anonymous morphed into Ramesh Reddy (RedHat)

[17:03] Ralf Handl: Voting Members: 4 of 11 (36%) (used for quorum calculation)

[17:04] anonymous morphed into Mike Pizzo

[17:04] Ralf Handl: Voting Members: 5 of 11 (45%) (used for quorum calculation)

[17:05] Ralf Handl: Voting Members: 6 of 11 (54%) (used for quorum calculation)

[17:06] Ralf Handl: Voting Members: 7 of 11 (63%) (used for quorum calculation)

[17:06] Ralf Handl: Achieved quorum: yes

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

[17:07] Ralf Handl: Gerald wants to discuss ii.ODATA-1244 Extend compute to work with aggregated values calculated from the input set after the applied issues

[17:08] Ralf Handl: Mike wants to discuss

[17:08] Ralf Handl: x.ODATA-1254 Can the default set of properties change over time?

[17:08] Ralf Handl: ix.ODATA-1257 Do URLs within a Batch Request need to be URL Encoded?

[17:08] Ralf Handl: viii.ODATA-1258 Should we allow arrays of primitive in term definitions?

[17:09] Ralf Handl: Discuss after Data Aggregation, time-boxed to 30 minutes

[17:10] Ralf Handl: Agenda is approved with these changes

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

a.Minutes from November 15, 2018 TC meeting: https://www.oasis-open.org/committees/download.php/64263/odata-meeting-237_on-20181115-minutes.html

[17:10] Ralf Handl: Minutes are approved

[17:10] 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:11] Ralf Handl: Mark updated the change history section and forwarded the document to Chet Ensign

[17:11] Ralf Handl: Mark will follow up on Monday

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

a.APPLIED

i.ODATA-1206 Explicitly note support for collection-valued navigation/complex properties in property paths in aggregate/groupby

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

[17:15] Ralf Handl: I move to merge https://github.com/oasis-tcs/odata-abnf/pull/13

[17:15] Mike Pizzo: I second

[17:16] Ralf Handl: No objection, motion passes

[17:16] Ralf Handl: ii.ODATA-1188 Allow using instance annotations in $select and $expand

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

[17:20] Mike Pizzo: I move we approve the application of ODATA-1188 to the abnf and merge https://github.com/oasis-tcs/odata-abnf/pull/7

[17:20] Ralf Handl: I move to merge https://github.com/oasis-tcs/odata-abnf/pull/7

[17:20] George Ericson (Dell): I second

[17:20] Ralf Handl: No objections, motion passes

[17:21] Ralf Handl: iii.ODATA-1114 If-Then-Else in $batch requests

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

2.https://www.oasis-open.org/committees/download.php/64120/odata-json-format-v4.01-wd06-2018-10-19.docx

[17:23] Ralf Handl: I move to merge https://github.com/oasis-tcs/odata-vocabularies/pull/26

[17:23] George Ericson (Dell): I second

[17:23] Ralf Handl: No objections, motion passes

[17:24] Ralf Handl: ii.ODATA-1244 Extend compute to work with aggregated values calculated from the input set

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

[17:28] Gerald Krause (SAP): excerpt from ABNF proposal:

[17:28] Gerald Krause (SAP): aggregateMethodCallExpr = 'aggregate' OPEN BWS aggregateFunctionExpr BWS CLOSE

aggregateFunctionExpr   = commonExpr aggregateWith [ aggregateFrom ]

[17:30] Gerald Krause (SAP): GET ~/Sales?$apply=

compute(Amount div aggregate(aggregate(Amount with sum) with average) as RelativeOrderSize)

[17:51] Gerald Krause (SAP): GET ~/Sales?$apply=groupby((Customer),compute(aggregate(Amount with sum) as TotalAmount))

[17:56] Gerald Krause (SAP): https://issues.oasis-open.org/projects/ODATA/issues/ODATA-1244?filter=allopenissues

[18:00] Ralf Handl: Agreement on functionality

[18:00] Ralf Handl: More examples needed

[18:00] Ralf Handl: Concise prose text needed

[18:01] Ralf Handl: Gerald to rework proposal, and ideally align with Hubert up-front

[18:02] Gerald Krause (SAP): Clarify input set for lambda operators

[18:04] Ralf Handl: Mike is capturing his comments in the Jira issue

[18:04] Ralf Handl: x.ODATA-1254 Can the default set of properties change over time?

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

[18:09] Ralf Handl: ODATA-1254 is OPEN

[18:09] Mike Pizzo: I move to resolve ODATA_1254 as proposed

[18:09] Matt Borges (SAP): I second

[18:10] Ralf Handl: ODATA-1254 is RESOLVED as proposed

[18:10] Ralf Handl: ix.ODATA-1257 Do URLs within a Batch Request need to be URL Encoded?

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

[18:12] Ralf Handl: ODATA-1257 is OPEN

[18:18] Ralf Handl: Only the initial producer of a relative URL knows that it is a relative URL, and whether parts of the URL need to be encoded or not

[18:19] Ralf Handl: Critical are: colons in relative URLs, they MUST be percent-encoded to not confuse them with the scheme separator

[18:19] Ralf Handl: Also critical: forward slashes within path segments that are not supposed to separate path segments also need to be percent-encoded

[18:20] Ralf Handl: The latter holds for relative and absolute URLs

[18:30] Mike Pizzo: URLs must be percent encoded in the request, including in a multipart batch request

URLs represented as string within a JSON payload, including JSON batch, do not need url encoding.

However, that means that relative URLs used in these places MUST be safely encoded. Need to define what safely encoded means - colons within the path must be encoded, (and forward-slashes used within data values) percent-encoded.  Question marks within path must be encoded, and hashes must be encoded.

[18:31] Mike Pizzo: URLs must be fully percent encoded in the request, including in a multipart batch request

URLs represented as string within a JSON payload, including JSON batch, must be safely encoded. Need to define what safely encoded means - colons within the path must be encoded, (and forward-slashes used within data values) percent-encoded.  Question marks within path must be encoded, and hashes must be encoded.

[18:32] Mike Pizzo: Must colons within the querystring be encoded?

[18:34] Ralf Handl: Mike to craft a proposal

[18:35] Ralf Handl: viii.ODATA-1258 Should we allow arrays of primitive in term definitions?

[18:38] Ralf Handl: ODATA-1258 is OPEN

[18:38] Ralf Handl: Add parameters to the list of places that don't allow collection of primitive

[18:38] Mike Pizzo: Yes.

[18:39] Mike Pizzo: Proposal:

Clarify that Collection(Edm.Primitive) cannot be used in properties, term definitions, parameters, or type definitions.

[18:39] Mike Pizzo: I move to resolved ODATA-1258 as proposed.

[18:39] Mark Biamonte (Progress)1: I second

[18:40] Ralf Handl: ODATA-1258 is RESOLVED with the modified proposal

[18:40] Ralf Handl: 6.Next meetings [9:50 am PT]

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

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

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

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

[18:42] Ralf Handl: Mike: figure out during December meetings whether to have meetings on January 03 and 10 - Mike would moderate

[18:42] Ralf Handl: b.Vocabularies: NEW or OPEN with concrete proposal

i.ODATA-1200 ODATA-884 / Support sample values for types, parameters, request/response bodies

[18:43] Ralf Handl: ii.ODATA-1194 Add term Core.Example to allow including annotation examples in term definitions

[18:43] Ralf Handl: https://github.com/oasis-tcs/odata-vocabularies/pull/16

[18:56] Ralf Handl: I move to resolve ODATA-1194 and ODATA-1200 as proposed and merge https://github.com/oasis-tcs/odata-vocabularies/pull/16

[18:57] Mike Pizzo: I second

[18:58] Ralf Handl: ODATA-1194 and ODATA-1200 are RESOLVED as proposed

[18:58] Ralf Handl: I move to close ODATA-1194 and ODATA-1200 as applied in the pull request

[18:58] Mike Pizzo: I second

[18:58] Ralf Handl: ODATA-1194 and ODATA-1200 are CLOSED as applied

[18:59] Ralf Handl: 7.AOB and wrap up [9:55 am PT]

[18:59] Ralf Handl: Meeting is adjourned

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

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

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

2. Approve agenda [8:05 am PT]

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

Minutes from November 15, 2018 TC meeting: https://www.oasis-open.org/committees/download.php/64263/odata-meeting-237_on-20181115-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]

Upcoming

i. #0037 Concept for Google Protocol Buffers as a data format – Hubert Heijkers – 2018-12-06

In progress

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

5. Issues [8:20 am PT]

APPLIED

i. ODATA-1206 Explicitly note support for collection-valued navigation/complex properties in property paths in aggregate/groupby

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

ii. ODATA-1188 Allow using instance annotations in $select and $expand

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

iii. ODATA-1114 If-Then-Else in $batch requests

Vocabularies: NEW or OPEN with concrete proposal

i. ODATA-1200 ODATA-884 / Support sample values for types, parameters, request/response bodies

ii. ODATA-1194 Add term Core.Example to allow including annotation examples in term definitions

iii. ODATA-1176 Capabilities: add new term SelectSupport

V4.01: NEW or OPEN

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

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

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

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

v. ODATA-1261 Allow $pagesize system query option

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

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

viii. ODATA-1258 Should we allow arrays of primitive in term definitions?

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

x. ODATA-1254 Can the default set of properties change over time?

xi. ODATA-1250 GeoJSON, SRID, and LineString

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

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

xiv. ODATA-1226 Ambiguity with Capabilities.ChangeTracking annotation

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

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

xvii. ODATA-1246 Allow BaseType to be a ComplexType

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

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

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

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

xxii. ODATA-1135 Document use of JSON $schema

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

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

Data Aggregation: NEW or OPEN

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

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

iii. ODATA-1218 Transformations for recursive hierarchy processing

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

v. ODATA-945 Correct examples 53 and 54

Vocabularies: NEW or OPEN that need more discussion

i. ODATA-1214 Annotate constructor actions

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

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

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

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

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]

Thursday December 06, 2018 during 8-10 am PST (17:00-19:00 CET)
Thursday December 13, 2018 during 8-10 am PST (17:00-19:00 CET)
Thursday December 20, 2018 during 8-10 am PST (17:00-19:00 CET)
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

odata message