RE: [odata] Agenda for OData TC meeting on 2015-05-07

Chat transcript:

Room information was updated by: Stefan

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

Stefan: Info: Voting Members: 1 of 14 (7%) (used for quorum calculation)

Stefan: Info:Voting Members: 1 of 14 (7%) (used for quorum calculation)

Stefan: Info: Voting Members: 2 of 14 (14%) (used for quorum calculation)

Stefan: Info: Voting Members: 7 of 14 (50%) (used for quorum calculation)

Stefan: Info: Voting Members: 8 of 14 (57%) (used for quorum calculation) We are quorate

Ralf Handl (SAP): 2.Approve agenda

Ralf Handl (SAP): Agenda is approved

Ralf Handl (SAP): 3.Approve minutes from previous meeting

Ralf Handl (SAP): a.Minutes from April 30, 2015 TC meeting: https://www.oasis-open.org/committees/download.php/55598/odata-meeting-96_on-20150430-minutes.html

Ralf Handl (SAP): Minutes approved

Ralf Handl (SAP): 4.Review action

Ralf Handl (SAP): a.Action items due

i.None

Ralf Handl (SAP): 5.Process issues

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

Ralf Handl (SAP): i.ODATA-759 6.2.3 Custom Aggregates: unprecise formulation

Ralf Handl (SAP): i.ODATA-759 6.2.3 Custom Aggregates: unprecise formulation

Ralf Handl (SAP): Change sentence from

 In this case, the value of the Type property MUST have the same value as the Type attribute of the declared property.

to

 In this case, the value of the annotation MUST have the same value as the Type attribute of the declared property.

Ralf Handl (SAP): ODATA-759 is OPEN

Martin Zurmuehl: I move to resolve ODATA-759 as proposed

Hubert Heijkers: I second

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

Ralf Handl (SAP): ii.ODATA-728 A recursive hierarchy annotation may also contain a navigation property to the parent node

Ralf Handl (SAP): NodeProperty: ID

ParentNodeProperty: Manager/ID

ParentNavigationProperty: Manager

Ralf Handl (SAP): ODATA-728 is OPEN

Gerald Krause (SAP): I move to resolve ODATA-728 with the amendment to remove the term property "ParentNodeProperty"

Stefan: I second

Ralf Handl (SAP): Objection: ParentNodeProperty must not be nullable

Ralf Handl (SAP): ParentNavigationProperty must not be nullable, ParentNodeProperty is removed

Hubert Heijkers: I move to resolve ODATA-728 with the following amendments; Remove the term property "ParentNodeProperty" and making the ParentNavigationProperty required by change the Nullable property to false.

Stefan: I second

Gerald Krause (SAP): I second

Ralf Handl (SAP): ODATA-728 is resolved with the amended proposal

Ralf Handl (SAP): iii.ODATA-727 Clarify the meaning of annotation values used for hierarchy terms

Ralf Handl (SAP): ODATA-727 is OPEN

Hubert Heijkers: I move to resolve ODATA-727 as proposed

Gerald Krause (SAP): I second

Martin Zurmuehl: i second

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

Ralf Handl (SAP): iv.ODATA-726 Describe the data model used for example 75

Ralf Handl (SAP): ODATA-726 is OPEN

Martin Zurmuehl: I move to resolve ODATA 726 as proposed

Gerald Krause (SAP): I second

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

Ralf Handl (SAP): v.ODATA-725 Missing navigation properties in diagram in section 2.2

Ralf Handl (SAP): ODATA-725 is OPEN

Gerald Krause (SAP): I move to resolve ODATA 725 as proposed

Hubert Heijkers: I second

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

Ralf Handl (SAP): vi.ODATA-703 Example 31: wrong description

Ralf Handl (SAP): ODATA-703 is OPEN

Hubert Heijkers: I move to resolve ODATA-703 as proposed

Ralf Handl (SAP): Mike suggests adding a correct description

Hubert Heijkers: I move to resolve ODATA-703 as proposed, while allowing the editors the freedom to come up with a creative description

Martin Zurmuehl: I second

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

Ralf Handl (SAP): vii.ODATA-702 Define the behaviour of system query option $count and path segment /$count in combination with $apply

Ralf Handl (SAP): $apply on resource paths ending in /$count acts on the set "preceding" the /$count, the result is the plain-text number of items in the result of $apply, similar to the combination of /$count and $filter

 $count system query option is executed after $apply, @odata.count contains the number of items in the result of $apply

Ralf Handl (SAP): ODATA-702 is OPEN

Hubert Heijkers: I move to resolve ODATA-702 as proposed

Stefan: second

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

Ralf Handl (SAP): viii.ODATA-701 Bug in Example 38: terms for LeveledHierarchy and RecursiveHierarchy incorrectly annotated

Ralf Handl (SAP): ODATA-701 is OPEN

Martin Zurmuehl: <Annotations Target="SalesModel.Product">

    <Annotation Term="Aggregation.LeveledHierarchy"

                Qualifier="ProductHierarchy">

     <Record>

      <PropertyValue Property="Levels">

        <Collection>

          <String>Category/Name</String>

          <String>Name</String>

        </Collection>

      </PropertyValue>

     </Record>

    </Annotation>

   </Annotations>

Ralf Handl (SAP): Term definition requires PropertyPath instead of String, values remain unchanged

Martin Zurmuehl: <Term Name="LeveledHierarchy" Type="Collection(Edm.PropertyPath)" AppliesTo="EntityType ComplexType">

Hubert Heijkers: I move to resolve ODATA-701 as proposed

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

Stefan: second

I second

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

Ralf Handl (SAP): ix.ODATA-662 Allow usage of $apply as "Expand Option" in $expand

Hubert Heijkers: <Sorry, had to drop as I mentioned at the start, just now we that we got to the one really interesting ticket;->

Martin Zurmuehl: We haven't specified the usage of $apply as "Expand Option" in $expand.

There are good use cases for $apply as an option of $expand (and it combines very well):

    GET Products?$expand=Sales($apply=aggregate(Amount with sum as Total))

Martin Zurmuehl: Returns all products, and the Sales navigation property value is a one-element array with the Total

Means: per Product in top-level result inline result of

Ralf Handl (SAP): Mike: does the syntax of $apply prevent nesting it in $expand?

Ralf Handl (SAP): Martin: no, no semicolons used in $apply syntax

Ralf Handl (SAP): Mike: seems like a pretty core thing

Ralf Handl (SAP): ODATA-662 is OPEN

Mike Pizzo: I move we approve OData-662 as proposed

Gerald Krause (SAP): I second

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

Ralf Handl (SAP): x.ODATA-588 Typo in example 10: query uses MaxAmount, response uses MinAmount

Ralf Handl (SAP): ODATA-588 is OPEN

Stefan: I move to resolve ODATA-588 as proposed.

Martin Zurmuehl: I move to resolve ODATA 588 as proposed

Gerald Krause (SAP): I second

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

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

a.Thursday May 21, 2015 during 8-10am PT?

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

Next meeting: Thursday May 21, 2015 during 8-10am PT

Ralf Handl (SAP): 7.AOB and wrap up

Ralf Handl (SAP): Mike: one topoc

Ralf Handl (SAP): Have accumulated several issues that go beyond errata

Ralf Handl (SAP): How about starting on V4.1 to address these issues

Ralf Handl (SAP): Related topic

Ralf Handl (SAP): People planning a REST API don't perceive OData as approrpiate

Ralf Handl (SAP): Spec is rather log

Ralf Handl (SAP): long

Ralf Handl (SAP): Name seems to limit it to "database access"

Ralf Handl (SAP): Not clear that entry barrier (minimal conformance) is pretty easy

Ralf Handl (SAP): Publish a "REST API Profile" - short description of how to start and use parts of OData to solve common REST API problems

Ralf Handl (SAP): I-REST, O-REST, ...

Ralf Handl (SAP): Mark: hear the same sort of comments

Ralf Handl (SAP): Complaints from client side that it looks too complex

Ralf Handl (SAP): Mike: looking at JSON or JSON Schema first impression is just one or two pages of text with examples, plus pointer to full spec

Ralf Handl (SAP): We should try to give the same first impression of simplicity

Ralf Handl (SAP): Mike will put together a proposal of how this could look like

Ralf Handl (SAP): Stefan: XML for $metadata also adds to the entry barrier

Ralf Handl (SAP): Using JSON (Schema) for CSDL would lower that barrier

Ralf Handl (SAP): Mike: need to check whether adding a JSON $metadata requires the TC to adjust its charter

Ralf Handl (SAP): Need to define the scope of our work for the next 12-18 months and have our charter reflect that

Ralf Handl (SAP): - JSON for $metadata

Ralf Handl (SAP): - V4.1 as a compatible protocol version with version negotiation

Ralf Handl (SAP): - I-REST / ... profile

Ralf Handl (SAP): Martin: make sure that the things we want to put into V4.1 doesn't make it too hard for V4.0 implementations to also support V4.1

Ralf Handl (SAP): Mike: need high degree of interop between 4.1 and 4.0, no substantive changes

Ralf Handl (SAP): Check existing issues "parked" on V4.1 whether they can be added "non-breaking"

Ralf Handl (SAP): Definitely: if client requests MaxVersion 4.0 it just gets plain 4.0

Ralf Handl (SAP): Stefan: non-breaking, compelling changes

Ralf Handl (SAP): Mike: identify what's important to add

Ralf Handl (SAP): Have both complete V4.1 spec plus a "delta to V4.0" document describing only the changes

Ralf Handl (SAP): Stefan: definitely worth it

Ralf Handl (SAP): Martin: talk about this in two weeks, notify Hubert of this decision

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, 6. Mai 2015 16:27
To: odata@lists.oasis-open.org
Subject: [odata] Agenda for OData TC meeting on 2015-05-07

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

2. Approve agenda [8:05am PT]

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

a. Minutes from April 30, 2015 TC meeting: https://www.oasis-open.org/committees/download.php/55598/odata-meeting-96_on-20150430-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. Process issues [Issues list: https://issues.oasis-open.org/issues/?jql=project%20%3D%20ODATA] [8:20am PT]

a. Issues for Data Aggregation in New or Open state