RE: Agenda for OData TC meeting on 2018-07-26

[17:01] anonymous morphed into Mark Biamonte (Progress)

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

3.a. Link to minutes updated

From: Handl, Ralf

Sent: Donnerstag, 26. Juli 2018 10:54

To: Handl, Ralf <ralf.handl@sap.com>; odata@lists.oasis-open.org

Subject: RE: Agenda for OData TC meeting on 2018-07-26

3.a. Link to minutes added

From: odata@lists.oasis-open.org <odata@lists.oasis-open.org> On Behalf Of Handl, Ralf

Sent: Mittwoch, 25. Juli 2018 17:12

To: odata@lists.oasis-open.org

Subject: [CAUTION] [odata] RE: Agenda for OData TC meeting on 2018-07-26

New topic

4. GitHub Pages sites for three of our GitHub repositories:

https://oasis-tcs.github.io/odata-json-schema/

https://oasis-tcs.github.io/odata-vocabularies/

https://oasis-tcs.github.io/odata-openapi/

These Pages sites contain the same content as the GitHub repositories, just without the GitHub decoration. Currently one has to guess or know their URLs. We want to make them discoverable by linking to them from the repository start page, similar to https://github.com/oasis-open/csaf-documentation

From: odata@lists.oasis-open.org <odata@lists.oasis-open.org> On Behalf Of Handl, Ralf

Sent: Mittwoch, 25. Juli 2018 11:08

To: odata@lists.oasis-open.org

Subject: [CAUTION] [odata] Agenda for OData TC meeting on 2018-07-26

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

2.Approve agenda [8:05 am PT]

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

a.Minutes from July 19, 2018 TC meeting: https://www.oasis-open.org/committees/download.php/63488/odata-meeting-221_on-20180719-minutes.html

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

a.Due

i.#0036 Register the OData- headers and preferences with IANA  Mark Biamonte  2017-11-30

1.IANA Header and Preference registration document questions

b.Upcoming

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

c.Pending

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

5.Issues [8:20 am PT]

a.Data Aggregation: NEW or OPEN

i.ODATA-1201 Improve the syntax of aggregation exceptions with "from"

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

iii.ODATA-945 Correct examples 53 and 54

b.Vocabularies: Bug fixes

i.ODATA-1192 Capabilities vocabulary: invalid DefaultValue for KeyAsSegmentSupported

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

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

d.V4.01: NEW or OPEN

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

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

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

iv.ODATA-1196 Clarify update of media streams

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

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

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

viii.ODATA-1189 Conformance: Nullable for collections

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

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

xi.ODATA-1183 Allow Singletons to be null

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

xiii.ODATA-1177 Core: add term SchemaLocation

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

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

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

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

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

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

xx.ODATA-1135 Document use of JSON $schema

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

e.Vocabularies: NEW or OPEN with concrete proposal

i.ODATA-1176 Capabilities: add new term SelectRestrictions

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

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

f.Vocabularies: NEW or OPEN that need more discussion

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

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-1005 Make sure we have capabilities for all new 4.01 functionality

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

6.Next meetings [9:50 am PT]

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

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

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://sap.emea.pgiconnect.com/OData-TC

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

[3] Timeline

https://www.oasis-open.org/committees/download.php/62637/TC%20Timeline-2018-03-02.docx

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

[17:05] Ralf Handl (SAP SE): Quorum achieved: yes

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

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

a.Minutes from July 19, 2018 TC meeting: https://www.oasis-open.org/committees/download.php/63488/odata-meeting-221_on-20180719-minutes.html

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

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

a.Due

i.#0036 Register the OData- headers and preferences with IANA  Mark Biamonte  2017-11-30

1.IANA Header and Preference registration document questions

[17:09] Ralf Handl (SAP SE): https://www.oasis-open.org/apps/org/workgroup/odata/email/archives/201807/msg00017.html

[17:10] Ralf Handl (SAP SE): 1) Gating items ahead of registration requests to the lists?  I'm unsure whether there are any other gating items, but I see a lot of activity in the OData TC

- Part3  at CS level -- needed?

Part 3 has been replaced by two documents in OData 4.01

OData Common Schema Definition Language (CSDL) XML Representation Version 4.0.1

OData Common Schema Definition Language (CSDL) JSON Representation Version 4.01

Both of these documents are at CS01

Note:  The Part1: Protocol document references OData Vocabularies Version 4.0 and that vocabularies document references OData Version 4.01. Part 3: Common Schema Definition Language (CSDL). Latest version: http://docs.oasis-open.org/odata/odata/v4.01/odata-v4.01-part3-csdl.html which is not valid for OData 4.01.  I think this may be why Robin is asking about Part 3.

[17:11] anonymous morphed into George Ericson (Dell)

[17:13] Ralf Handl (SAP SE): Mark to open an issue to fix Vocabularies doc reference to non-existing OData V4.01 part 3

[17:16] Ralf Handl (SAP SE): 3) HTML section URLs: headlines in the new documents are links to the stable anchors, using the pattern #sec_...

[17:19] Ralf Handl (SAP SE): 4) Can we update the IANA registration later to point to the OASIS Specification once we've progressed it to OS? Mark to follow up

[17:22] Ralf Handl (SAP SE): 5) Only register the prefered variant of preferences without odata. prefix

[17:22] Ralf Handl (SAP SE): Mark prefers that

[17:22] Ralf Handl (SAP SE): Mike will go with that

[17:22] Ralf Handl (SAP SE): Ralf prefers that

[17:23] Ralf Handl (SAP SE): No objections, only register the non-prefixed variants

[17:24] Ralf Handl (SAP SE): b.Upcoming

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

[17:24] Ralf Handl (SAP SE): c.Pending

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

[17:25] Ralf Handl (SAP SE): Moved to August 08, 2018

[17:25] Ralf Handl (SAP SE): 4. GitHub Pages sites for three of our GitHub repositories:

https://oasis-tcs.github.io/odata-json-schema/

https://oasis-tcs.github.io/odata-vocabularies/

https://oasis-tcs.github.io/odata-openapi/

These Pages sites contain the same content as the GitHub repositories, just without the GitHub decoration. Currently one has to guess or know their URLs. We want to make them discoverable by linking to them from the repository start page, similar to https://github.com/oasis-open/csaf-documentation

[17:27] Ralf Handl (SAP SE): https://oasis-open.github.io/csaf-documentation/

[17:35] Ralf Handl (SAP SE): I move to link from the Github repo start pages to the corresponding github.io Pages Sites

[17:35] Michael Pizzo: I second

[17:36] Ralf Handl (SAP SE): Motion passes

[17:37] Ralf Handl (SAP SE): Volunteers for beautifying the Pages Sites, e.g. with an OData logo

[17:37] Ralf Handl (SAP SE): Ted Jones will have a go on it!

[17:38] Ralf Handl (SAP SE): 5.Issues [8:20 am PT]

a.Data Aggregation: NEW or OPEN

[17:39] Ralf Handl (SAP SE): i.ODATA-1201 Improve the syntax of aggregation exceptions with "from"

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

[17:41] Ralf Handl (SAP SE): https://github.com/oasis-tcs/odata-abnf/pull/1

[17:42] Gerald Krause (SAP): I move to resolve ODATA-1201 as proposed

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

[17:43] Ralf Handl (SAP SE): ODATA-1201 is OPEN

[17:43] Ralf Handl (SAP SE): ODATA-1201 is RESOLVED as proposed

[17:53] Ralf Handl (SAP SE): ii.ODATA-947 Transformation for computing ratios with aggregated values

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

[17:54] Ralf Handl (SAP SE): Hubert on 2018-06-21:

think about similar use cases

ratio() is very useful

combine this with hierarchies

revenue contribution of offices to countries to continents

ability to refer to the input set

[17:57] Ralf Handl (SAP SE): GET ~/Sales?$apply=

groupby((Customer),aggregate(Amount with sum as CustomerAmount))

/ratio(CustomerAmount to CustomerAmount with sum as RevenueContribution)

[17:58] Ralf Handl (SAP SE): GET ~/Sales?$apply=

groupby((Customer),aggregate(Amount with sum as CustomerAmount))

/compute(CustomerAmount div aggregate(CustomerAmount with sum) as RevenueContribution)

[18:04] Ralf Handl (SAP SE): GET ~/Sales?$apply=

groupby((Customer),compute(Amount div aggregate(Amount with sum) as RevenueContribution))

[18:06] Ralf Handl (SAP SE): The last one won't work

[18:06] Ralf Handl (SAP SE): GET ~/Sales?$apply=

groupby((Customer),aggregate(Amount with sum as CustomerAmount))

/compute(CustomerAmount div aggregate(CustomerAmount with sum) as RevenueContribution)

[18:10] Ralf Handl (SAP SE): GET ~/Sales?$apply=

groupby((Customer),aggregate(Amount with sum as CustomerAmount))

/keep-in-mind(aggregate(CustomerAmount with sum as Divisor)/compute(CustomerAmount div Divisor as RevenueContribution)

[18:11] Ralf Handl (SAP SE): George: how does this relate to SQL?

[18:11] Ralf Handl (SAP SE): George: how beneficial is this for clients?

[18:12] Ralf Handl (SAP SE): Second question: ratio is quite beneficial

[18:21] Ralf Handl (SAP SE): How would this translate into Common Table Expressions in SQL?

[18:22] Ralf Handl (SAP SE): Gerald to provide SQL counterparts for evaluating these expressions

[18:23] Ralf Handl (SAP SE): iii.ODATA-945 Correct examples 53 and 54

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

[18:24] Ralf Handl (SAP SE): Hubert: we have to explain more about the differences

Ralf:

Plain paths with / work like compute: pull arguments from related entities, place result "at the top"

Parentheses can be used to place the result within the related/nested structure

Ralf: Slight difference:

GET ~/Products?$apply=groupby((Name,Sales/Currency/Code),aggregate(Sales(Amount with sum as Total)))

GET ~/Products?$apply=groupby((Name,Sales/Currency/Code),aggregate(Sales/Amount with sum as Total))

Ralf: 3.1.1 Keyword as

Aggregate expressions can define an alias using the as keyword, followed by a SimpleIdentifier (see [OData-CSDL, section 17.2]).

The alias will introduce a dynamic property in the aggregated result set. The introduced dynamic property is added to the

type containing the original _expression_ or custom aggregate.

The alias MUST NOT collide with names of declared properties, custom aggregates, or other aliases in that type.

Ralf:

Sales/Amount with sum as Total

Sales(Amount with sum as Total)

George: be more explicit in the definition and not define by example

Ralf:

First example: in top context we are interested in the Amount

Second example: we are interested in the Sales, and within the Sales in the Amount

Need to revise the specification text: section 3.1.1

[18:27] Ralf Handl (SAP SE): Gerald to work on revised text for section 3.1.1

[18:27] Ralf Handl (SAP SE): b.Vocabularies: Bug fixes

i.ODATA-1192 Capabilities vocabulary: invalid DefaultValue for KeyAsSegmentSupported

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

[18:28] Ralf Handl (SAP SE): ODATA-1192 is OPEN

[18:28] Ralf Handl (SAP SE): Change default value from 'True' to 'true'.

[18:28] Michael Pizzo: I move to resolve ODATA-1192 as proposed

[18:29] Hubert Heijkers (IBM): I second

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

[18:29] Ralf Handl (SAP SE): https://github.com/oasis-tcs/odata-vocabularies/pull/15

[18:29] Ralf Handl (SAP SE): Diffs

-            "$DefaultValue": "True",

+            "$DefaultValue": true,

[18:30] Ralf Handl (SAP SE): Next diff

-      <Term Name="KeyAsSegmentSupported" Type="Core.Tag" DefaultValue="True" AppliesTo="EntityContainer">

+      <Term Name="KeyAsSegmentSupported" Type="Core.Tag" DefaultValue="true" AppliesTo="EntityContainer">

[18:30] Ralf Handl (SAP SE): I move to merge this pull request

[18:30] Hubert Heijkers (IBM): I second

[18:30] Ralf Handl (SAP SE): Motion passes

[18:31] Ralf Handl (SAP SE): I move to CLOSE ODATA-1192 as applied

[18:32] Michael Pizzo: I second

[18:32] Ralf Handl (SAP SE): ODATA-1192 is CLOSED as applied

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

[18:33] Ralf Handl (SAP SE): https://oasis-tcs.github.io/odata-vocabularies/vocabularies/Org.OData.Aggregation.V1.xml:82 Property Warning: Unspecified Nullable facet defaults to true for property 'Rollup'. It is unusual for properties with default values to be nullable. An explicit Nullable='true' facet is recommended when null property values should be permitted.

<Property Name="Rollup" DefaultValue="MultipleHierarchies" Type="Aggregation.RollupType">...

[18:35] Ralf Handl (SAP SE): https://oasis-tcs.github.io/odata-vocabularies/vocabularies/Org.OData.Aggregation.V1.xml:85 Property Warning: Unspecified Nullable facet defaults to true for property 'PropertyRestrictions'. It is unusual for boolean-typed properties to allow null values. An explicit Nullable='true' facet is recommended when null property values should be permitted.

<Property Name="PropertyRestrictions" DefaultValue="false" Type="Edm.Boolean">...

[18:36] Ralf Handl (SAP SE): https://oasis-tcs.github.io/odata-vocabularies/vocabularies/Org.OData.Authorization.V1.xml:76 Property Warning: Unspecified Nullable facet defaults to true for property 'RequiredScopes'. It is unusual to for collection-typed properties to allow null items. An explicit Nullable='true' facet is recommended when null property values should be permitted.

<Property Name="RequiredScopes" Type="Collection(Edm.String)">...

[18:37] Ralf Handl (SAP SE): ODATA-1193 is OPEN

[18:37] Ralf Handl (SAP SE): Mike: these checks are great

[18:42] Ralf Handl (SAP SE): Gerald: check Aggregation issues

[18:42] Ralf Handl (SAP SE): Mike: check Authorization issues

[18:48] Ralf Handl (SAP SE): Capabilities:

collection of filter functions --> Nullable=false

maxlevels --> nullable=false

[18:52] Ralf Handl (SAP SE): Ralf: Capabilities

[18:52] Ralf Handl (SAP SE): c.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:54] Ralf Handl (SAP SE): ODATA-1194 and ODATA-1200

[18:58] Ralf Handl (SAP SE): <Term Name="Example" Type="Core.ExampleType">

        <Annotation Term="Core.Description" String="A container for annotation examples" />

        <Annotation Term="Core.Example">

          <Record>

            <Annotation Term="Core.Description"

              String="Note that the value of Core.Example is a record/object containing the annotation examples" />

          </Record>

        </Annotation>

      </Term>

      <ComplexType Name="ExampleType">

        <Annotation Term="Core.Description" String="This type intentionally doesn't have properties, so it can only contain annotation examples" />

      </ComplexType>

[18:58] Ralf Handl (SAP SE): <Term Name="Example" Type="Core.ExampleValue" AppliesTo="EntityType ComplexType Parameter"/>

<ComplexType Name="ExampleValue" Abstract="true">

 <Property Name="Description" Type="Edm.String" Nullable="false">

 <Annotation Term="Core.Description" String="Description of the example value" />

 </Property>

 </ComplexType>

<ComplexType Name="InlineExampleValue" BaseType="ExampleValue">

 <Property Name="Value" Type="Edm.String" Nullable="false">

 <Annotation Term="Core.Description" String="Example value for the custom parameter" />

 </Property>

 </ComplexType>

<ComplexType Name="ExternalExampleValue" BaseType="ExampleValue">

 <Property Name="ExternalValue" Type="Edm.String" Nullable="false">

 <Annotation Term="Core.Description" String="Url reference to the value in its literal format" />

 </Property>

 </ComplexType>

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

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

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

[19:06] Ralf Handl (SAP SE): Mike cannot attend next week

[19:06] Ralf Handl (SAP SE): Ted also cannot attend next week

[19:07] Ralf Handl (SAP SE): Ramesh is also out next week

[19:07] Ralf Handl (SAP SE): Let's try it next week

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

[19:11] Ralf Handl (SAP SE): F2F in Redmond September 25-28

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

From: odata@lists.oasis-open.org <odata@lists.oasis-open.org> On Behalf Of Handl, Ralf
Sent: Donnerstag, 26. Juli 2018 16:30
To: odata@lists.oasis-open.org
Subject: [CAUTION] [odata] RE: Agenda for OData TC meeting on 2018-07-26

3.a. Link to minutes updated

From: Handl, Ralf
Sent: Donnerstag, 26. Juli 2018 10:54
To: Handl, Ralf <ralf.handl@sap.com>; odata@lists.oasis-open.org
Subject: RE: Agenda for OData TC meeting on 2018-07-26

3.a. Link to minutes added

From: odata@lists.oasis-open.org <odata@lists.oasis-open.org> On Behalf Of Handl, Ralf
Sent: Mittwoch, 25. Juli 2018 17:12
To: odata@lists.oasis-open.org
Subject: [CAUTION] [odata] RE: Agenda for OData TC meeting on 2018-07-26

New topic

4½. GitHub Pages sites for three of our GitHub repositories:

These Pages sites contain the same content as the GitHub repositories, just without the GitHub “decoration”. Currently one has to “guess” or know their URLs. We want to make them discoverable by linking to them from the repository start page, similar to https://github.com/oasis-open/csaf-documentation

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

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

2. Approve agenda [8:05 am PT]

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

Minutes from July 19, 2018 TC meeting: https://www.oasis-open.org/committees/download.php/63488/odata-meeting-221_on-20180719-minutes.html

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

i. #0036 Register the OData- headers and preferences with IANA – Mark Biamonte – 2017-11-30

IANA Header and Preference registration document questions

Upcoming

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

Pending

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

5. Issues [8:20 am PT]

Data Aggregation: NEW or OPEN

i. ODATA-1201 Improve the syntax of aggregation exceptions with "from"

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

iii. ODATA-945 Correct examples 53 and 54

Vocabularies: Bug fixes

i. ODATA-1192 Capabilities vocabulary: invalid DefaultValue for KeyAsSegmentSupported

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

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-1202 Deep update with nested delta items should allow Core.ContentID

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

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

iv. ODATA-1196 Clarify update of media streams

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

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

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

viii. ODATA-1189 Conformance: Nullable for collections

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

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

xi. ODATA-1183 Allow Singletons to be null

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

xiii. ODATA-1177 Core: add term SchemaLocation

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

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

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

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

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

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

xx. ODATA-1135 Document use of JSON $schema

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

Vocabularies: NEW or OPEN with concrete proposal

i. ODATA-1176 Capabilities: add new term SelectRestrictions

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

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

Vocabularies: NEW or OPEN that need more discussion

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

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-1005 Make sure we have capabilities for all new 4.01 functionality

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

6. Next meetings [9:50 am PT]

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

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://sap.emea.pgiconnect.com/OData-TC
Conference call details: https://www.oasis-open.org/apps/org/workgroup/odata/download.php/56760/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