OData TC meeting #110 Thursday Oct 22, 2015

Acting chair: Ralf

Chat transcript from room: odatatc
2015-10-22 0800-1000 PDT

1. Roll call

1.1 Members present

        Hubert Heijkers (IBM)
        Ken Baclawski (Northeastern University)
        Mark Biamonte (Progress Software)
        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)
        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 October 15, 2015 TC meeting #109:


Minutes approved unchanged as published

4. Review action items

4.1 Action items due October 22, 2015


5. Extension for Data Aggregation

5.1 Review documents

5.1.1 Specification document:
5.1.2 Summary of changes:
5.1.3 ABNF Changes:
5.1.4 ABNF Testcases:
5.1.5 Misc.

All walk through the documents via shared live session.

5.2 Issues for Data Aggregation in Applied state

  1. ODATA-833 - Example 40 applies term RecursiveHierarchy term incorrectly
  2. ODATA-851 - groupby(): ABNF still allows more than two parameters
  3. ODATA-857 - Example 5: use two aggregate expressions
  4. ODATA-860 - Move definition of Custom Aggregation Method to separate subsection.
  5. ODATA-866 - 3.14 Transformation compute: add reference to numeric promotion rules
  6. ODATA-871 - Clarify odata.type for Compute and Aggregate

Mark: I move that we close ODATA-833, ODATA-851, ODATA-857, ODATA-860, ODATA-866 and ODATA-871 as applied. Ramesh seconds.

ODATA-833, ODATA-851, ODATA-857, ODATA-860, ODATA-866 and ODATA-871 are CLOSED as applied

5.3 Review zip file

5.3.1 https://www.oasis-open.org/committees/download.php/56706/odata-data-aggregation-ext-v4.0-wd04-2015-10-16.zip

Ramesh: btw, how are the test cases executed?

Mark: I have verified that the zip file contains the following documents
Mark Biamonte (Progress): odata-data-aggregation-ext-v4.0-wd04-2015-10-16-redlined.docx

Mark: I opened each document and verified that the odata-data-aggregation-ext-v4.0-wd04-2015-10-16-redlined.docx document had the changes just discussed

5.4 Approve CSD03 with non-material changes to CS02

Ramesh: I move to approve the Chair requesting that TC Administration hold a Special Majority Vote to approve OData Extension for Data Aggregation Version 4.0 Working Draft 04 contained in https://www.oasis-open.org/committees/download.php/56706/odata-data-aggregation-ext-v4.0-wd04-2015-10-16.zip as a Committee Specification. I further move that the TC affirm that changes have been made since the last public review, that the changes made are documented in https://www.oasis-open.org/committees/download.php/56707/odata-data-aggregation%20CSD03%20Summary%20of%20Non-Material%20Changes%202015-10-16-final.docx and that the TC judges these changes to be Non-Material in accordance with the definition in the OASIS TC Process (http://www.oasis-open.org/policies-guidelines/tc-process#dNonmaterialChange). Ted seconds.

Motion passes

6. JSON Format for CSDL

6.1 Issues for JSON Format for CSDL in New or Open state

6.1.1 ODATA-872- Consider defining structure of bound actions/functions

Ralf: ODATA-872 is OPEN

6.2 Review documents

6.2.1 Specification document:
6.2.2 EDM JSON Schema:

6.3 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
6.3.1 Discussion

Ralf: Example 7: split up into seperate examples

Mark: add multiple variants for different combinations of facets

Ralf: Example 24: incorrect representation of actions and functions

Ralf: Action and function representation objects MUST have a "parameters" member, which MAY be empty

Ralf: Change examples to use different names for binding parameters, and avoid the name "in"

Ralf: Document order of parameters is significant: switch to array representation with objects {name:string, type:{$ref or primitive}}

Ralf: Use similar representation as Swagger, i.e. "type":"string","format":"decimal" for primitive types

Ralf: Mike to open an issue for representation of CSDL references as strings (with OData semantics) or JSON References. Research into use of JSON References as true references and not just as "macro expansion". WD01 as affected/fix version

Ralf: Section 4.2.4: definition doesn't match current representation depicted in example

Ralf: Annotations without explicit value in XML: don't do that in JSON Schema, just explicitly repeat the default value from the term definition

7. Next meeting

7.1 Thursday October 29, 2015 during 8-10am PT?


8. AOB and wrap up

Ralf: Use Ralf's Adobe Connect from now on for meetings.

Meeting adjourned by chair.