Acting chair: Ram
Chat transcript from room: odatatc 2016-06-02 0800-1000 PDT
Gerald Krause (SAP SE)
Hubert Heijkers (IBM)
Ken Baclawski (Northeastern University)
Martin Zurmuehl (SAP SE)
Matthew Borges (SAP SE) a.k.a. Matt
Michael Pizzo (Microsoft) a.k.a. Mike
Ralf Handl (SAP SE)
Ram Jeyaraman (Microsoft)
Ramesh Reddy (Red Hat)
Stefan Hagen (Individual)
Susan Malaika (IBM)
Ted Jones (Red Hat)
Quorum achieved. Details cf. normative attendance sheet for this meeting (event_id=41465).
Notes taken by all and subsequently edited for readability by Stefan.
Agenda approved unchanged as published.
Minutes approved unchanged as published.
https://www.oasis-open.org/committees/download.php/58164/odata-meeting-130_on-20160512-minutes.html
Minutes approved unchanged as published.
Minutes approved unchanged as published.
Hubert: I move to approve requesting OASIS to set up two OASIS Open Repos as documented in the https://lists.oasis-open.org/archives/odata/201606/msg00004.html with the specific GitHub names for the Repos as "OData-OpenAPI" and "OData-Vocabularies" and correct email addresses for the maintainers. Amended by Ram: as: Person 1: Ralf Handl, ralf.handl@sap.com, ralfhandl, SAP SE; Person 2 Mike Pizzo, mikep@microsoft.com, mikepizzo, Microsoft. Amended by Ralf with main URL https://github.com/oasis-open. Ramesh seconds the motion as amended by Ram and Ralf.
Ram: No objections, motion passes.
Ram: The chairs will request the TC admin to setup the repos.
Ram: Action #0035 closed, no objections
Ram: Action #0036 remains open
Public review comment resolution log at https://lists.oasis-open.org/archives/odata/201605/msg00033.html
Martin: example: link to edm.property element:
http://docs.oasis-open.org/odata/odata/v4.0/errata02/os/complete/part3-csdl/odata-v4.0-errata02-os-part3-csdl-complete.html#_Toc406397951
http://docs.oasis-open.org/odata/odata/v4.0/errata02/os/complete/part3-csdl/odata-v4.0-errata02-os-part3-csdl-complete.html#elementEdmProperty
Mike: Link for the Core V4 errata 3: https://www.oasis-open.org/apps/org/workgroup/odata/download.php/58175/odata-v4.0-errata03-wd02-2016-05-18.zip
Mike: Link JSON V4 errata 3: https://www.oasis-open.org/apps/org/workgroup/odata/download.php/58170/odata-json-format-v4.0-errata03-wd01-2016-05-18.zip
Mike: I move that the TC approve OData version 4.0 Errata 03 Working Draft 02 and all associated artifacts packaged together in https://www.oasis-open.org/apps/org/workgroup/odata/download.php/58175/odata-v4.0-errata03-wd02-2016-05-18.zip as an Approved Errata and make it available with OData version 4.0 OASIS Standard. Further, I confirm that the errata corrections do not constitute Substantive Changes to the Standard. Ralf seconds.
Ram: motion passes, no objections
Ralf: I move that the TC approve OData JSON Format version 4.0 Errata 03 Working Draft 02 and all associated artifacts packaged together in https://www.oasis-open.org/apps/org/workgroup/odata/download.php/58170/odata-json-format-v4.0-errata03-wd01-2016-05-18.zip as an Approved Errata and make it available with OData JSON Format version 4.0 OASIS Standard. Further, I confirm that the errata corrections do not constitute Substantive Changes to the Standard. Martin seconds.
Ram: motion passes, no objections
Ram will submit request to publish the approved errata with all six levels in the Table of Contents.
All reviewed the application of the resolutions
Martin: I move to close issues ODATA-936, ODATA-932, ODATA-931, ODATA-930, and ODATA-934 as applied. Mark seconds.
Ram: Motion passes, no objections.
Ram: No objections to reopening the issue and the previously approved resolution to add a clarification proposed by Mike.
Mike: I move we resolve ODATA-937 as proposed, with the additional proposal that we not add the OData prefix to new headers, preferences, and format parameters added in 4.01 and beyond that have a generic meaning (in particular, omit-values and SchemaVersion). Martin seconds.
Ram: motion passes, no objections
Ram: ODATA-941 is open, no objections
Mike: Specify that services should error if an insert or update contains a property for which the user doesn't have permission to update, and the value of the property does not match the value specified by the user.
Updating a specific property (identified as the target of the update URL) should fail if the user does not have permission to that property.
Mike: Working proposal: Clarify that "non-updatable" in 11.4.3, Update an Entity, means "marked as computed or read-only in metadata".
Specify that services should error if an insert or update contains an updatable property that cannot be changed by this user at this time (i.e., given the current state of the object, or for which the user doesn't have permission to update), and the value of the property does not match the value specified by the user. In this case, the service MAY return an error even if the property does match the value specified by the user.
As a result, clients should use PATCH and only specify the properties that they want to change.
Updating a specific property (identified as the target of the update URL) should fail if the property is not updatable.
Mike: I move we resolve ODATA-941 as proposed. Martin seconds.
Ram: motion passes, no objections
Agreed
Ram: We will have a longer meeting from 6am-10am PT on June 23rd.
None.
Meeting adjourned by chair.