RE: [odata] Agenda for OData TC meeting on 2015-04-16

Room information was updated by: Stefan

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

Stefan: @All: Voting Members: 1 of 15 (6%) (used for quorum calculation)

Stefan: @Chair: Please send chat transcript after meeting to odata-list and/or scribe/secretary mail address, so I can assemble the minutes after the meeting and upload to kavi. Thanks.

Ralf Handl (SAP): Will do!

Ralf Handl (SAP): Voting Members: 8 of 15 (53%) (used for quorum calculation)

rareddy morphed into Ramesh Reddy(Redhat)

Stefan: @Ralf: Thanks a bunch. I do have connectivity problems on the move, will try to join via voice line later.

anonymous morphed into Matt Borges (SAP)

Ralf Handl (SAP): 2.Approve agenda

Ralf Handl (SAP): Agenda is approved

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

Ralf Handl (SAP): Minutes are approved

Ralf Handl (SAP): 4.Review action items

Ralf Handl (SAP): None

Ralf Handl (SAP): 5.Process issues

Ralf Handl (SAP): a.Issues for V4.0_ERRATA03 in New or Open state

Ralf Handl (SAP): i.OData CSDL

Ralf Handl (SAP): 1.ODATA-801           Consider supporting negative scale for decimal type

Ralf Handl (SAP): ODATA-801 is OPEN

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

Ralf Handl (SAP): Mark will look into this

Ralf Handl (SAP): Defer to future meeting

Ralf Handl (SAP): Discuss together with other issues on Edm.Decimal: ODATA-771, ODATA-804

Ralf Handl (SAP): 2.ODATA-803           Collection-valued property: Define default value for nullable facet

Ralf Handl (SAP): Mike: if Nullable facet is missing clients SHOULD expect that the collection may contain null values

Ralf Handl (SAP): Mike: what do current implementations do?

Ralf Handl (SAP): Ramesh to look into Olingo implementation

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

Ralf Handl (SAP): { "value":[1,null,3] }

Ralf Handl (SAP): ODATA-803 is OPEN

Martin Zurmuehl: The edmroperty element MAY contain the Nullable attribute whose Boolean value specifies whether a value is required for the property.

Mike Pizzo: 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 Heijkers: I second

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

Ralf Handl (SAP): ii.OData JSON Format

Ralf Handl (SAP): 1.ODATA-771           Exponential notation for Edm.Decimal values in JSON payloads

Ralf Handl (SAP): Hubert proposes F2F in Hawaii between August 04 and August 17

Ralf Handl (SAP): Defer issue to future meeting

Ralf Handl (SAP): iii.OData Protocol

Ralf Handl (SAP): 1.ODATA-791           11.2.5.2 System Query Option $orderby: specify order of Edm.Boolean and Edm.Geo

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

Martin Zurmuehl: I second

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

Ralf Handl (SAP): iv.OData Vocabularies

Ralf Handl (SAP): 1.ODATA-802           Define a vocabulary for odata.* annotations

Ralf Handl (SAP): Mike: odata.* is special for JSON, the same meta information would not be represented as annotations in Atom

Ralf Handl (SAP): Mike: if we make it a vocabulary, even in the context of the JSON Format specification, it may get used in $metadata

Ralf Handl (SAP): ODATA-802 is OPEN

Ralf Handl (SAP): Matt: it seems odd that information is represented in JSON as annotations and differently in other formats

Matt Borges (SAP): I move to close ODATA-802 without action

Mike Pizzo: I second.

Mark Biamonte (Progress): I second

Ralf Handl (SAP): ODATA-802 is closed without action

Ralf Handl (SAP): 6.Next meeting

Ralf Handl (SAP): a.Thursday April 23, 2015 during 8-10am PT?

Ralf Handl (SAP): b.Thursday April 30, 2015 during 8-10am PT?

Ralf Handl (SAP): Next meeting Thursday April 30, 2015 during 8-10am PT

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

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

Matt Borges (SAP): I need to drop off for another meeting

From: odata@lists.oasis-open.org [mailto:odata@lists.oasis-open.org] On Behalf Of Handl, Ralf
Sent: Dienstag, 14. April 2015 16:15
To: odata@lists.oasis-open.org
Subject: [odata] Agenda for OData TC meeting on 2015-04-16

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

2. Approve agenda [8:05am PT]

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

a. Minutes from March 26, 2015 TC meeting: https://www.oasis-open.org/committees/download.php/55436/odata-meeting-94_on-20150326-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 V4.0_ERRATA03 in New or Open state