RE: Agenda for OData TC meeting on 2018-06-14

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

[17:03] Ralf Handl (SAP SE): Sorry, am late, will dial in now

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

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

[17:07] Ralf Handl (SAP SE): George: iv.ODATA-1183 Allow Singletons to be null

[17:07] Ralf Handl (SAP SE): Mike: iii.ODATA-1187 No way to bind nav prop on recursively nested (contained or complex) type

[17:08] Ralf Handl (SAP SE): Mike: pushback on lack of DateTime data type

[17:09] Ralf Handl (SAP SE): Agenda is approved with the above changes

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

a.Minutes from June 07, 2018 TC meeting: https://www.oasis-open.org/committees/download.php/63236/odata-meeting-216_on-20180607-minutes.html

b.Minutes from May 24, 2018 TC meeting: https://www.oasis-open.org/committees/download.php/63235/odata-meeting-215_on-20180524-minutes.html

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

[17:10] 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.Action items due

i.none

[17:10] Michael Pizzo: Thread on lack of DateTime datatype inhibiting adoption of OData: https://stackoverflow.com/questions/820896/listobject-contains-_expression_-tree

[17:10] Michael Pizzo: Sorry; wrong link...

[17:10] Ralf Handl (SAP SE): 4.1 Mike on DateTime with unknown time zone

[17:11] Michael Pizzo: Thread on lack of DateTime datatype inhibiting adoption of OData:https://github.com/OData/WebApi/issues/136

[17:15] Ralf Handl (SAP SE): We could add an Edm.LocalDateTime with the explicit meaning that the time zone of this timestamp is unknown and that clients MUST NOT assume it to be UTC

[17:17] Ralf Handl (SAP SE): Mike: use a type definition over Edm.String with a pattern validation

[17:18] Ralf Handl (SAP SE): George: define a term for annotating string properties

[17:20] Ralf Handl (SAP SE): Pattern validation: https://github.com/oasis-tcs/odata-vocabularies/blob/master/vocabularies/Org.OData.Validation.V1.md#Pattern

[17:21] Ralf Handl (SAP SE): George: also introduce further annotations for e.g. ISO 8601 intervals

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

[17:26] Ralf Handl (SAP SE): Mike to reopen ODATA-220 and prepare a proposal

[17:27] Ralf Handl (SAP SE): 5.b.iv. ODATA-1183 Allow Singletons to be null

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

[17:32] Ralf Handl (SAP SE): ODATA-1183 is OPEN

[17:32] Ralf Handl (SAP SE): Mike: seems consistent with single-valued nullable navigation properties

[17:33] Ralf Handl (SAP SE): Ralf: is also consistent with top-level function imports with a nullable return type

[17:34] Ralf Handl (SAP SE): If singleton is null, follow 11.2.7 Requesting Related Entities

If the relationship terminates on a single entity, the response MUST be the format-specific representation of the related single entity. If no entity is related, the service returns 204 No Content.

[17:48] Ralf Handl (SAP SE): Postponed to next week

[17:48] Ralf Handl (SAP SE): Homework: think about the default - consistency with navigation properties versus compatibility with V4

[17:48] Ralf Handl (SAP SE): 5.b.iii. ODATA-1187 No way to bind nav prop on recursively nested (contained or complex) type

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

[17:50] Michael Pizzo: Example complex type containing a navigation property:

<ComplexType Name="Address">

<Property Name="PreviousAddress" Type="self.PreviousAddress" Nullable="true"/>

<NavigationProperty Name="Country" Type="self.Country"/>

</ComplexType>

[17:50] Michael Pizzo: To bind the country property of address within an entityset:

<EntitySet Name="Customers" EntityType="self.Customer">

<NavigationPropertyBinding Path="Address/Country" Target="Countries" />

<NavigationPropertyBinding Path="Address/PreviousAddress/Country" Target="Countries" />

</EntitySet>

[17:51] Ralf Handl (SAP SE): <NavigationPropertyBinding Path="Address/PreviousAddress*/Country" Target="Countries" />

[17:52] Ralf Handl (SAP SE): <NavigationPropertyBinding Path="Address/PreviousAddress+/Country" Target="Countries" />

[17:53] Ralf Handl (SAP SE): $expand=PreviousAddress($levels=5)

[17:53] Ralf Handl (SAP SE): Context URL: PreviousAddress+ with "+" suffix

[17:54] Michael Pizzo: Alternatively; to avoid a breaking change we could add an annotation to the exiting path that says "recursive"

[17:57] Michael Pizzo: Then we could specify the "recursive path" within the annotation (which may contain more than one segment)...

[18:11] Michael Pizzo: Might not need to specify path; if the path is recursive, you can annotate it with "recursive"...

[18:11] Michael Pizzo: We don't need to specify different bindings for different levels of recursion.

[18:12] Ralf Handl (SAP SE): ODATA-1187 is OPEN

[18:15] Ralf Handl (SAP SE): Mike to prepare a proposal

[18:24] Michael Pizzo: Note: we originally intended annotations as a first-class mechanism for compatibly extend metadata.  However, there are some model elements that cannot be annotated today (including NavigationPropertyBindings).  Should we fix this by making sure all elements can be annotated?

[18:27] Ralf Handl (SAP SE): Mike to open issue for Hubert on which metadata constructs should be annotatable

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

a.Data Aggregation: NEW or OPEN

i.ODATA-1159 Clarify context URLs for aggregated result sets

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

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

[18:36] Ralf Handl (SAP SE): Hubert: what if a property is primitive for some instances, and structured for others?

[18:37] Ralf Handl (SAP SE): What if identically named dynamic properties are differently structured / projected in different parts of the concatenated result?

[18:39] Ralf Handl (SAP SE): Outermost context URL specifies "most common" structure, deviating instances have individual context URLs

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

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

[18:40] Ralf Handl (SAP SE): ii.ODATA-1137 Clarify type information for dynamic properties in the aggregated result set

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

[18:44] Ralf Handl (SAP SE): ODATA-1137 is OPEN

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

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

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

[18:47] Ralf Handl (SAP SE): iii.ODATA-1073 Conformance section references wrong annotation term

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

[18:49] Ralf Handl (SAP SE): Replace "via the Custom Aggregates annotation" by "via the ApplySupported annotation"

[18:50] Ralf Handl (SAP SE): ODATA-1073 is OPEN

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

[18:51] Michael Pizzo: I second.

[18:51] Ralf Handl (SAP SE): ODATA-1073 is RESOLVED with the amended proposal

[18:51] Ralf Handl (SAP SE): iv.ODATA-1068 3.12 Transformation expand: require at least two parameters, with innermost expansion requiring a filter()

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

[18:52] Ralf Handl (SAP SE): An expand() transformation without a nested filter() is just a complicated identity transformation, so we should require a filter() for the innermost expand() transformation in a nested expand(). Outer and intermediate expand() don't need a filter() as they are necessary to reach the level where the filter() needs to be applied.

[18:53] Ralf Handl (SAP SE): ODATA-1068 is OPEN

[18:53] Ralf Handl (SAP SE): ..../expand(Products)/.... doesn't do anything

[18:54] Ralf Handl (SAP SE): .../expand(Products,filter(...)/... actually changes something

[18:57] Ralf Handl (SAP SE): GET ~/Categories?$apply=expand(Products,expand(Sales,filter(Amount gt 3)))

[18:58] Ralf Handl (SAP SE): $apply=expand(Products,expand(Sales,filter(Amount gt 3)),expand(Suppliers,expand(Products,filter(true))))

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

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

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

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

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

From: odata@lists.oasis-open.org [mailto:odata@lists.oasis-open.org] On Behalf Of Handl, Ralf
Sent: Dienstag, 12. Juni 2018 10:29
To: odata@lists.oasis-open.org
Subject: [CAUTION] [odata] Agenda for OData TC meeting on 2018-06-14

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

2. Approve agenda [8:05 am PT]

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

Minutes from June 07, 2018 TC meeting: https://www.oasis-open.org/committees/download.php/63236/odata-meeting-216_on-20180607-minutes.html
Minutes from May 24, 2018 TC meeting: https://www.oasis-open.org/committees/download.php/63235/odata-meeting-215_on-20180524-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]

Action items due

i. none

5. Issues [8:20 am PT]

Data Aggregation: NEW or OPEN

i. ODATA-1159 Clarify context URLs for aggregated result sets

ii. ODATA-1137 Clarify type information for dynamic properties in the aggregated result set

iii. ODATA-1073 Conformance section references wrong annotation term

iv. ODATA-1068 3.12 Transformation expand: require at least two parameters, with innermost expansion requiring a filter()

v. ODATA-1041 Broaden definitions of transformations topcount and bottomcount

vi. ODATA-1040 Clarification of term "_expression_"

vii. ODATA-1038 Clarify term "simple value"

viii. ODATA-977 Allow POST with $apply to invoke an action to an aggregated result

ix. ODATA-972 Example 30: wrong result

x. ODATA-971 7.1: Add example for grouping by single-valued navigation property

xi. ODATA-968 3.1.4: add example for from in aggregate() with multiple arguments

xii. ODATA-967 Chapter 3: remove restriction for input type of bound functions

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

xiv. ODATA-946 Clarify scope for $apply

xv. ODATA-945 Correct examples 53 and 54

xvi. ODATA-944 Clarify scope of property paths in transformations

xvii. ODATA-943 Correct broken link for Groupable Property

xviii. ODATA-909 ABNF for pathPrefix should also allow qualifiedComplexTypeName

xix. ODATA-905 Example 67: result row for USA, Sugar missing, Example 68: last total should be 7

xx. ODATA-904 Example 55: clarify groupby in combination with relationships of instance cardinality zero

xxi. ODATA-839 A recursive hierarchy annotation may also contain a navigation property to the children nodes

V4.01: NEW or OPEN

i. ODATA-1189 Conformance: Nullable for collections

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

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

iv. ODATA-1183 Allow Singletons to be null

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

vi. ODATA-1177 Core: add term SchemaLocation

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

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

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

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

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

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

xiii. ODATA-1135 Document use of JSON $schema

xiv. 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-1099 Add annotations to describe custom query options and custom headers

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

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

6. Next meetings [9:50 am PT]

Thursday June 21, 2018 during 8-10 am PDT (17:00-19:00 CEST)
Thursday June 28, 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