OData TC meeting #76 Thursday Jun 26, 2014

Acting chair: Ram

Chat transcript from room: odatatc
2014-06-26 0800-1000 PDT

1. Roll call

1.1 Members present

        Susan Malaika (IBM)
        Edmond Bourne (BlackBerry)
        Gerald Krause (SAP AG)
        Hubert Heijkers (IBM)
        John Willson (Individual)
        Ken Baclawski (Northeastern University)
        Mark Biamonte (Progress Software)
        Matthew Borges (SAP AG) a.k.a. Matt
        Michael Pizzo (Microsoft) a.k.a. Mike
        Patrick Durusau (Individual)
        Ralf Handl (SAP AG)
        Ram Jeyaraman (Microsoft)
        Stefan Drees (Individual)
        Susan Malaika (IBM)
        Ted Jones (Red Hat)
        Martin Zurmuehl (SAP AG)

Quorum achieved. Details cf. normative attendance sheet for this meeting.

2. Approve agenda

Agenda approved as published.

3. Approve minutes from previous meeting(s)

3.1 Minutes from June 12, 2014 TC meeting:

URL=from June 12, 2014 TC meeting#74

Minutes approval shifted to next meeting, to give all more time reading them

4. Review action items

URL=Action item list

4.1 Action items due by June 26, 2014

None

5. Process issues

OData v4 Errata issues in New or Open state:

ODATA-685 is OPEN

Mike summarizes the issue

Patrick: I move to call out as non-normative text.

Martin seconds

ODATA-704 is OPEN

Ralf: I move to resolve ODATA-704 as proposed.

Martin seconds

No objections, motion carries

ODATA-705 is OPEN

ODATA-706 is OPEN

Martin summarizes

Issue affects only Part 1 protocol

ODATA-707 is OPEN

Ralf summarizes that this issue was discovered by an implementation team and explains shortly the proposed resolution ways

All discuss if OData has to provide workarounds for JSON consumers or guidance for implementers of clients and servers when it comes to numbers as JSON only has endless numbers and does not really ensure consumers only receive numbers that match their host languages number concept.

Ralf considers this as mostly a format characteristics the providers and consumers have to deal with, but can't "repair" as this would try to change JSON.

Mike summarizes that thes points have to be dealt with but of course under the mentioned constraints from Ralf and Stefan and proposes to continue next week.

ODATA-708 is OPEN

Mike summarizes.

Matt thinks that makes sense

Martin thinks it sounds reasonable

Ralf: I move to resolve ODATA-705, ODATA-706, and ODATA-708 as proposed.

Stefan seconds

No objections and no more discussions, the motion carries ODATA-705, ODATA-706, and ODATA-708 are now resolved as proposed.

ODATA-709 is OPEN

Martin summarizes this purely editorial issue

Stefan takes this as "from __future__ import non_parens"

ODATA-710 is OPEN

ODATA-711 is OPEN

Ralf summarizes the issue

ODATA-712 is OPEN

Martin summarizes the issue

All discuss the missing things, the ticket proposes to add.

Martin suggests to add all examples for missing parts to the ticket, so Mike can check why we missed them in the first place and to form a consensus on adding them

Ralf gives some samples:

10.2 Collection of Entities 
Context URL template: 
{context-url}#{entity-set} 
{context-url}#Collection({type-name}) is missing
10.3 Entity 
Context URL template: 
{context-url}#{entity-set}/$entity 
{context-url}#{type-name} is missing

10.7 Collection of Projected Entities 
Context URL templates: 
{context-url}#{entity-set}{/type-name}{select-list} 
{context-url}#Collection({type-name}){select-list} is missing

10.8 Projected Entity 
Context URL templates: 
{context-url}#{entity-set}{/type-name}{select-list}/$entity 
{context-url}#{singleton}{select-list} 
{context-url}#{type-name}{select-list} is missing

10.9 Collection of Projected Expanded Entities 
Context URL template: 
{context-url}#{entity-set}{/type-name}{select-list} 
{context-url}#Collection({type-name}){select-list} is missing

10.10 Projected Expanded Entity 
Context URL template: 
{context-url}#{entity-set}{/type-name}{select-list}/$entity 
{context-url}#{singleton}{select-list} 
{context-url}#{type-name}{select-list} is missing

10.13 Property Value 
Context URL template: 
{context-url}#{entity}/{property-path} 
{context-url}#{type-name}/{property-path} is missing

10.16 Operation Result 
Context URL templates: 
{context-url}#{entity-set}{/type-name}{select-list} 
{context-url}#Collection({type-name}){select-list} is missing 
{context-url}#{entity-set}{/type-name}{select-list}/$entity 
{context-url}#{type-name}{select-list} is missing 
{context-url}#{entity}/{property-path} 
{context-url}#{type-name}/{property-path} is missing 
{context-url}#Collection({type-name}) 
{context-url}#{type-name}

Mke: I move to approve ODATA-709, OData-710 and ODATA-711 as proposed.

Martin seconds

No objections and no more discussions, the motion carries ODATA-709, OData-710 and ODATA-711 are now resolved as proposed.

No other issues

Note: Three of the above issues we will tackle later.

Ram summarizes the plan all agreed to come back next week to discuss the remaining issues

Mike asks if the others want to walk through the docs in the remainng time today

All agree to postpone to next week

6. Next meeting planned for Jul, 03 2014

Agreed

7. AOB

None

Meeting adjourned at 09:09 PDT