RE: Agenda for OData TC meeting on 2018-08-16

[17:01] Room information was updated by: Ralf Handl (SAP SE)

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

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

2.Approve agenda [8:05 am PT]

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

a.Minutes from August 09, 2018 TC meeting: https://www.oasis-open.org/committees/download.php/63694/odata-meeting-224_on-20180809-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.Done  to be closed

i.#0038 Prepare proposal for REST Profile / OData Essentials  Mike Pizzo  2018-08-08

b.Upcoming

i.#0037 Concept for Google Protocol Buffers as a data format  Hubert Heijkers  2018-09-27

c.Pending

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

5.Face-to-Face Meeting [8:20 am PT]

a.Location

i.Redmond  Mike to confirm

b.Schedule - proposed

i.Tuesday September 25 to Wednesday September 26, 2018: Pre-Meeting  does not count towards voter eligibility

ii.Thursday September 27 to Friday September 28, 2018: TC Meeting  counts towards voter eligibility!

c.Agenda  proposed

i.Resolve V4.01 issues

ii.Next steps for V4.01

iii.Data Aggregation

iv.OData-OpenAPI Mapping

v.REST-EZ

vi.Vocabularies

6.Issues [8:50 am PT]

a.Data Aggregation: NEW or OPEN

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

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

iii.ODATA-1205 Examples 53, 54, and 59 are not compliant with Data Aggregation ABNF

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

v.ODATA-945 Correct examples 53 and 54

b.Vocabularies: Annotation Examples and Example Values for types, parameters, request/response bodies

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

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

c.V4.01: NEW or OPEN

i.ODATA-1213 Address use of 201 Created for Create Link Requests

ii.ODATA-1212 Validation term for allowed terms in Annotation Paths

iii.ODATA-1211 ODATA-681 4.2 and 5.1: Explicitly state that an alias MUST NOT be identical to any other alias or namespace in the same document.

iv.ODATA-1210 CSDL ReturnType element needs to specify rules for Nullable and Collection with entity types

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

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

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

viii.ODATA-1197 Chapter 21 Error Response: replace misleading "code" values with FOO or BAR

ix.ODATA-1196 Clarify update of media streams

x.ODATA-1195 11.2.6.6: value of $search is search _expression_, not boolean _expression_

xi.ODATA-1191 Make sure that all model elements are annotatable

xii.ODATA-1190 Add matchesPattern as a $filter function

xiii.ODATA-1189 Conformance: Nullable for collections

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

xv.ODATA-1187 No way to bind nav prop on recursively nested (contained or complex) type

xvi.ODATA-1183 Allow Singletons to be null

xvii.ODATA-1180 Cast between enumeration types and integer types

xviii.ODATA-1177 Core: add term SchemaLocation

xix.ODATA-1171 Consider using matrix parameters for filter segments

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

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

xxii.ODATA-1148 PATCH with nested nav props should not remove omitted resources

xxiii.ODATA-1143 Extend the Property metatype to allow a type that is an EntityType.

xxiv.ODATA-1141 Upsert: clarify upsert along nullable single-valued navigation path

xxv.ODATA-1135 Document use of JSON $schema

xxvi.ODATA-1088 Clarify effect of applying an Annotation to an element

d.Vocabularies: NEW or OPEN with concrete proposal

i.ODATA-1212 Validation term for allowed terms in Annotation Paths

ii.ODATA-1209 Term for original OData version of (auto-)converted $metadata

iii.ODATA-1204 Vocabularies Document references OData Version 4.01. Part 3: Common Schema Definition Language (CSDL)

iv.ODATA-1176 Capabilities: add new term SelectRestrictions

v.ODATA-1167 Add way to specify which batch formats (if any) are supported by a service

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

e.Vocabularies: NEW or OPEN that need more discussion

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

ii.ODATA-1199 ODATA-884 / Add property SystemQueryOptions to call out supported system query options per request method

iii.ODATA-1193 Automated vocabulary checks indicate some potential issues

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

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

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

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

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

ix.ODATA-884 Add term ErrorCodes to describe possible codes in error messages (public comment c201510e00019)

7.Next meetings [9:50 am PT]

a.Thursday August 23, 2018 during 8-10 am PDT (17:00-19:00 CEST)

b.Thursday August 30, 2018 during 8-10 am PDT (17:00-19:00 CEST)

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

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

[17:04] Ralf Handl (SAP SE): quorum achieved: yes

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

[17:05] Ralf Handl (SAP SE): Agenda is approved

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

a.Minutes from August 09, 2018 TC meeting: https://www.oasis-open.org/committees/download.php/63694/odata-meeting-224_on-20180809-minutes.html

[17:07] Ralf Handl (SAP SE): 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.Done  to be closed

i.#0038 Prepare proposal for REST Profile / OData Essentials  Mike Pizzo  2018-08-08

b.Upcoming

i.#0037 Concept for Google Protocol Buffers as a data format  Hubert Heijkers  2018-09-27

c.Pending

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

[17:07] Ralf Handl (SAP SE): Sorry

[17:07] Ralf Handl (SAP SE): Minutes are approved

[17:07] Ralf Handl (SAP SE): 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.Done  to be closed

i.#0038 Prepare proposal for REST Profile / OData Essentials  Mike Pizzo  2018-08-08

b.Upcoming

i.#0037 Concept for Google Protocol Buffers as a data format  Hubert Heijkers  2018-09-27

c.Pending

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

[17:11] Michael Pizzo: https://www.oasis-open.org/apps/org/workgroup/odata/download.php/63723/IANA_Header_Registration.docx

[17:15] Michael Pizzo: Updates to links to latest 4.01 specification.

[17:15] Michael Pizzo: https://www.oasis-open.org/apps/org/workgroup/odata/download.php/63722/IANA_Preference_Registration.docx

[17:20] Michael Pizzo: Reviewed updates to links to latest 4.01 specification.

[17:23] Ralf Handl (SAP SE): Mike: remove revision information as IANA hasn't seen previous revisions

[17:23] Ralf Handl (SAP SE): Mark to check with TC Admin

[17:25] Michael Pizzo: I move we task Mark with preparing and submitting to the TC Admin a clean (non-redlined) version of https://www.oasis-open.org/apps/org/workgroup/odata/download.php/63723/IANA_Header_Registration.docx and https://www.oasis-open.org/apps/org/workgroup/odata/download.php/63722/IANA_Preference_Registration.docx, with the revision information removed, for submission to IANA.

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

[17:26] Ralf Handl (SAP SE): No objections, motion passes

[17:26] Ralf Handl (SAP SE): 5.Face-to-Face Meeting [8:20 am PT]

a.Location

i.Redmond  Mike to confirm

b.Schedule - proposed

i.Tuesday September 25 to Wednesday September 26, 2018: Pre-Meeting  does not count towards voter eligibility

ii.Thursday September 27 to Friday September 28, 2018: TC Meeting  counts towards voter eligibility!

c.Agenda  proposed

i.Resolve V4.01 issues

ii.Next steps for V4.01

iii.Data Aggregation

iv.OData-OpenAPI Mapping

v.REST-EZ

vi.Vocabularies

[17:27] Michael Pizzo: https://news.microsoft.com/life/meet-me-in-the-trees/

[17:28] Ralf Handl (SAP SE): Mike: F2F will be in Redmond, most likely building 27

[17:32] Michael Pizzo: Preliminary information on F2F: https://www.oasis-open.org/apps/org/workgroup/odata/email/archives/201808/msg00037.html

[17:34] Ralf Handl (SAP SE): Gerald and Ralf will attend in person

[17:34] Ralf Handl (SAP SE): Mark will attend in person

[17:34] Ralf Handl (SAP SE): Hubert plans to attend

[17:34] Michael Pizzo: Mike will attend

[17:35] Ralf Handl (SAP SE): George, Matt, and Ted will call in

[17:38] Ralf Handl (SAP SE): Mike: keep 2/2 split of pre-meeting and official meeting

[17:42] Ralf Handl (SAP SE): Mike to contact Stefan whether to add "Securing OData"

[17:43] Ralf Handl (SAP SE): Mike: V4.01 top prio

[17:43] Ralf Handl (SAP SE): Gerald: Hierarchies top prio for next edition of Data Aggregation

[17:45] Ralf Handl (SAP SE): Mike: Thursday 8am to 4 pm

[17:46] Michael Pizzo: (Pacific time)

[17:48] Ralf Handl (SAP SE): Ralf to ask Stefan whether this works for him

[17:49] Ralf Handl (SAP SE): Mike: Friday to be decided on Thursday, e.g. 8-4 or 9-4

[17:50] Ralf Handl (SAP SE): 6.Issues [8:50 am PT]

a.Data Aggregation: NEW or OPEN

[17:50] Ralf Handl (SAP SE): i.ODATA-1207 Clarify need for @odata.id in nested response structures

[17:52] Ralf Handl (SAP SE): Task was to check effects on client libraries

[17:52] Ralf Handl (SAP SE): Gerald talked to developers of three client libraries

[17:52] Ralf Handl (SAP SE): Two fall back to treating entities as transient if they contain neither @id nor all key properties

[17:53] Ralf Handl (SAP SE): The third library relies on presence of either @id or key properties

[17:55] Ralf Handl (SAP SE): Mike: .NET client library doesn't care, server library can produce responses with neither full key nor @id

[17:56] Ralf Handl (SAP SE): Gerald to check wrt Olingo _javascript_ client

[17:57] Ralf Handl (SAP SE): ... and with Evan Ireland

[17:57] Ralf Handl (SAP SE): Follow up next week

[17:58] Ralf Handl (SAP SE): ii.ODATA-1206 Explicitly note support for collection-valued navigation/complex properties in property paths in aggregate/groupby

[17:58] Ralf Handl (SAP SE): ii.ODATA-1206 Explicitly note support for collection-valued navigation/complex properties in property paths in aggregate/groupby

[17:58] Ralf Handl (SAP SE): https://issues.oasis-open.org/browse/ODATA-1206

[17:59] Ralf Handl (SAP SE): It is intended to support aggregation of property values reached via paths that may involve collection-valued navigation properties (see example 53). Likewise, it is intended to support grouping by properties reached via paths that may involve collection-valued navigation properties (see example 54).

So far, these possibilities are mentioned only by examples, but should be described explicitly in the prose text.

[18:01] Ralf Handl (SAP SE): ODATA-1206 is OPEN

[18:02] Ralf Handl (SAP SE): Add to section 3.1 Transformation aggregate (insertions surrounded by *):

An aggregate _expression_ may be

an _expression_ valid in a $filter system query option on the input set that results in a simple value, e.g. the path to an aggregatable property, with a specified aggregation method,

* an aggregatable property, with a specified aggregation method, that can be reached via a path consisting of a sequence of navigation properties, complex properties and complex collection properties. *

[...]

Update of section 3.10.1 Simple Grouping (insertions surrounded by *):

In its simplest form the first parameter of groupby specifies the grouping properties, a comma-separated list of one or more single-valued property paths (paths ending in a single-valued primitive, complex, or navigation property) that is enclosed in parentheses. * A path may consist of a sequence of navigation properties, complex properties and complex collection properties.*

[18:03] Michael Pizzo: I move we approve ODATA-1206 as proposed.

[18:04] Gerald Krause (SAP): I second

[18:05] Ralf Handl (SAP SE): ODATA-1206 is resolved as proposed

[18:05] Ralf Handl (SAP SE): iii.ODATA-1205 Examples 53, 54, and 59 are not compliant with Data Aggregation ABNF

[18:05] Ralf Handl (SAP SE): https://issues.oasis-open.org/browse/ODATA-1205

[18:06] Ralf Handl (SAP SE): Extend ABNF rule (insertion surrounded with *):

aggregateExpr   = customAggregate [ customFrom asAlias ]

                / commonExpr aggregateWith [ aggregateFrom ] asAlias

*                / pathPrefix primitiveProperty aggregateWith [ aggregateFrom ] asAlias *

                / pathPrefix '$count' asAlias

                / pathPrefix customAggregate

                / pathPrefix pathSegment OPEN aggregateExpr CLOSE

[18:09] Ralf Handl (SAP SE): Use "aggregatablePrimitiveProperty" in aggregation ABNF to mentally exclude streams and Geo types

[18:14] Ralf Handl (SAP SE): ODATA-1205 is OPEN

[18:14] Gerald Krause (SAP): I move to resolve ODATA-1205 as proposed.

[18:14] Michael Pizzo: I second

[18:15] Ralf Handl (SAP SE): ODATA-1205 is RESOLVED as proposed

[18:18] Ralf Handl (SAP SE): The two remaining aggregation issues are "little elephants" and are best discussed during the F2F

[18:18] Ralf Handl (SAP SE): b.Vocabularies: Annotation Examples and Example Values for types, parameters, request/response bodies

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

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

[18:19] Ralf Handl (SAP SE): Skip

[18:20] Ralf Handl (SAP SE): Discuss everything around ODATA-884 during the F2F

[18:21] Ralf Handl (SAP SE): c.V4.01: NEW or OPEN

i.ODATA-1213 Address use of 201 Created for Create Link Requests

[18:21] Ralf Handl (SAP SE): https://issues.oasis-open.org/browse/ODATA-1213

[18:23] Ralf Handl (SAP SE): ODATA-1213 is OPEN

[18:24] Matt Borges (SAP): I move to resolve ODATA-1213 as proposed.

[18:24] Michael Pizzo: I second

[18:24] Ralf Handl (SAP SE): ODATA-1213 is RESOLVED as proposed

[18:25] Ralf Handl (SAP SE): https://issues.oasis-open.org/browse/ODATA-1214

[18:26] Ralf Handl (SAP SE): Annotate constructor actions

[18:26] Ralf Handl (SAP SE): ODATA-1214 is OPEN

[18:29] Ralf Handl (SAP SE): Defer and discuss as part of ODATA-884

[18:30] Ralf Handl (SAP SE): ii.ODATA-1212 Validation term for allowed terms in Annotation Paths

[18:30] Ralf Handl (SAP SE): https://issues.oasis-open.org/browse/ODATA-1212

[18:30] Ralf Handl (SAP SE): Annotation paths allow referencing annotations.

Often the referenced annotation has to have one of certain "allowed" terms that can be interpreted in that context.

Currently these "allowed terms" cannot be expressed in the term or property definition.

[18:31] Ralf Handl (SAP SE): Mention term Validation.AllowedTerms in CSDL sections 14.2.1.3 Annotation Path.

Add to Validation vocabulary:

<Term Name="AllowedTerms" Type="Collection(Core.QualifiedTermName)" AppliesTo="Term Property">

  <Annotation Term="Core.Description"

          String="Annotation path expressions assigned to the annotated term or property MUST resolve to annotations with one of the listed terms" />

  <Annotation Term="Core.RequiresType" String="Edm.AnnotationPath" />

</Term>

Add to Core vocabulary:

<TypeDefinition Name="QualifiedTermName" UnderlyingType="Edm.String">

  <Annotation Term="Core.Description" String="The qualified name of a term in scope." />

</TypeDefinition>

[18:32] Ralf Handl (SAP SE): ODATA-1212 is OPEN

[18:45] Michael Pizzo: Concern: for forward compatibility, in things like "applies to" we are clear that it's a non-breaking change to extend the list of things enumerated in the expected collection.

[18:46] Mark Biamonte (Progress): I need to leave to had to another meeting I have at 1:00

[18:46] Michael Pizzo: WOrding from AppliesTo:

he value of AppliesTo is a whitespace-separated list of symbolic values from the table above that identify model elements the term is intended to be applied to.

[18:50] Michael Pizzo: "Annotation path expressions assigned to the annotated term or property are intended to resolve to annotations with one of the listed terms. For forward compatibility, clients should be prepared for the annotation to be applied to other terms. "

[18:51] Michael Pizzo: "Annotation path expressions assigned to the annotated term or property are intended to resolve to annotations with one of the listed terms. For forward compatibility, clients should be prepared for the annotation to reference terms besides those listed."

[18:52] Michael Pizzo: Updated proposal:

<Term Name="AllowedTerms" Type="Collection(Core.QualifiedTermName)" AppliesTo="Term Property">

  <Annotation Term="Core.Description"

          String="Annotation path expressions assigned to the annotated term or property are intended to resolve to annotations with one of the listed terms. For forward compatibility, clients should be prepared for the annotation to reference terms besides those listed." />

  <Annotation Term="Core.RequiresType" String="Edm.AnnotationPath" />

</Term>

[18:53] Ralf Handl (SAP SE): I move to resolve ODATA-1212 with the amended proposal

[18:53] Michael Pizzo: I second

[18:53] Ralf Handl (SAP SE): ODATA-1212 is RESOLVED as proposed

[18:54] Ralf Handl (SAP SE): iii.ODATA-1211 ODATA-681 4.2 and 5.1: Explicitly state that an alias MUST NOT be identical to any other alias or namespace in the same document.

[18:54] Ralf Handl (SAP SE): ODATA-1211 is OPEN

[18:55] Michael Pizzo: I move we resolved ODATA-1211 as proposed.

[18:55] Ralf Handl (SAP SE): I second

[18:55] Ralf Handl (SAP SE): ODATA-1211 is RESOLVED as proposed

[18:59] Ralf Handl (SAP SE): 7.Next meetings [9:50 am PT]

a.Thursday August 23, 2018 during 8-10 am PDT (17:00-19:00 CEST)

b.Thursday August 30, 2018 during 8-10 am PDT (17:00-19:00 CEST)

[19:00] Ralf Handl (SAP SE): Mike will be out next week

[19:01] Ralf Handl (SAP SE): 8.AOB and wrap up [9:55 am PT]

[19:01] Ralf Handl (SAP SE): Meeting is adjourned

From: odata@lists.oasis-open.org <odata@lists.oasis-open.org> On Behalf Of Handl, Ralf
Sent: Mittwoch, 15. August 2018 10:02
To: odata@lists.oasis-open.org
Subject: [CAUTION] [odata] Agenda for OData TC meeting on 2018-08-16

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

2. Approve agenda [8:05 am PT]

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

Minutes from August 09, 2018 TC meeting: https://www.oasis-open.org/committees/download.php/63694/odata-meeting-224_on-20180809-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]

Done – to be closed

i. #0038 Prepare proposal for REST Profile / OData Essentials – Mike Pizzo – 2018-08-08

Upcoming

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

Pending

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

5. Face-to-Face Meeting [8:20 am PT]

Location

i. Redmond – Mike to confirm

Schedule - proposed

i. Tuesday September 25 to Wednesday September 26, 2018: Pre-Meeting – does not count towards voter eligibility

ii. Thursday September 27 to Friday September 28, 2018: TC Meeting – counts towards voter eligibility!

Agenda – proposed

i. Resolve V4.01 issues

ii. Next steps for V4.01

iii. Data Aggregation

iv. OData-OpenAPI Mapping

v. REST-EZ

vi. Vocabularies

6. Issues [8:50 am PT]

Data Aggregation: NEW or OPEN

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

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

iii. ODATA-1205 Examples 53, 54, and 59 are not compliant with Data Aggregation ABNF

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

v. ODATA-945 Correct examples 53 and 54

Vocabularies: Annotation Examples and Example Values for types, parameters, request/response bodies

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

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

V4.01: NEW or OPEN

i. ODATA-1213 Address use of 201 Created for Create Link Requests

ii. ODATA-1212 Validation term for allowed terms in Annotation Paths

iii. ODATA-1211 ODATA-681 4.2 and 5.1: Explicitly state that an alias MUST NOT be identical to any other alias or namespace in the same document.

iv. ODATA-1210 CSDL ReturnType element needs to specify rules for Nullable and Collection with entity types

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

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

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

viii. ODATA-1197 Chapter 21 Error Response: replace misleading "code" values with FOO or BAR

ix. ODATA-1196 Clarify update of media streams

x. ODATA-1195 11.2.6.6: value of $search is search _expression_, not boolean _expression_

xi. ODATA-1191 Make sure that all model elements are annotatable

xii. ODATA-1190 Add matchesPattern as a $filter function

xiii. ODATA-1189 Conformance: Nullable for collections

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

xv. ODATA-1187 No way to bind nav prop on recursively nested (contained or complex) type

xvi. ODATA-1183 Allow Singletons to be null

xvii. ODATA-1180 Cast between enumeration types and integer types

xviii. ODATA-1177 Core: add term SchemaLocation

xix. ODATA-1171 Consider using matrix parameters for filter segments

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

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

xxii. ODATA-1148 PATCH with nested nav props should not remove omitted resources

xxiii. ODATA-1143 Extend the Property metatype to allow a type that is an EntityType.

xxiv. ODATA-1141 Upsert: clarify upsert along nullable single-valued navigation path

xxv. ODATA-1135 Document use of JSON $schema

xxvi. ODATA-1088 Clarify effect of applying an Annotation to an element

Vocabularies: NEW or OPEN with concrete proposal

i. ODATA-1212 Validation term for allowed terms in Annotation Paths

ii. ODATA-1209 Term for original OData version of (auto-)converted $metadata

iii. ODATA-1204 Vocabularies Document references OData Version 4.01. Part 3: Common Schema Definition Language (CSDL)

iv. ODATA-1176 Capabilities: add new term SelectRestrictions

v. ODATA-1167 Add way to specify which batch formats (if any) are supported by a service

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

Vocabularies: NEW or OPEN that need more discussion

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

ii. ODATA-1199 ODATA-884 / Add property SystemQueryOptions to call out supported system query options per request method

iii. ODATA-1193 Automated vocabulary checks indicate some potential issues

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

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

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

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

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

ix. ODATA-884 Add term ErrorCodes to describe possible codes in error messages (public comment c201510e00019)

7. Next meetings [9:50 am PT]

Thursday August 23, 2018 during 8-10 am PDT (17:00-19:00 CEST)
Thursday August 30, 2018 during 8-10 am PDT (17:00-19:00 CEST)

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