OData TC meeting #112 Thursday Nov 05, 2015

Acting chair: Ralf

Chat transcript from room: odatatc
2015-11-05 0800-1000 PT

1. Roll call

1.1 Members present

        Gerald Krause (SAP SE)
        Hubert Heijkers (IBM)
        Ken Baclawski (Northeastern University)
        Mark Biamonte (Progress Software)
        Martin Zurmuehl (SAP SE) 
        Matthew Borges (SAP SE) a.k.a. Matt
        Michael Pizzo (Microsoft) a.k.a. Mike
        Ralf Handl (SAP SE) 
        Ramesh Reddy (Red Hat)
        Stefan Hagen (Individual)
        Susan Malaika (IBM)
        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 unchanged as published.

3. Approve minutes from previous meeting(s)

3.1 Minutes from October 29, 2015 TC meeting #111:


Minutes approved unchanged as published

4. Review action items

4.1 Action items due November 05, 2015


5. Extension for Data Aggregation

a.Result of electronic ballot https://www.oasis-open.org/apps/org/workgroup/odata/ballot.php?id=2877 [17:09] Ralf Handl (SAP): Vote passed with 100% Yes - Thanks!

6. Next Face-to-Face Meeting

6.1 When - First week February 2016, 01-05 does this work?

All discuss

All: Week February 29 - March 04

No objections

6.2 Where - Please Propose Locations

Ralf: Location suggested is Zurich, Switzerland

Stefan: seconds this

Ralf: I like Zurich

Mike: That works for me.

Mark: If I can lobby my company to come this week and location would work for me.

No objections

Ralf: Action Item for Hubert: "Check if IBM can host the F2F in Zurich, Vulkanstrasse" (Due date: November 19)

6.3 What

6.3.1 Finish CSD01 for JSON CSDL

No objections

6.3.2 Get agreement on scope and shape of V4.01

No objections

6.3.3 Prepare respective draft documents

No objections

7. JSON Format for CSDL

7.1 Walk through current document revision

7.1.1 Specification document: odata-json-csdl-v4.0-wd01-2015-10-23.docx


7.1.2 EDM JSON Schema: edm.json


7.2 Issues for JSON Format for CSDL in Applied state

  1. ODATA-841 - Representation of Precision and Scale
  2. ODATA-855 - Should we define patterns for some of the primitive types
  3. ODATA-856 - Add annotations for Min/Max/Pattern
  4. ODATA-858 - Define meaning of MaxLength for String, Binary, and Stream
  5. ODATA-864 - Translate @Core.Description annotations into JSON Schema description keywords
7.2.1 Discussion:

Mike to open a ticket on whether to always use arrays for action/function overloads

Hubert: always use an array, no special case for 1-element arrays

Mark and Ralf second

Ralf to open an issue to pull out entityContainer, actions, functions, and terms to top-level keywords

Ralf: Resume walk-through in next meeting, we stopped just before "4.2.5 Annotations"

Hubert: I move to resolve ODATA-841, ODATA-855, ODATA-858 and ODATA-864 as applied. Ted seconds.

Ralf: Motion passes

Ralf to check whether the document still contains plain untranslated @Core.Description

8. V4.0 ERRATA03

8.1 Issues for V4.0_ERRATA03 in New or Open state

8.1.1 OData JSON Format ODATA-828 - Update I-JSON reference

Mike: Revised Wording:The DateTimeOffset and TimeOfDay data types as defined in [OData-ABNF] allow for the seconds component to be omitted. For compatibility with [I-JSON], OData clients and servers SHOULD include the seconds component.

Mike: I move we resolve ODATA-828 according to this revised proposal. Hubert seconds.

ODATA-828 is resolved with the amended proposal

8.1.2 OData Protocol ODATA-877 - Must delta responses continue to track "orphaned" entities?

Mike: Proposed wording for ODATA-877:
If a previously tracked related entity is orphaned because all paths to the entity as specified in the defining query have been broken (i.e., due to relationship changes and/or changes or deletions to parent entities) then the service MUST return the appropriate notifications for the client to determine that the entity has been orphaned (i.e., the changed relationships and removed parent entities) but the client should not assume that it will receive additional notifications for such an orphaned entity.

Hubert: I move to resolve ODATA-877 as proposed. Matt seconds.

ODATA-877 is resolved as proposed

9. V4.01

9.1 Issues for V4.01_WD01 in New or Open state

9.1.1 Enum Types
  1. Proposal by Ken Baclawski: https://www.oasis-open.org/committees/download.php/56805/DerivationForEnumerations_KenBaclawski.html
  2. ODATA-494 - Define inheritance for enumeration types
  3. ODATA-849 - Add possibility for enumeration types to "extend" another enumeration type


<EnumType Name="ExtendedShippingMethod" Widens="ShippingMethod">
  <Member Name="Economy"/>

10. Next meeting

10.1 Thursday November 12, 2015 during 8-10am PT?

Ted: I will be at TechEd next week

Date and time of next meeting agreed

11. AOB and wrap up

Meeting adjourned by chair.