Agenda for OData TC meeting on 2018-11-08

Here [1] is a draft agenda for the OData TC (Technical Committee) meeting scheduled on Thursday November 08, 2018 during 8-10 am 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:00 am PT]

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

2. Approve agenda [8:05 am PT]

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

Minutes from October 25, 2018 TC meeting: https://www.oasis-open.org/committees/download.php/64148/odata-meeting-235_on-20181025-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. Repeatable Requests [8:20 am PT]

https://www.oasis-open.org/committees/document.php?document_id=49687&wg_abbrev=odata

i. This proposed Committee Note has been dormant for some time

Are there other implementations besides SAP’s implementation?
Matt and Evan would like finish the document and get it published

6. Issues [8:50 am PT]

Vocabularies: NEW or OPEN with concrete proposal

i. ODATA-1216 Terms for POST/PATCH/PUT with system query options to shape response

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

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

iv. ODATA-1176 Capabilities: add new term SelectSupport

APPLIED

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

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

ii. ODATA-1203 Allow numeric indexes in Path constructs within annotations

iii. ODATA-1183

iv. ODATA-1170 Allow @odata.type for isomorphy to CSDL XML

v. ODATA-1232 Support Union types

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

vi. ODATA-1229 Introduce LocalDateTime TypeDef to apply to string datatype

vii. ODATA-1208 Specify the finest possible granularity for Duration

viii. ODATA-1202 Deep update with nested delta items should allow Core.ContentID

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

V4.01: NEW or OPEN

i. ODATA-1250 GeoJSON, SRID, and LineString

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-1165 Describe $expand and $select via prose text and examples, remove ABNF snippets

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

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

viii. ODATA-1226 Ambiguity with Capabilities.ChangeTracking annotation

ix. ODATA-1251 Should annotated null/default values be omitted/restored?

x. ODATA-1246 Allow BaseType to be a ComplexType

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

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

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

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

xv. ODATA-1135 Document use of JSON $schema

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

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

Data Aggregation: NEW or OPEN

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

ii. ODATA-1218 Transformations for recursive hierarchy processing

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

iv. ODATA-947 Transformation for computing ratios with aggregated values

v. ODATA-945 Correct examples 53 and 54

Vocabularies: NEW or OPEN that need more discussion

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

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

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

iv. ODATA-1214 Annotate constructor actions

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

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

vii. ODATA-1060 Improve specification of element response requirements

7. Next meetings [9:50 am PT]

Thursday November 15, 2018 during 8-10 am PST (17:00-19:00 CET)
Thursday November 22, 2018 during 8-10 am PST (17:00-19:00 CET) – Thanksgiving in the United States – no meeting?
Thursday November 29, 2018 during 8-10 am PST (17:00-19:00 CET)

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