RE: [odata] Agenda for OData TC meeting on 2018-03-22 - chat transcript

["Handl, Ralf" <ralf.handl@sap.com>]

[15:48] Room information was updated by: Stefan Hagen

OASIS Open Data Protocol (OData) TC OData TC Weekly Meeting (Conference Call) #208

- Thursday, 22 March 2018, 08:00am to 10:00am PDT

   - i.e. 2018-03-22 16:00 to 18:00 CET (UTC+1)

   - other timezone? Try eg.:

    - https://www.timeanddate.com/worldclock/meetingdetails.html?year=2018&month=3&day=22&hour=15&min=0&sec=0&p1=47&p2=69&p3=179

TimezoneInterferences:

- In North America, daylight savings time began on March 11th. (Ends November 4th if you want to be proactive.) 

- In Europe (by and large), daylight savings time begins later on March 25th. 

- Note as always that different locales do this differently. 

  - (For example, Mexico starts on April 1st.) So folks may want to check to be sure. 

UsefulPlaces:

- Chat:

   - http://webconf.soaphub.org/conf/room/odatatc   # ... this place

- ScreenShare and Voice:

   - https://sap.emea.pgiconnect.com/OData-TC

Next Planned meetings (tentative):

- Thursday March 29, 2018 during 8-10 am PDT (17:00-18:00 CEST)  Daylight Saving Time for All 

   - https://www.oasis-open.org/apps/org/workgroup/odata/event.php?event_id=46249

- Thursday April 05, 2018 during 8-10 am PDT (17:00-18:00 CEST)  Week after Easter?

   - https://www.oasis-open.org/apps/org/workgroup/odata/event.php?event_id=46250

Agenda-Draft E-Mail URL:

- E-Mail Public URL = "" href="https://lists.oasis-open.org/archives/odata/201803/msg00062.html" target="_blank">https://lists.oasis-open.org/archives/odata/201803/msg00062.html

Minutes Draft Public URL (previous meeting):

- URL = "" href="https://www.oasis-open.org/committees/download.php/62704/odata-meeting-207_on-20180315-minutes.html" target="_blank">https://www.oasis-open.org/committees/download.php/62704/odata-meeting-207_on-20180315-minutes.html

Online document walkthroughs or presentations:

- URL = "" href="https://sap.emea.pgiconnect.com/OData-TC" target="_blank">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 

Timeline(Updated!):

- URL = "" href="https://www.oasis-open.org/committees/download.php/62637/TC%20Timeline-2018-03-02.docx" target="_blank">https://www.oasis-open.org/committees/download.php/62637/TC%20Timeline-2018-03-02.docx 

Agenda Draft (for meeting #20:

==============================================================

1. Roll call [8:00 am PT]

  1.1 Self-registration link: 

      URL = "" href="https://www.oasis-open.org/apps/org/workgroup/odata/event.php?event_id=46248" target="_blank">https://www.oasis-open.org/apps/org/workgroup/odata/event.php?event_id=46248 

2. Approve agenda [8:05 am PT]

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

  3.1 Minutes from March 15, 2018 TC meeting: 

      URL = "" href="https://www.oasis-open.org/committees/download.php/62704/odata-meeting-207_on-20180315-minutes.html" target="_blank">https://www.oasis-open.org/committees/download.php/62704/odata-meeting-207_on-20180315-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]

  4.1 Action items due

    4.1.1 none

5. Issues [8:20 am PT]

  5.1 V4.01: NEW or OPEN 

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

    5.1.2 ODATA-1163 A Case for Common Expressions

    5.1.3 ODATA-1154 Clarify which OData-Version a service should return

    5.1.4 ODATA-1149 Support Delta responses for Singletons

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

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

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

    5.1.8 ODATA-1135 Document use of JSON $schema

    5.1.9 ODATA-1088 Clarify effect of applying an Annotation to an element

  5.2 Vocabularies: NEW or OPEN with concrete proposal

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

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

  5.3 Vocabularies: NEW or OPEN that need more discussion

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

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

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

  5.4 Data Aggregation: NEW or OPEN

    5.4.1  ODATA-1162 Fix data type in example model

    5.4.2  ODATA-1161 Clarify how to process hybrid results of a transformation in subsequent transformations

    5.4.3  ODATA-1160 Clarify example 66 in section 7.5

    5.4.4  ODATA-1159 Clarify context URLs for aggregated result sets

    5.4.5  ODATA-1158 Transformations for limiting the number of entities in the result of a $apply transformation

    5.4.6  ODATA-1157 Transformation for sorting entities created by a $apply transformation

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

    5.4.8  ODATA-1073 Conformance section references wrong annotation term

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

    5.4.10 ODATA-1041 Broaden definitions of transformations topcount and bottomcount

    5.4.11 (and 16 more)

6. Next meetings [9:50 am PT]

  6.1 Thursday March 29, 2018 during 8-10 am PDT (17:00-19:00 CEST)  back to normal time difference, vacations???

  6.2 Thursday April 05, 2018 during 8-10 am PDT (17:00-19:00 CEST)  Week after Easter?

  6.3 Thursday April 12, 2018 during 8-10 am PDT (17:00-19:00 CEST)

7. AOB and wrap up [9:55 am PT]

==============================================================

Meeting Member URL:

- URL = "" href="https://www.oasis-open.org/apps/org/workgroup/odata/event.php?event_id=46248" target="_blank">https://www.oasis-open.org/apps/org/workgroup/odata/event.php?event_id=46248

   - Please use starting approx. 15 minutes before the meeting for self registration. Thanks.

   - Self registration deep link (as a service):

     - https://www.oasis-open.org/apps/org/workgroup/odata/record_my_attendance.php?event_id=46248&confirmed=1

[15:48] Stefan Hagen: H4Q::Voting Members: 1 of 11 (9%) (used for quorum calculation)

Room Information:

OASIS Open Data Protocol (OData) TC OData TC Weekly Meeting (Conference Call) #208

- Thursday, 22 March 2018, 08:00am to 10:00am PDT

   - i.e. 2018-03-22 16:00 to 18:00 CET (UTC+1)

   - other timezone? Try eg.:

    - https://www.timeanddate.com/worldclock/meetingdetails.html?year=2018&month=3&day=22&hour=15&min=0&sec=0&p1=47&p2=69&p3=179

TimezoneInterferences:

- In North America, daylight savings time began on March 11th. (Ends November 4th if you want to be proactive.) 

- In Europe (by and large), daylight savings time begins later on March 25th. 

- Note as always that different locales do this differently. 

  - (For example, Mexico starts on April 1st.) So folks may want to check to be sure. 

UsefulPlaces:

- Chat:

   - http://webconf.soaphub.org/conf/room/odatatc   # ... this place

- ScreenShare and Voice:

   - https://sap.emea.pgiconnect.com/OData-TC

Next Planned meetings (tentative):

- Thursday March 29, 2018 during 8-10 am PDT (17:00-18:00 CEST)  Daylight Saving Time for All 

   - https://www.oasis-open.org/apps/org/workgroup/odata/event.php?event_id=46249

- Thursday April 05, 2018 during 8-10 am PDT (17:00-18:00 CEST)  Week after Easter?

   - https://www.oasis-open.org/apps/org/workgroup/odata/event.php?event_id=46250

Agenda-Draft E-Mail URL:

- E-Mail Public URL = "" href="https://lists.oasis-open.org/archives/odata/201803/msg00062.html" target="_blank">https://lists.oasis-open.org/archives/odata/201803/msg00062.html

Minutes Draft Public URL (previous meeting):

- URL = "" href="https://www.oasis-open.org/committees/download.php/62704/odata-meeting-207_on-20180315-minutes.html" target="_blank">https://www.oasis-open.org/committees/download.php/62704/odata-meeting-207_on-20180315-minutes.html

Online document walkthroughs or presentations:

- URL = "" href="https://sap.emea.pgiconnect.com/OData-TC" target="_blank">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 

Timeline(Updated!):

- URL = "" href="https://www.oasis-open.org/committees/download.php/62637/TC%20Timeline-2018-03-02.docx" target="_blank">https://www.oasis-open.org/committees/download.php/62637/TC%20Timeline-2018-03-02.docx 

Agenda Draft (for meeting #20:

==============================================================

1. Roll call [8:00 am PT]

  1.1 Self-registration link: 

      URL = "" href="https://www.oasis-open.org/apps/org/workgroup/odata/event.php?event_id=46248" target="_blank">https://www.oasis-open.org/apps/org/workgroup/odata/event.php?event_id=46248 

2. Approve agenda [8:05 am PT]

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

  3.1 Minutes from March 15, 2018 TC meeting: 

      URL = "" href="https://www.oasis-open.org/committees/download.php/62704/odata-meeting-207_on-20180315-minutes.html" target="_blank">https://www.oasis-open.org/committees/download.php/62704/odata-meeting-207_on-20180315-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]

  4.1 Action items due

    4.1.1 none

5. Issues [8:20 am PT]

  5.1 V4.01: NEW or OPEN 

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

    5.1.2 ODATA-1163 A Case for Common Expressions

    5.1.3 ODATA-1154 Clarify which OData-Version a service should return

    5.1.4 ODATA-1149 Support Delta responses for Singletons

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

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

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

    5.1.8 ODATA-1135 Document use of JSON $schema

    5.1.9 ODATA-1088 Clarify effect of applying an Annotation to an element

  5.2 Vocabularies: NEW or OPEN with concrete proposal

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

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

  5.3 Vocabularies: NEW or OPEN that need more discussion

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

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

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

  5.4 Data Aggregation: NEW or OPEN

    5.4.1  ODATA-1162 Fix data type in example model

    5.4.2  ODATA-1161 Clarify how to process hybrid results of a transformation in subsequent transformations

    5.4.3  ODATA-1160 Clarify example 66 in section 7.5

    5.4.4  ODATA-1159 Clarify context URLs for aggregated result sets

    5.4.5  ODATA-1158 Transformations for limiting the number of entities in the result of a $apply transformation

    5.4.6  ODATA-1157 Transformation for sorting entities created by a $apply transformation

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

    5.4.8  ODATA-1073 Conformance section references wrong annotation term

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

    5.4.10 ODATA-1041 Broaden definitions of transformations topcount and bottomcount

    5.4.11 (and 16 more)

6. Next meetings [9:50 am PT]

  6.1 Thursday March 29, 2018 during 8-10 am PDT (17:00-19:00 CEST)  back to normal time difference, vacations???

  6.2 Thursday April 05, 2018 during 8-10 am PDT (17:00-19:00 CEST)  Week after Easter?

  6.3 Thursday April 12, 2018 during 8-10 am PDT (17:00-19:00 CEST)

7. AOB and wrap up [9:55 am PT]

==============================================================

Meeting Member URL:

- URL = "" href="https://www.oasis-open.org/apps/org/workgroup/odata/event.php?event_id=46248" target="_blank">https://www.oasis-open.org/apps/org/workgroup/odata/event.php?event_id=46248

   - Please use starting approx. 15 minutes before the meeting for self registration. Thanks.

   - Self registration deep link (as a service):

     - https://www.oasis-open.org/apps/org/workgroup/odata/record_my_attendance.php?event_id=46248&confirmed=1

[16:02] Ralf Handl (SAP SE): Voting Members: 5 of 11 (45%) (used for quorum calculation)

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

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

[16:04] Ralf Handl (SAP SE): Quorum achieved: yes

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

[16:06] Ralf Handl (SAP SE): Mike: heads-up on feedback from OASIS directors

[16:08] Ralf Handl (SAP SE): Citation: OData adoption is "off the charts"

[16:09] Ralf Handl (SAP SE): If you know of companies interested in participating in the OData TC, please let Robin Cover (and us) know

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

a.Minutes from March 15, 2018 TC meeting: https://www.oasis-open.org/committees/download.php/62704/odata-meeting-207_on-20180315-minutes.html

[16:12] Ralf Handl (SAP SE): No comments, meeting minutes are approved

[16:12] Ralf Handl (SAP SE): @Stefan: thanks for transforming the somewhat chaotic chat transcripts into readable minutes

[16:13] 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

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

a.V4.01: NEW or OPEN

[16:13] Ralf Handl (SAP SE): i.ODATA-1165 Describe $expand and $select via prose text and examples, remove ABNF snippets

[16:14] Ralf Handl (SAP SE): http://docs.oasis-open.org/odata/odata/v4.01/cs01/part2-url-conventions/odata-v4.01-cs01-part2-url-conventions.html#_Toc505773297

[16:18] Ralf Handl (SAP SE): Mike: would be helpful to have an example of how this would look like

[16:19] Ralf Handl (SAP SE): Just remove ABNF *snippets* from prose spec, keep ABNF as machine-readable work product

[16:19] Ralf Handl (SAP SE): ODATA-1165 is OPEN

[16:20] Ralf Handl (SAP SE): ii.ODATA-1163 A Case for Common Expressions

[16:20] Ralf Handl (SAP SE): Proposal:

The case function has the following signatures: 

_expression_ case(Edm.Boolean:_expression_, ..., Edm.Boolean:_expression_) 

_expression_ case(Edm.Boolean:_expression_, ..., Edm.Boolean:_expression_,_expression_) 

Each Edm.Boolean:_expression_ parameter is a tuple separated by a colon, where the first component evaluates to a Boolean value, and the second component may be an _expression_ of any type. 

The case function returns the _expression_ value of the leftmost parameter, whose first component evaluates to true. If none of the parameters match, case returns null, unless the last parameter is an _expression_, whose value is returned otherwise. 

If all parameter expressions are of numeric type, the return value has a numeric type capable of representing any of these expressions. Otherwise, the return value is the result of casting the _expression_ of the matching parameter to Edm.String.

[16:24] Ralf Handl (SAP SE): Mike: if all expressions are of the same type, return that type

[16:27] Gerald Krause (SAP): Mike: If all expressions are of the same type, the return value is of this type

[16:30] Michael Pizzo: Key question: is it important to know the type of the _expression_? Or can we say that the type is dependent upon the value (i.e., the type of the _expression_ is Edm.Any)

[16:32] Ralf Handl (SAP SE): Homework: check your (intended) implementations on what they require / can deal with

[16:39] Gerald Krause (SAP): Hubert: How to handle the unknown type of dynamic properties from open types in case result expressions?

[16:43] Ralf Handl (SAP SE): i.ODATA-1154 Clarify which OData-Version a service should return

[16:43] Ralf Handl (SAP SE): Proposed rewording: The service MUST respond with a payload compliant with the greatest version of the protocol that is less than or equal to the request's OData-MaxVersion, if specified. 

Questions: 

1) What if no OData-MaxVersion is specified? 

2) Does specifying an OData-Version limit the constructs that the request can use in the URL? i.e., if I have a 4.0 payload, am I restricted to 4.0 URL constructs, even if I know the service supports them? 

3) What if the client *only* support 4.01? Do we have a way to specify NOT to return 4.0? 

4) Does a service have to return a 4.01 payload if the request uses a 4.01 construct?

[16:45] Ralf Handl (SAP SE): Ad 1: Current spec says

If OData-MaxVersion is not specified, then the service SHOULD interpret the request as having an OData-MaxVersion equal to the maximum version supported by the service.

[16:45] Ralf Handl (SAP SE): Means: return max version the service implements

[16:45] Ralf Handl (SAP SE): I.e. the latest and greatest

[16:48] Ralf Handl (SAP SE): Hubert: implemented it that way

[16:51] Ralf Handl (SAP SE): Mike: can we leave that up to each service?

[16:53] Michael Pizzo: We say that an interoperable odata client should specify the odata-maxversion.  in the absence of specifying an odata-maxversion, we should probably leave it up to the service.

[16:54] Ralf Handl (SAP SE): Mike: "same request must return same result"

[16:55] Ralf Handl (SAP SE): This means no MaxVersion is equivalent to MaxVersion:4.0

[16:55] Michael Pizzo: No, it means no maxversion is equivalent to the first (default) version that the service implemented.  If it started as a 4.01 service it might always default to 4.01

[16:56] Ralf Handl (SAP SE): Yes, now 

[17:00] Ralf Handl (SAP SE): Rephrase spec to:

If OData-MaxVersion is not specified, then the service SHOULD interpret the request as having an OData-MaxVersion equal to the *initial* version supported by the service

[17:01] Ralf Handl (SAP SE): to keep the service behavior consistent over time

[17:02] Ralf Handl (SAP SE): Mike: 1) "initial default version of the service"

[17:08] Ralf Handl (SAP SE): If OData-MaxVersion is not specified, then the service SHOULD interpret the request as having an OData-MaxVersion equal to the *initial default* version produced by the service

[17:08] Ralf Handl (SAP SE): 2) Does specifying an OData-Version limit the constructs that the request can use in the URL? i.e., if I have a 4.0 payload, am I restricted to 4.0 URL constructs, even if I know the service supports them?

[17:09] Ralf Handl (SAP SE): Mike: can a service accept request URLs with e.g. the "in" operator if the client specifies OData-Version:4.0

[17:10] Ralf Handl (SAP SE): Mike: yes

[17:11] anonymous morphed into G

[17:11] Ralf Handl (SAP SE): OData-Version only has to reflect the payload of the request

[17:11] Ralf Handl (SAP SE): Current text:

OData clients SHOULD use the OData-Version header on a request to specify the version of the protocol used to generate the request.

[17:12] Ralf Handl (SAP SE): Rephrase to:

OData clients SHOULD use the OData-Version header on a request to specify the version of the protocol used to generate the request *body*.

[17:13] Ralf Handl (SAP SE): Or *payload* -> check what we consistently use

[17:14] Ralf Handl (SAP SE): 3) What if the client *only* support 4.01? Do we have a way to specify NOT to return 4.0?

[17:14] Ralf Handl (SAP SE): No MinVersion (yet)

[17:17] Michael Pizzo: If the client inspects the metadata to determine the service supports 4.01, and requests a maxversion of 4.01, the above rule requires that the service return 4.01.

[17:18] G morphed into George Ericson (Dell)

[17:20] Ralf Handl (SAP SE): 4) Does a service have to return a 4.01 payload if the request uses a 4.01 construct?

[17:20] Ralf Handl (SAP SE): Mike: OData-Version:4.01 OData-MaxVersion:4.0

[17:21] Ralf Handl (SAP SE): George: sounds like too much flexibility

[17:24] Michael Pizzo: 4) Request and response payloads are independent. The service must honor OData-MaxVersion in a response regardless of the version of the request payload.

[17:25] Michael Pizzo: Similar to the fact that the request payload could be different than a response payload.

[17:25] Michael Pizzo: Summarized in issue:

1) The same request should return the same response, so in the absence of an odata-maxversion header, the service should return the same payload over time.  "If OData-MaxVersion is not specified, then the service SHOULD interpret the request as having an OData-MaxVersion equal to the *initial default* version produced by the service".

2) Client is allowed to use 4.01 without specifying an OData-Version or OData-MaxVersion of 4.01. A payload MUST specify the OData-Version of the request body.

3) If the client inspects the metadata to determine the service supports 4.01, and requests a maxversion of 4.01, the proposed general rule requires that the service return 4.01 (we can introduce a min version in the future, if required).

4) Request and response payloads are independent. The service must honor OData-MaxVersion in a response regardless of the version of the request payload.

[17:32] Michael Pizzo: Proposal:

The service MUST respond with a payload compliant with the greatest supported version of the protocol that is less than or equal to the request's OData-MaxVersion, if specified. 

The same request should return the same response, so in the absence of an odata-maxversion header, the service should return the same payload over time.  "If OData-MaxVersion is not specified, then the service SHOULD interpret the request as having an OData-MaxVersion equal to the *initial default* version produced by the service".

Client is allowed to use 4.01 without specifying an OData-Version or OData-MaxVersion of 4.01. If a request has a payload, a compliant client MUST specify the OData-Version of the request body.

If the client inspects the metadata to determine the service supports 4.01, and requests a maxversion of 4.01, the proposed general rule requires that the service return 4.01 (we can introduce a min version in the future, if required).

Request and response payloads are independent. The service must honor OData-MaxVersion in a response regardless of the version of the request payload.

[17:33] Hubert Heijkers (IBM): I move to resolve ODATA-1154 as per the amended proposal.

[17:34] Michael Pizzo: I second

[17:34] Ralf Handl (SAP SE): ODATA-1154 is RESOLVED with the above proposal

[17:34] Ralf Handl (SAP SE): iv.ODATA-1149 Support Delta responses for Singletons

[17:35] Ralf Handl (SAP SE): Ralf: need new context URL pattern to distinguish this from "full object"

[17:44] Ralf Handl (SAP SE): "@context":"http://host/service/$metadata#Customers/$delta",

  "@context":"http://host/service/$metadata#MySingleton/$delta",

[17:46] Michael Pizzo: In 4.01, the delta response for a singleton is represented as a single top-level object with (possibly nested) changes.

In 4.0, the response could (in theory) be an array containing a flattened response or a single object with nested content showing the after-image.

[17:46] Michael Pizzo: George: This also applies to single-valued navigation properties?

[17:47] Michael Pizzo: Yes, as well as collection-valued navigation properties (which may not have been clear in 4.0)

[17:53] Michael Pizzo: Proposal:

Deltas can be supported for singletons and single-value navigation properties as well as entities and collection-valued navigation properties.

The context url for a delta against a singleton (or single-valued nav prop) follows the same pattern of appending /$delta to the context url returned by a request against that singleton (or single-valued nav prop).

The 4.01 JSON payload for a delta request/response rooted in a single object is the single object with nested changes (i.e., propertyName@delta).

We don't define a 4.0 JSON format for a delta payload for a request/response rooted in a single object.

[17:54] Michael Pizzo: I move we resolve ODATA-1149 as proposed.

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

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

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

a.Thursday March 29, 2018 during 8-10 am PDT (17:00-19:00 CEST)  back to normal time difference, vacations???

b.Thursday April 05, 2018 during 8-10 am PDT (17:00-19:00 CEST)  Week after Easter?

c.Thursday April 12, 2018 during 8-10 am PDT (17:00-19:00 CEST)

[17:56] Ralf Handl (SAP SE): a) no meeting next week

[17:57] Ralf Handl (SAP SE): b.Thursday April 05, 2018 during 8-10 am PDT (17:00-19:00 CEST)  Week after Easter?

c.Thursday April 12, 2018 during 8-10 am PDT (17:00-19:00 CEST)

[17:58] Ralf Handl (SAP SE): b: Gerald can't, Mike and Matt can,

[17:58] Ralf Handl (SAP SE): George can

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

a. 

b.Thursday April 05, 2018 during 8-10 am PDT (17:00-19:00 CEST)  Week after Easter?

c.Thursday April 12, 2018 during 8-10 am PDT (17:00-19:00 CEST)

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

[17:59] Ralf Handl (SAP SE): Meeting is adjourned

[18:00] Ralf Handl (SAP SE): Happy Easter!

 

 

From: odata@lists.oasis-open.org [mailto:odata@lists.oasis-open.org] On Behalf Of Handl, Ralf
Sent: Mittwoch, 21. März 2018 09:40
To: odata@lists.oasis-open.org
Subject: [CAUTION] [odata] Agenda for OData TC meeting on 2018-03-22

 

Here [1] is a draft agenda for the OData TC (Technical Committee) meeting scheduled on Thursday March 22, 2018 during 8-10 am PDT (16:00-18:00 CET). 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]

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

 

2.        Approve agenda [8:05 am PT]

 

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

1. Minutes from March 15, 2018 TC meeting: https://www.oasis-open.org/committees/download.php/62704/odata-meeting-207_on-20180315-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]

1. Action items due

                                  i.    none

 

5.        Issues [8:20 am PT]

1. V4.01: NEW or OPEN

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

                                 ii.    ODATA-1163 A Case for Common Expressions

                                iii.    ODATA-1154 Clarify which OData-Version a service should return

                                iv.    ODATA-1149 Support Delta responses for Singletons

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

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

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

                              viii.    ODATA-1135 Document use of JSON $schema

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

 

2. Vocabularies: NEW or OPEN with concrete proposal

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

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

 

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

 

4. Data Aggregation: NEW or OPEN

                                  i.    ODATA-1162 Fix data type in example model

                                 ii.    ODATA-1161 Clarify how to process hybrid results of a transformation in subsequent transformations

                                iii.    ODATA-1160 Clarify example 66 in section 7.5

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

                                 v.    ODATA-1158 Transformations for limiting the number of entities in the result of a $apply transformation

                                vi.    ODATA-1157 Transformation for sorting entities created by a $apply transformation

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

                              viii.    ODATA-1073 Conformance section references wrong annotation term

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

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

                                xi.    (and 16 more)

 

6.        Next meetings [9:50 am PT]

1. Thursday March 29, 2018 during 8-10 am PDT (17:00-19:00 CEST) – back to normal time difference, vacations???
2. Thursday April 05, 2018 during 8-10 am PDT (17:00-19:00 CEST) – Week after Easter?
3. Thursday April 12, 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