OData TC meeting #89 Thursday Jan 15, 2015

Acting chair: Ram

Chat transcript from room: odatatc
2015-01-15 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 Drees (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 as published.

3. Approve minutes from previous meeting(s)

3.1 Minutes from January 08, 2015 TC meeting:

Meeting#88 on 2015-JAN-08

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 January 15, 2015

None

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

5.1 OData Protocol

5.1.1 ODATA-479 "Allow Content-ID referencing in request bodies for inserting links to newly created entities"

Ralf: We are probably safe: ids are URIs, and unless they contain a colon they are relative to the request. We've reserved $ for top-level resources, so $1 should be ok.

Ralf: To be verified

Ralf: Postpone this issue to next meeting

5.1.2 ODATA-765 "Example 77 (invoking an action): show complex parameters"

Ralf: ODATA-765 is OPEN

Ralf:

POST http://host/service/Customers('ALFKI')/SampleEntities.CreateOrder 

 { 
    "items":[ 
       {"product":4001, "quantity":2}, 
       {"product":7062, "quantity":1} 
    ], 
    "discountCode": "BLACKFRIDAY" 
 }
 

Current text:

POST http://host/service/Customers('ALFKI')/SampleEntities.CreateOrder

{
   "quantity": 2,
   "discountCode": "BLACKFRIDAY"
}
 

Mike: Current example description: Example 77: invoke the SampleEntities.CreateOrder action using /Customers('ALFKI') as the customer (or binding parameter). The values 2 for the quantity parameter and BLACKFRIDAY for the discountCode parameter are passed in the body of the request
New second sentence: The values for the items and and discountCode parameters are passed in the body of the request.
The items parameter value is an array of complex type instances, the discountCode parameter value is a string.

Mike: Added the following text to the proposal. Also modify description of example appropriately:
Example 77: invoke the SampleEntities.CreateOrder action using /Customers('ALFKI') as the customer (or binding parameter). The values for the items and and discountCode parameters are passed in the body of the request. The items parameter value is an array of complex type instances, the discountCode parameter value is a string.

Martin: I move to resolve ODATA-765 as proposed in the jira ticket. Hubert seconds

ODATA-765 is resolved as proposed

5.1.3 ODATA-766 "8.2.4 and 8.2.5 should refer to RFC7232 (public comment c201501e00001)"

Ralf: ODATA-766 is OPEN

Ralf: Check all references to RFC7230 whether they are really refering the correct part

Postponed to next meeting

5.1.4 ODATA-767 "Adapt Acknowledgements"

Ralf: ODATA-767 is OPEN

Ralf: Proposal: keep this issue open until next Errata are published, then add missing people to the Acknowledgement section

5.1.5 ODATA-768 "Remove superfluous text after references"

Ralf: An OData service MUST support at least one of [OData-JSON]ODataJSONRefOData-JSON or [OData-Atom]OData-Atom, and MAY support additional formats for both request and response bodies.

Ralf: ODATA-768 is OPEN

Martin and Ralf to check whether this error pattern appears in other places

Postponed to next meeting

5.1.6 ODATA-769 "5.2 Model Versioning: allow adding a new term to the model"

Ralf: ODATA-769 is OPEN

Martin: I move to resolve ODATA-769 as proposed. Mike seconds

ODATA-769 is resolved as proposed

6. OData JSON Format for Common Schema Definition Language (CSDL)

Mike to check with JSON Schema authors whether they plan to focus on validation only or whether they want to cover modeling in addition

Mike to check with JSON Schema authors on timeline for standardization

John: Liked the discussion. Could use a diagram. Liked the modeling extension approach o JSON.

Ralf: In the mean-time: experiment with redundant OData-specific extensions, and introduce predefined Nullable-variants for Edm types in edm.json

Mike: Consider an annotation that tells clients not to expect additional properties

Mike will open a Jira issue

Mike: Let's prepare an example of how a metadata file would look with the current JSON Schema, and a variant showing how we want it to look with "modeling extension"

Ralf: https://tools.oasis-open.org/version-control/browse/wsvn/odata/trunk/spec/examples/#_trunk_spec_examples_

Mike: we can extend OData 4.0 compatibly by only using the specific media type application/schema+json and reserving the plain application/json for the future

7. Next meeting

Suggested is 2015-FEB-05 8:00-10:00am PT

Agreed

8. AOB

None.

Meeting adjourned at 09:25 PT