OData TC meeting #85 Thursday Nov 13, 2014

Acting chair: Ram

Chat transcript from room: odatatc
2014-11-13 0800-1000 PDT

1. Roll call

1.1 Members present

        Edmond Bourne (BlackBerry)
        Gerald Krause (SAP AG)
        Hubert Heijkers (IBM)
        Jason Fam (IBM)
        John Willson (Individual)
        Ken Baclawski (Northeastern University)
        Martin Zurmuehl (SAP AG)
        Matthew Borges (SAP AG) a.k.a. Matt 
        Michael Pizzo (Microsoft) a.k.a. Mike
        Ralf Handl (SAP AG)
        Ram Jeyaraman (Microsoft)
        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 October 30, 2014 TC meeting:

Meeting#84 on 2014-OCT-30

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 November 13, 2014

None

5. Process issues

5.1 ODATA-733 "Specify navigation property binding combined with containment"

Ralf: Clarify handling of cycles in Extends for EntityContainers

Mike: services should not do this, clients should stop once they encounter a service again

Mike: DMTF is defining a "core" service with entity sets that each service has to support

Mike: proposes "Services should not introduce cycles in Extends. Clients must be prepared to process cycles in Extends."

Mike: I move we resolve ODATA-733 as proposed.

Hubert seconds

Motion passes, no objections

5.2 ODATA-734 "Unicode Facet is inadequate"

ODATA-734 is open

Mike to record the discussion in Jira

John: also investigate UTF-8 vs UTF-16

5.3 ODATA-735 "Enhance the CSDL for instance annotations"

ODATA-735 is open

John: maybe a session attribute defining language coding for session

Mike: would need to extend the CSDL schema, so no candidate for Errata03

Mike: I move we move this issue to OData 4.1 release.

Matt seconds

Motion passes

5.4 ODATA-742 "Usage of domain contoso.com and term name contoso in examples"

Martin: The edm:Term element MAY define a value for the AppliesTo attribute. The value of this attribute is a whitespace-separated list of CSDL element names that this term is intended to be applied to. If no value is supplied, the term is not intended to be restricted in its application. As the intended usage may evolve over time, clients SHOULD be prepared for any annotation to be applied to any element

Martin: leftover of editing

Mike: let's change it

ODATA-742 is open

Martin: I move we resolve ODATA-742 and remove references to contoso in the documents

Stefan seconds

Motion passes

5.5 ODATA-746 "12.2.3: IsComposable - clarify what is allowed even if set to false"

Mike explains background: stored procedures vs table-valued functions

Martin: If no value is specified for the IsComposable attribute, the value defaults to false. "Functions whose IsComposable attribute is true are considered composable. A composable function can be invoked with additional path segments or system query options appended to the path that identifies the composable function as appropriate for the type returned by the composable function."

Mike: if there's a generic implementation that post-processes the result the server can set IsComposable to true

ODATA-746 is open

Mike: I move we resolve ODATA-746 by clarifying that IsComposable restricts further query refinement through segments, key lookup, or query options.

Martin seconds

Motion passes

5.6 ODATA-745 "Sections 4.5.5, 7.3, and 7.4: is odata.nextLink allowed for all collections?"

Mike: there might be a JIRA ticket for this documenting the discussion and decision

ODATA-745 is open

5.7 ODATA-749 "What should service return when attempting to related two entities that are already related?"

ODATA-749 is open

Hubert: I more to resolve ODATA-749 as proposed.

Mike seconds

Motion passes

5.8 ODATA-731 "Explicitly state that JSON service documents may contain annotations"

ODATA-731 is open

Mike: I move we resolve ODATA-731 by saying that Any JSON object and name-value pair can be annotated, including the service document. Dynamic properties are not allowed in the service document.

Hubert seconds

Motion passes

Martin: Added "https://issues.oasis-open.org/browse/ODATA-519 "Define server-driven paging for collection-valued resources"" to ODATA-745

6. JSON representation for metadata

All walk through the document

Ram: public comments via the comments mailing list are fine

send mail to: odata-comment@lists.oasis-open.org

7. Next meeting

Next week: 2014-11-20 8:00-10:00am PT

Agreed

8. AOB

None.

Meeting adjourned at 10:00 PDT