RE: Agenda for OData TC Face-to-Face meeting part 2 on 2018-09-28

[8:59] Room information was updated by: Ralf Handl (SAP SE)

Here [1] is a draft agenda for the OData TC (Technical Committee) Face-to-Face meeting Part 2 scheduled on Friday September 28, 2018 during 9 am to 3 pm PDT (18:00 to 00:00+1 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.Friday Morning [9:00 am PT]

a.Approve agenda [9:05 am PT]

b.V4.01: NEW or OPEN  [09:10 am PT]

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

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

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

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

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

vi.ODATA-1135 Document use of JSON $schema

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

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

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

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

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

2.Friday Afternoon [1:30 pm PT]

a.Vocabularies: V4.01-related issues

i.ODATA-1227 Improve description of filter _expression_ restrictions

ii.ODATA-1229 Introduce LocalTime annotation to apply to string datatype

iii.ODATA-1226 Ambiguity with Capabilities.ChangeTracking annotation

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

v.ODATA-1176 Capabilities: add new term SelectSupported

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

b.OpenAPI-related vocabulary issues

i.ODATA-1214 Annotate constructor actions

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

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

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

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

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

c.Data Aggregation: NEW or OPEN

i.ODATA-945 Correct examples 53 and 54

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

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

d.Miscellaneous

3.Next meetings [2:50 pm PT]

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

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

4.AOB and wrap up [2:55 pm 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

[9:10] Ralf Handl (SAP SE): 1.Friday Morning [9:00 am PT]

a.Approve agenda [9:05 am PT]

[9:14] Ralf Handl (SAP SE): b.V4.01: NEW or OPEN  [09:10 am PT]

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

[9:15] Ralf Handl (SAP SE): ODATA-1198 is OPEN

[9:15] Ralf Handl (SAP SE): We had a lengthy discussion in the pre-meeting, see proposal sketch in https://issues.oasis-open.org/browse/ODATA-1198

[9:16] Ralf Handl (SAP SE): Mike will work out a proposal

[9:16] Ralf Handl (SAP SE): Defer issue until then

[9:16] Ralf Handl (SAP SE): ii.ODATA-1168 Clarify the use of ETags for Avoiding Update Conflicts

[9:16] Ralf Handl (SAP SE): Proposal exists, to be processed together with ODATA-1198

[9:19] Ralf Handl (SAP SE): Hubert will open issue to allow @etag control information for collections

[9:20] Ralf Handl (SAP SE): Ralf noticed inconsistency in JSON Format 4.5.10 Control Information: etag (odata.etag). Last paragraph states that @etag is ignored in request bodies, this contradicts "patch to entity set".

[9:20] Ralf Handl (SAP SE): iii.ODATA-1148 PATCH with nested nav props should not remove omitted resources

[9:20] Ralf Handl (SAP SE): https://issues.oasis-open.org/browse/ODATA-1148

[9:26] Ralf Handl (SAP SE): I move to close ODATA-1148 without action.

[9:26] Ted Jones (Red Hat): I second

[9:27] Ralf Handl (SAP SE): ODATA-1148 is CLOSED without action

[9:27] Ralf Handl (SAP SE): iv.ODATA-1141 Upsert: clarify upsert along nullable single-valued navigation path

[9:28] Ralf Handl (SAP SE): https://issues.oasis-open.org/browse/ODATA-1141

[9:34] Ralf Handl (SAP SE): Mike: for server-generated keys the differentiation between "specify key" and "do not specify key" is odd

[9:35] Ralf Handl (SAP SE): George: should we differentiate between PUT and PATCH?

[9:37] Ralf Handl (SAP SE): PUT seems straight-forward because all desired property values in the after-image are specified, so we can assign meaning to "not specify key"

[9:37] Michael Pizzo1: concern is same for client-generated keys.  having different create and replace versus update behavior depending on whether the key/id values were provided seems weird from REST.

[9:38] Ralf Handl (SAP SE): PATCH is trickier as here only those properties are specified whose values are desired to change, and changing the (related) key if the key is NOT specified is odd.

[9:52] Ralf Handl (SAP SE): Deep Update also does not specify behavior for single-valued navigation properties, needs to be changed according to how we resolve this issue

[9:56] Ralf Handl (SAP SE): Deep Update: if a nested entity exists but is not yet related, it is first related and then updated.

[9:56] Ralf Handl (SAP SE): This has to go into 11.4.3.1 Update Related Entities When Updating an Entity, paragraph 5

[9:58] Ralf Handl (SAP SE): Mike: if a single-valued relationship changes, a delta response would contain the newly related entity, including its key.

[9:59] Ralf Handl (SAP SE): Mike: it would be nice if sending such a message to a server would result in changing the relationship

[10:06] Ralf Handl (SAP SE): Mike: for PATCH it seems ok to have this behavior

[10:23] Ralf Handl (SAP SE): Mike: for PUT is a little weird

[10:23] Ralf Handl (SAP SE): George: someone needs to write this up before we decide

[10:24] Ralf Handl (SAP SE): Mike volunteers to write it up

[10:25] Ralf Handl (SAP SE): Ralf: would be fine if we only define this behavior for PATCH

[10:26] Ralf Handl (SAP SE): George: reserve PUT for later until we have a better feel for it

[10:37] Ralf Handl (SAP SE): Single-valued nullable containment navigation property

[10:37] Ralf Handl (SAP SE): nothing exists: PUT creates and relates

[10:37] Ralf Handl (SAP SE): something exists: PUT changes

[10:37] Ralf Handl (SAP SE): PUT also changes the key in this case because the key has no meaning here

[10:38] Ralf Handl (SAP SE): Single-valued nullable NON-containment

[10:38] Ralf Handl (SAP SE): nothing exists: PUT creates and relates

[10:39] Ralf Handl (SAP SE): something exists: ???

[10:45] Ralf Handl (SAP SE): Text for "Update an entity" states that key property values are ignored when updating an existing entity.

[10:45] Ralf Handl (SAP SE): This implies that you cannot relate a different entity via PATCH or PUT to a single-valued navigation property.

[10:49] Ralf Handl (SAP SE): Short break until 11:00 am PDT

[11:19] Ralf Handl (SAP SE): Nullable singleton: PUT creates and relates, singleton is conceptionally a containment-navigation property because that's the only address to reach the singleton.

[11:21] Ralf Handl (SAP SE): Single-valued nullable NON-containment

[11:21] Ralf Handl (SAP SE): something exists: update and ignore key properties, thus do not relate something different

[11:29] Hubert Heijkers (IBM)3: I move to resolve ODATA-1141 as per the new, heavily debated, amended proposal;-!

[11:29] George Ericson (Dell): Second

[11:32] Ralf Handl (SAP SE): Just for the record: for non-containment a new entity can be created and related in one request via DEEP PATCH specifying just the single-valued navigation property with the to-be-created new entity

[11:33] Ralf Handl (SAP SE): https://issues.oasis-open.org/browse/ODATA-1234

[11:34] Ralf Handl (SAP SE): Allow relative URLs in headers

[11:36] Ralf Handl (SAP SE): ODATA-1234 is OPEN

[11:36] Hubert Heijkers (IBM)3: I move to resolve ODATA-1234 as proposed.

[11:36] Matt Borges (SAP): I second

[11:36] Ralf Handl (SAP SE): ODATA-1234 is RESOLVED as proposed

[11:36] Ralf Handl (SAP SE): v.ODATA-1114 If-Then-Else in $batch requests

[11:36] Ralf Handl (SAP SE): https://issues.oasis-open.org/browse/ODATA-1114

[11:37] Ralf Handl (SAP SE): Proposal:

Add an optional "if" member to request objects that allows specifying a condition for executing the request depending on the outcome of preceding requests.

The value of "if" is a string containing a boolCommonExpr as in $filter that can reference preceding requests listed in "dependsOn". It replaces the default condition of "all preceding requests listed in dependsOn have succeeded".

Filter _expression_ syntax is extended, additional expressions are

$<content-id>/$succeeded to check if the referenced request succeeded

$<content-id>/$failed to check if the referenced request failed

$<content-id> to reference the response body

$<content-id>/<path> to reference a part of the response body

Define new property ConditionalRequestsSupported for Capabilities.BatchSupportType to advertise this new capability.

If a service does not support "if" the conditional request MUST fail. If the conditional request is part of an atomicity group, that group fails and is rolled back.

[11:40] Ralf Handl (SAP SE): ODATA-1114 is OPEN

[11:44] Hubert Heijkers (IBM)3: I move to resolve ODATA-1114 as per the amended proposal

[11:44] Mark Biamonte (Progress): I second

[11:44] Ralf Handl (SAP SE): ODATA-1114 is RESOLVED as proposed

[11:45] Ralf Handl (SAP SE): vi.ODATA-1135 Document use of JSON $schema

[11:45] Ralf Handl (SAP SE): https://issues.oasis-open.org/browse/ODATA-1135

[11:56] Ralf Handl (SAP SE): Deferred

[11:59] Ralf Handl (SAP SE): vii.ODATA-1088 Clarify effect of applying an Annotation to an element

[12:00] Ralf Handl (SAP SE): https://issues.oasis-open.org/browse/ODATA-1088

[12:29] Ralf Handl (SAP SE): ODATA-1088 is OPEN

[12:30] George Ericson (Dell): Move to approve ODATA-1088 as revised.

[12:30] Michael Pizzo: I second

[12:30] Ralf Handl (SAP SE): ODATA-1088 is RESOLVED as proposed

[12:32] Ralf Handl (SAP SE): Short break

[12:38] Ralf Handl (SAP SE): viii.ODATA-1064 Add ability to annotate collections to return only count and NextLink

[12:38] Ralf Handl (SAP SE): https://issues.oasis-open.org/browse/ODATA-1064

[12:42] Ralf Handl (SAP SE): Mike and George to discuss after the official meeting whether this solves the underlying problem

[12:42] Ralf Handl (SAP SE): ix.ODATA-1143 Extend the Property metatype to allow a type that is an EntityType.

[12:42] Ralf Handl (SAP SE): https://issues.oasis-open.org/browse/ODATA-1143

[12:51] Ralf Handl (SAP SE): Ralf: what about navigation properties in such a "snapshot": can I $expand them?

[12:53] Ralf Handl (SAP SE): Mike: an entity as a value of a structured property actually is a complex type instance

[12:55] Ralf Handl (SAP SE): This means it's "key" does not have any meaning

[12:55] Ralf Handl (SAP SE): So you can e.g. have duplicates within a collection

[12:59] Ralf Handl (SAP SE): What about containment navigation properties? Are contained entities automatically part of the snapshot and behave like structural properties?

[12:59] Ralf Handl (SAP SE): Mike: no. They are still containment navigation properties, just as on a complex type

[13:01] Ralf Handl (SAP SE): George: what about entity types in parameters?

[13:02] Ralf Handl (SAP SE): Mark: how about inheritance? Derive entity type from complex type and add a key, or derive complex type from entity type and thus remove the key

[13:05] Ralf Handl (SAP SE): Hubert: why not just use a containment navigation property, e.g. from a log entry to the thing to be logged. The contained entity is different by definition from the "original" entity.

[13:09] Ralf Handl (SAP SE): ODATA-1143 is OPEN

[13:10] George Ericson (Dell): Move to close OData-1143 without action.

[13:10] Hubert Heijkers (IBM)3: I second

[13:10] Ralf Handl (SAP SE): ODATA-1143 is CLOSED without action

[13:10] Ralf Handl (SAP SE): i.ODATA-1187 No way to bind nav prop on recursively nested (contained or complex) type

[13:11] Ralf Handl (SAP SE): xi.ODATA-1191 Make sure that all model elements are annotatable

[13:45] Ralf Handl (SAP SE): Lunch break until 14:45

[14:28] Ralf Handl (SAP SE): Lunch break is over

[14:30] Ralf Handl (SAP SE): ODATA-1187

[14:30] Ralf Handl (SAP SE): Proposal:

Clients can typically assume that binding a recursive navprop path binds recursively. If we need to later, we can add an entityset/singleton annotation to say it doesn't.

[14:30] Michael Pizzo: I move to resolve ODATA-1187 as proposed

[14:31] Hubert Heijkers (IBM)3: I second

[14:31] Ralf Handl (SAP SE): ODATA-1187 is RESOLVED as proposed

[14:31] Ralf Handl (SAP SE): xi.ODATA-1191 Make sure that all model elements are annotatable

[14:31] Ralf Handl (SAP SE): ODATA-1191 is OPEN

[15:04] Hubert Heijkers (IBM): I move to close ODATA-1191 without further action

[15:04] Ramesh Reddy(Red Hat): I second

[15:04] Ralf Handl (SAP SE): ODATA-1191 is CLOSED without action

[15:20] Ralf Handl (SAP SE): ODATA-1227 is OPEN

[15:20] Hubert Heijkers (IBM): I move to resolve ODATA-1227 as proposed

[15:20] Michael Pizzo: I second

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

[15:21] Ralf Handl (SAP SE): ii.ODATA-1229 Introduce LocalTime annotation to apply to string datatype

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

[15:58] Ralf Handl (SAP SE): ODATA-1229 is OPEN

[15:58] Hubert Heijkers (IBM): I move to resolve ODATA-1229 as proposed

[15:58] Michael Pizzo3: I second

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

[16:00] Ralf Handl (SAP SE): Short break until 16:10

[16:13] Ralf Handl (SAP SE): iv.ODATA-1216 Terms for POST/PATCH/PUT with system query options to shape response

[16:26] Ralf Handl (SAP SE): Mike: for UpdateSupport we will also need FilterSupported and SearchSupported

[16:27] Ralf Handl (SAP SE): And SortSupported and ComputeSupported

[16:28] Ralf Handl (SAP SE): And NavigationSupport with similar structure

[16:29] Ralf Handl (SAP SE): Mike: could use same complex type for UpdateSupport and ActionSupport

[17:14] Ralf Handl (SAP SE): Don't introduce new top-level terms, instead extend the existing XxxRestrictions. This then automatically extends the NavigationRestrictions.

[17:17] Ralf Handl (SAP SE): Ralf to rework the proposal as stated above

[17:18] Ralf Handl (SAP SE): v.ODATA-1176 Capabilities: add new term SelectSupported

[17:19] Ralf Handl (SAP SE): Instead of boolean terms we should add structured terms that also reflect the added V4.01 capabilities with nested query options

[17:19] Ralf Handl (SAP SE): Ralf to rework the proposal accordingly

[17:19] Ralf Handl (SAP SE): vi.ODATA-1005 Make sure we have capabilities for all new 4.01 functionality

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

[17:54] Ralf Handl (SAP SE): ODATA-1230 has been reopened

[17:55] Michael Pizzo3: I move we remove $search from ODATA-1230.

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

[17:55] Ralf Handl (SAP SE): ODATA-1230 is RESOLVED with the amended proposal

[17:55] Michael Pizzo3: (it is dangerous to invoke a function or take other action on fuzzy values)

[17:56] Ralf Handl (SAP SE): 3.Next meetings [2:50 pm PT]

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

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

[17:57] Ralf Handl (SAP SE): Proposal: skip next week

[17:57] Ralf Handl (SAP SE): George and Mike to work on vocabulary issues offline

[17:58] Ralf Handl (SAP SE): Don't skip the meeting, just make it voluntary and not count towards voting eligibility

[17:58] Ralf Handl (SAP SE): Meaning no motions

[18:00] Ralf Handl (SAP SE): 1.AOB and wrap up [2:55 pm PT]

[18:00] Ralf Handl (SAP SE): No other business, the meeting is adjourned

[18:01] Ralf Handl (SAP SE): Thanks!!!

From: odata@lists.oasis-open.org <odata@lists.oasis-open.org> On Behalf Of Handl, Ralf
Sent: Freitag, 28. September 2018 07:56
To: odata@lists.oasis-open.org
Subject: [CAUTION] [odata] RE: Agenda for OData TC Face-to-Face meeting part 2 on 2018-09-28

Moved Data Aggregation issues to last position

From: odata@lists.oasis-open.org <odata@lists.oasis-open.org> On Behalf Of Handl, Ralf
Sent: Donnerstag, 27. September 2018 15:58
To: odata@lists.oasis-open.org
Subject: [CAUTION] [odata] Agenda for OData TC Face-to-Face meeting part 2 on 2018-09-28

Here [1] is a draft agenda for the OData TC (Technical Committee) Face-to-Face meeting Part 2 scheduled on Friday September 28, 2018 during 9 am to 3 pm PDT (18:00 to 00:00+1 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. Friday Morning [9:00 am PT]

Approve agenda [9:05 am PT]

V4.01: NEW or OPEN [09:10 am PT]

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

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

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

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

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

vi. ODATA-1135 Document use of JSON $schema

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

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

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

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

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

2. Friday Afternoon [1:30 pm PT]

Vocabularies: V4.01-related issues

i. ODATA-1227 Improve description of filter _expression_ restrictions

ii. ODATA-1229 Introduce LocalTime annotation to apply to string datatype

iii. ODATA-1226 Ambiguity with Capabilities.ChangeTracking annotation

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

v. ODATA-1176 Capabilities: add new term SelectSupported

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

OpenAPI-related vocabulary issues

i. ODATA-1214 Annotate constructor actions

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

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

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

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

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

Data Aggregation: NEW or OPEN

i. ODATA-945 Correct examples 53 and 54

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

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

Miscellaneous

3. Next meetings [2:50 pm PT]

Thursday October 04, 2018 during 8-10 am PDT (17:00-19:00 CEST)
Thursday October 11, 2018 during 8-10 am PDT (17:00-19:00 CEST)

4. AOB and wrap up [2:55 pm 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