[odata] Agenda for OData TC meeting on 2015-10-08

anonymous morphed into Matt Borges (SAP)

Room information was updated by: Stefan

Please register at https://www.oasis-open.org/apps/org/workgroup/odata/event.php?event_id=39119

Stefan: Current participation result: Voting Members: 5 of 13 (38%) (used for quorum calculation)

Stefan: Note: Still only: Voting Members: 6 of 13 (46%) (used for quorum calculation)

Stefan: ... one to go.

Ralf Handl (SAP): Me

Stefan: Voting Members: 7 of 13 (53%) (used for quorum calculation)

Stefan: Quorate

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

Ralf Handl (SAP): Agenda is approved

Stefan: @Ralf: Please forward chat trace as usual, will now have to commute and hope for at least good voice line ... Thanks a bunch.

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

Ralf Handl (SAP): a.Minutes from October 01, 2015 TC meeting: https://www.oasis-open.org/committees/download.php/56641/odata-meeting-107_on-20151001-minutes.html

Ralf Handl (SAP): Minutes are approved

Ralf Handl (SAP): 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

Ralf Handl (SAP): 5.Planning and Next Steps [8:20am PT]

Ralf Handl (SAP): a.Extension for Data Aggregation

i.Public Review passed without comments

ii.Next possible steps

1.Promote it to CS02 with minor corrections, see agenda item 6.a.

Allows shipping of implementations based on it, especially with compute

2.Hold it back to get feedback from implementation teams

Makes shipping with post-CS01 features legally slippery

anonymous morphed into Mark Biamonte (Progress)

Ralf Handl (SAP): Agreement on proceeding Data Aggregation to CS02

Ralf Handl (SAP): Authors to prepare revised revision of the document

Ramesh Reddy(Redhat): that would be good for newer members like me

Ralf Handl (SAP): To be voted on in two weeks if no negative feedback from implementation teams comes up

Ralf Handl (SAP): Mike: review document with applied changes next week

Ralf Handl (SAP): b.JSON CSDL

Ralf Handl (SAP): i.Most issues resolved and applied

ii.Next steps

1.Finish document

2.Initiate first public review

iii.Put this on agenda every week to get it out the door?

Ralf Handl (SAP): Mike: split meeting time 50/50 between JSON CSDL and V4.01

Ralf Handl (SAP): Ramesh: JSON CSDL has been the most asked for topic recently, so this is appropriate

Ralf Handl (SAP): c.Version 4.01

i.Issues grouped and initially discussed

ii.Next steps

1.Decide on document structure, see ODATA-743

2.Request starter documents

3.Resolve and apply remaining 13 issues for Errata03 before forking off V4.01 documents?

Ralf Handl (SAP): Mike: put priority on issues that affect both Errata03 and V4.01

Ralf Handl (SAP): 6.Process issues [Issues list: https://issues.oasis-open.org/issues/?jql=project%20%3D%20ODATA] [9:00am PT]

Ralf Handl (SAP): a.Issues for Data Aggregation in New or Open state

Ralf Handl (SAP): i.ODATA-833           Example 40 applies term RecursiveHierarchy term incorrectly

Ralf Handl (SAP): ODATA-833 is OPEN

Gerald Krause (SAP): I move to solve OData-833 as proposed.

Mike Pizzo: I second

Ralf Handl (SAP): ODATA-833 is resolved as proposed

Ralf Handl (SAP): ii.ODATA-851           groupby(): ABNF still allows more than two parameters

Ralf Handl (SAP): Change line 136 from

groupbyTrafo = 'groupby' OPEN BWS groupbyList *( BWS COMMA BWS applyExpr) BWS CLOSE

to

groupbyTrafo = 'groupby' OPEN BWS groupbyList [ BWS COMMA BWS applyExpr ] BWS CLOSE

Mike Pizzo: I move we resolved ODATA-851 as proposed

Gerald Krause (SAP): I second

Ralf Handl (SAP): ODATA-851 is resolved as proposed

Ralf Handl (SAP): iii.ODATA-857           Example 5: use two aggregate expressions

Ralf Handl (SAP): ODATA-857 is OPEN

Ralf Handl (SAP): Example 5:

GET ~/Sales?$apply=aggregate(Amount with sum as Total,Amount with max as MxA)

results in

  "@odata.context": "$metadata#Sales(Total,MxA)",

  "value": [

    { "@odata.id": null, "Total": 24, "MxA": 8 }

Ralf Handl (SAP): Example 5:

GET ~/Sales?$apply=aggregate(Amount with sum as Total,Amount with max as MxA)

results in

  "@odata.context": "$metadata#Sales(Total,MxA)",

  "value": [

    { "@odata.id": null, "Total": 24, "MxA": 8 }

Mike Pizzo: I move we resolve ODATA-857 as proposed

Gerald Krause (SAP): I second.

Mark Biamonte (Progress): I second

Ralf Handl (SAP): ODATA-857 is resolved as proposed

Ralf Handl (SAP): iv.ODATA-860           Move definition of Custom Aggregation Method to separate subsection.

Ralf Handl (SAP): 3.1.3.6 Custom Aggregation Methods

Services can define custom aggregation methods if the functionality offered by the standard aggregation methods is not sufficient for the intended consumers.

Custom aggregation methods MUST use a namespace-qualified name (see [OData-ABNF]), i.e. contain at least one dot. Dot-less names are reserved for future versions of this specification.

3.1.4 Keyword from

Ralf Handl (SAP): Mike: add example

Ralf Handl (SAP): ODATA-860 is OPEN

Mike Pizzo: I move to resolve ODATA-860 as proposed, including adding a new example for custom aggregations.

Mark Biamonte (Progress): I second

Gerald Krause (SAP): I second.

Ralf Handl (SAP): ODATA-860 is resolved as proposed, including adding a new example for custom aggregation

Ralf Handl (SAP): 7.Next meeting [9:50am PT]

a.Thursday October 15, 2015 during 8-10am PT?

Ralf Handl (SAP): No objections

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

Mike Pizzo: New process for highlighting issues for discussion: mark the "Environment" field with [Needs Discussion]. We will add these to the agenda, along with new and proposed issues to be discussed.

Ralf Handl (SAP): AOB-1: Process issues Errata03

Ralf Handl (SAP): Walk through Change document

Ralf Handl (SAP): https://sap.emea.pgiconnect.com/OData-TC/

Ralf Handl (SAP): ODATA-840  Add example for $expand=NavProp/$count

Ralf Handl (SAP): ODATA-840 is OPEN

Mike Pizzo: I move we close ODATA-833, ODATA-851, and ODATA-857 as applied

Ramesh Reddy(Redhat): I second

Ralf Handl (SAP): ODATA-833, ODATA-851, and ODATA-857 are CLOSED as applied

Ralf Handl (SAP): Add example to URL conventions using $expand=NavProp/$count.

 Add section/example to JSON Format describing that in this case the navigation property is NOT represented other than via instance annotations, and that NavProp@odata.count annotation is part of the response.

Mike Pizzo: I move we resolve ODATA-840 as proposed.

Ted Jones (Red Hat): I second

Mark Biamonte (Progress): i second

Ralf Handl (SAP): ODATA-840 is resolved as proposed

Ralf Handl (SAP): ODATA-837  Example 28: replace $deltaToken with a valid custom query option

Ralf Handl (SAP): Use server-generated-secret instead of $deltaToken

Ralf Handl (SAP): ODATA-837 is OPEN

Ralf Handl (SAP): ODATA-853  8.3.3: last sentence should use "header" instead of "preference"

Ralf Handl (SAP): 8.3.3 Header OData-EntityId

A response to a create operation that returns 204 No Content MUST include an OData-EntityId response header. The value of the header is the entity-id of the entity that was acted on by the request. The syntax of the OData-EntityId preference is specified in [OData-ABNF].

Ralf Handl (SAP): ODATA-853 is OPEN

Mark Biamonte (Progress): I move to resolve OData-853 as propose

Gerald Krause (SAP): I second

Ralf Handl (SAP): ODATA-853 is resolved as proposed

Ralf Handl (SAP): ODATA-852  8.3.1: superfluous text paragraph 3, sentence 1

Ralf Handl (SAP): As OData allows multiple formats for representing the same structured information, services SHOULD use weak ETags that only depend on the format-independent entity state is recommended.

Ralf Handl (SAP): As OData allows multiple formats for representing the same structured information, services SHOULD use weak ETags that only depend on the format-independent entity state.

Ralf Handl (SAP): ODATA-852 is OPEN

Mark Biamonte (Progress): I move to resolve OData-852 as proposed

Gerald Krause (SAP): I move to resolve ODATA-852 as proposed.

Gerald Krause (SAP): I second.

Ralf Handl (SAP): ODATA-852 is resolved as proposed

Ralf Handl (SAP): ODATA-835  5.1: PATCH missing in list of operations that do not allow system query options

Ralf Handl (SAP): POST requests to entity sets as well as all PUT and DELETE requests do not allow system query options.

Ralf Handl (SAP): POST requests to entity sets as well as all PATCH, PUT and DELETE requests do not allow system query options.

Ralf Handl (SAP): ODATA-835 is OPEN

Mike Pizzo: I move we resolve ODATA-835 as proposed.

Gerald Krause (SAP): I second.

Ralf Handl (SAP): ODATA-835 is resolved as proposed

Ralf Handl (SAP): ODATA-828  Update I-JSON reference

Ralf Handl (SAP): [I-JSON] Bray, T., Ed., "The I-JSON Message Format" draft-bray-i-json-01, 06 January 2014. http://tools.ietf.org/html/draft-bray-i-json-01

 to (NEW):

 [RFC7493] Bray, T., Ed., "The I-JSON Message Format", RFC 7493, March 2015. https://tools.ietf.org/html/rfc7493

Ralf Handl (SAP): ODATA-828 is OPEN

Ralf Handl (SAP): Mark is going to check if there are significant changes between the two document versions

Ralf Handl (SAP): ODATA-861  ODATA-813 / Define behavior when neither accept header or $format query parameter is specified

Ralf Handl (SAP): As far as I could find, the spec does not define what the expected behavior should be when neither an accept header nor a $format query parameter is specified in a request. Does the server return the response in a spec defined default format or does the server get to choose which format to return results in.

 We should also cover the case of ambiguous Accept headers containing */*: currently the Olingo server library responds to requests from IE and Chrome with Atom-XML:

 - Internet Explorer sends Accept: text/html, application/xhtml+xml, */*

 - Chrome sends Accept: text/html,application/xhtml+xml,application/xml;q=0.9,image/webp,*/*;q=0.8

 As application/json isn't explicitly mentioned, they use application/xml

Ralf Handl (SAP): ODATA-861 is OPEN

Mike Pizzo: Proposal: Clarify in specification that, in absence of $format or accept header, service is allowed to return results in any format.

The current olingo behavior is, unfortunately, correct given the headers specified by IE and Chrome.

Ramesh Reddy(Redhat): I move to resolve ODATA-861 as proposed

Mark Biamonte (Progress): I second

Ralf Handl (SAP): ODATA-861 is resolved as proposed

Ralf Handl (SAP): Meeting is adjourned

From: odata@lists.oasis-open.org [mailto:odata@lists.oasis-open.org] On Behalf Of Handl, Ralf
Sent: Mittwoch, 7. Oktober 2015 12:17
To: odata@lists.oasis-open.org
Subject: [odata] Agenda for OData TC meeting on 2015-10-08

Here [1] is a draft agenda for the OData TC (Technical Committee) meeting scheduled on Thursday October 08, 2015 during 8-10am 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:00am PT]

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

2. Approve agenda [8:05am PT]

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

a. Minutes from October 01, 2015 TC meeting: https://www.oasis-open.org/committees/download.php/56641/odata-meeting-107_on-20151001-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. Action items due

i. None

5. Planning and Next Steps [8:20am PT]

a. Extension for Data Aggregation