OData TC meeting #95 Thursday Apr 16, 2015

Acting chair: Ralf

Chat transcript from room: odatatc
2015-04-16 0800-1000 PDT

1. Roll call

1.1 Members present

        Gerald Krause (SAP AG)
        Hubert Heijkers (IBM)
        Jason Fam (IBM)
        John Willson (Individual)
        Ken Baclawski (Northeastern University)
        Mark Biamonte (Progress Software)
        Martin Zurmuehl (SAP AG)
        Matthew Borges (SAP AG) a.k.a. Matt
        Michael Pizzo (Microsoft) a.k.a. Mike
        Ralf Handl (SAP AG)
        Ramesh Reddy (Red Hat)
        Stefan Hagen (Individual)
        Ted Jones (Red Hat)

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

Notes taken by all and subsequently edited for readability by Stefan.

2. Approve agenda

Agenda approved as published.

3. Approve minutes from previous meeting(s)

3.1 Minutes from March 23, 2015 TC meeting #94:

Meeting#94 on 2015-MAR-23

Minutes approved unchanged as published

4. Review action items

URL=Action item list at https://www.oasis-open.org/apps/org/workgroup/odata/members/action_items.php

4.1 Action items due by April 16, 2015

4.1.1 Follow up with JSON-Schema on use for modeling

No news./p>

5. Process issues (for V4.0_ERRATA03 in New or Open state)

5.1 OData CSDL

5.1.1 ODATA-801 "Consider supporting negative scale for decimal type"


Mike: how does Oracle treat these data types in APIs (ODBC, ADO.net)

Mark: Will look into this

Defer to future meeting

Discuss together with other issues on Edm.Decimal: ODATA-771, ODATA-804

5.1.2 ODATA-803 "Collection-valued property: Define default value for nullable facet"

Mike: if Nullable facet is missing clients SHOULD expect that the collection may contain null values.
What do current implementations do?

Ramesh: To look into Olingo implementation

Mike: resolve as proposed and add note that absence of Nullable facet doesn't guarantee that service will accept null values

{ "value":[1,null,3] }


Martin: The edm http://webconf.soaphub.org/conf/images/tongue.gifroperty element MAY contain the Nullable attribute whose Boolean value specifies whether a value is required for the property.

Mike: I move we approve ODATA-803 as proposed, with a cautionary note to clients that, since this default was not defined in 4.0, in the absence of this facet clients should be prepared to receive collections containing null values but should be prepared for the service to refuse collections containing null values. Hubert seconds.

ODATA-803 is resolved as proposed

5.2 OData JSON Format

5.2.1 ODATA-771 "Exponential notation for Edm.Decimal values in JSON payloads"

Hubert proposes F2F in Hawaii between August 04 and August 17

Defer issue to future meeting

5.3 OData Protocol

5.3.1 ODATA-791 " System Query Option $orderby: specify order of Edm.Boolean and Edm.Geo"

Pizzo: I move we resolve ODATA-791 as proposed. Martin seconds.

ODATA-791 is resolved as proposed

5.4 OData Vocabularies

5.4.1 ODATA-802 "Define a vocabulary for odata.* annotations"

Mike: odata.* is special for JSON, the same meta information would not be represented as annotations in Atom.
If we make it a vocabulary, even in the context of the JSON Format specification, it may get used in $metadata


Matt: it seems odd that information is represented in JSON as annotations and differently in other formats

Matt: I move to close ODATA-802 without action. Mike seconds.

ODATA-802 is closed without action

6. Next meeting

Thursday April 30, 2015 during 8-10am PDT / 17:00-19:00 CEST ?


7. AOB and wrap up

Ramesh: I have a question: How should a EDM.Stream value be handled in ComplexType? I did not see any reference to that in specification?

Answer/discussion not minuted

Meeting adjourned