Acting chair: Ralf
Chat transcript from room: odatatc 2015-11-05 0800-1000 PT
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.
Agenda approved unchanged as published.
Minutes approved unchanged as published
All: Week February 29 - March 04
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.
Ralf: Action Item for Hubert: "Check if IBM can host the F2F in Zurich, Vulkanstrasse" (Due date: November 19)
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
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
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
<EnumType Name="ExtendedShippingMethod" Widens="ShippingMethod"> <Member Name="Economy"/> </EnumType>
Ted: I will be at TechEd next week
Date and time of next meeting agreed
Meeting adjourned by chair.