[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: RE: Agenda for OData TC meeting 2016-03-10 - Chat transcript
Please change your name from 'anonymous' using the Settings button Stefan: Voting Members: 3 of 13 (23%) (used for quorum calculation) Room information was updated by: Stefan Please register as usual at https://www.oasis-open.org/apps/org/workgroup/odata/event.php?event_id=41453
[17:02] anonymous morphed into Ralf Handl (SAP SE) [17:02] Room information was updated by: Stefan Please register as usual at https://www.oasis-open.org/apps/org/workgroup/odata/event.php?event_id=41453
Updated agenda: https://www.oasis-open.org/apps/org/workgroup/odata/email/archives/201603/msg00160.html
[17:02] Stefan: Updated Agenda at: https://www.oasis-open.org/apps/org/workgroup/odata/email/archives/201603/msg00160.html [17:03] Stefan: Voting Members: 7 of 13 (53%) (used for quorum calculation) [17:03] Stefan: We are quorate :-) [17:06] Ralf Handl (SAP SE): 2.Approve agenda [17:06] Ralf Handl (SAP SE): Agenda is approved [17:06] Ralf Handl (SAP SE): 3.Approve minutes from previous meeting(s) [17:06] Ralf Handl (SAP SE): https://www.oasis-open.org/apps/org/workgroup/odata/download.php/57676/latest/odata-meeting-122_on-20160302_03-F2F_minutes.html [17:08] Ralf Handl (SAP SE): Minutes are approved [17:08] Ralf Handl (SAP SE): 4.Review action items [Action item list: https://www.oasis-open.org/apps/org/workgroup/odata/members/action_items.php] a.Action items due
i.None
[17:08] Ralf Handl (SAP SE): 5.Errata 3 Issues [17:09] Ralf Handl (SAP SE): a.Review applications of Errata 3 issue resolutions (This is a carryover from previous meeting) i.Review application of ODATA-803 and ODATA-912
[17:10] Mike Pizzo1: I move we close ODATA-803 and ODATA-912 as applied. [17:10] Stefan: I second [17:11] Ralf Handl (SAP SE): ODATA-803 and ODATA-912 are CLOSED as applied [17:11] Ralf Handl (SAP SE): b.Approve Errata 03 docs for public review [17:11] Ralf Handl (SAP SE): i.Sample motion: I move that the TC approve OData version 4.0 Errata 03 Working Draft 01 and all associated artifacts packaged together in https://www.oasis-open.org/apps/org/workgroup/odata/download.php/57711/odata-v4.0-errata03-wd01-2016-03-10.zip as Errata Draft 03 to OData v4.0 OASIS Standard approved on 24 February 2014 and confirm that the errata corrections do not constitute Substantive Changes to the Standard. Further, I move that the TC approve submitting OData version 4.0 Errata 03 contained in https://www.oasis-open.org/apps/org/workgroup/odata/download.php/57711/odata-v4.0-errata03-wd01-2016-03-10.zip for 15 days of public review. ii.Sample motion: I move that the TC approve OData JSON Format version 4.0 Errata 03 Working Draft 01 and all associated artifacts packaged together in https://www.oasis-open.org/apps/org/workgroup/odata/download.php/57691/odata-v4.0-errata03-wd01-2016-03-03.zip as Errata Draft 03 to OData JSON Format v4.0 OASIS Standard approved on 24 February 2014 and confirm that the errata corrections do not constitute Substantive Changes to the Standard. Further, I move that the TC approve submitting OData JSON Format version 4.0 Errata 03 contained in in https://www.oasis-open.org/apps/org/workgroup/odata/download.php/57691/odata-v4.0-errata03-wd01-2016-03-03.zip for 15 days of public review.
[17:17] Ralf Handl (SAP SE): https://www.oasis-open.org/apps/org/workgroup/odata/download.php/57711/odata-v4.0-errata03-wd01-2016-03-10.zip [17:19] Ralf Handl (SAP SE): Errata 03 Core: https://www.oasis-open.org/apps/org/workgroup/odata/download.php/57717/odata-v4.0-errata03-wd01-2016-03-10.zip [17:20] Ralf Handl (SAP SE): https://www.oasis-open.org/apps/org/workgroup/odata/download.php/57718/odata-json-format-v4.0-errata03-wd01-2016-03-03.zip [17:27] Mike Pizzo1: i.I move that the TC approve OData version 4.0 Errata 03 Working Draft 01 and all associated artifacts packaged together in https://www.oasis-open.org/apps/org/workgroup/odata/download.php/57717/odata-v4.0-errata03-wd01-2016-03-10.zip as Errata Draft 03 to OData v4.0 OASIS Standard approved on 24 February 2014 and confirm that the errata corrections do not constitute Substantive Changes to the Standard. Further, I move that the TC approve submitting OData version 4.0 Errata 03 contained in https://www.oasis-open.org/apps/org/workgroup/odata/download.php/57717/odata-v4.0-errata03-wd01-2016-03-10.zip for 15 days of public review. [17:29] Mark Biamonte (Progress): I second [17:32] Ralf Handl (SAP SE): Motion passes [17:32] Mike Pizzo1: I move that the TC approve OData JSON Format version 4.0 Errata 03 Working Draft 01 and all associated artifacts packaged together in https://www.oasis-open.org/apps/org/workgroup/odata/download.php/57718/odata-json-format-v4.0-errata03-wd01-2016-03-03.zip as Errata Draft 03 to OData JSON Format v4.0 OASIS Standard approved on 24 February 2014 and confirm that the errata corrections do not constitute Substantive Changes to the Standard. Further, I move that the TC approve submitting OData JSON Format version 4.0 Errata 03 contained in in https://www.oasis-open.org/apps/org/workgroup/odata/download.php/57718/odata-json-format-v4.0-errata03-wd01-2016-03-03.zip for 15 days of public review [17:32] Stefan: I second [17:33] Ralf Handl (SAP SE): Motion passes [17:33] Ralf Handl (SAP SE): 6.V4.01 issues [17:34] Ralf Handl (SAP SE): a.Issues for V4.01_WD01 in New or Open state i.Set Operations
1.Review Revised Proposal
2.Address Issues
[17:34] Ralf Handl (SAP SE): a.ODATA-820 Allow indexing into collections b.ODATA-616 Allow POST to collections of complex and primitive types, and DELETE with $filter
c.ODATA-615 Allow PATCH and DELETE with $filter on collections to modify or delete all (and only) the matching entities
d.ODATA-876 Allow services to return contained entities inline for delta responses
e.ODATA-666 Define Deep Update and Deep Upsert operations
f.ODATA-613 Allow POST to entity sets using the delta-response
[17:37] Ralf Handl (SAP SE): a.ODATA-820 Allow indexing into collections [17:37] Ralf Handl (SAP SE): Proposal: 1)Introduce array collections [ODATA-820]
a.Define new term, "Ordered", to advertise that a collection has a stable order. If it is a collection of primitive or complex types it can be indexed by ordinal:
< Term Name="Ordered" Type="Core.Tag" DefaultValue="true" AppliesTo="Property,NavigationProperty,EntitySet,ReturnType">
< Annotation Term="Core.Description" String="Collection has a stable order. Ordered collections of primitive or complex types can be indexed by ordinal."/>
< /Term>
b.GET/PUT/PATCH/DELETE to the /{index} of an ordered collection of primitive or complex types retrieves/replaces/modifies/deletes just that item
i./index cannot be appended to collections of entities or non-ordered collections
ii.Index is zero-based ordinal and follows JSONPointer syntax: collection/index
c.Update section 7.1.5 of the CSDL spec to note that it is possible to have an ordered collection of complex types with navigation properties.
2) Define a new "PositionalInsert" term to advertise that a collection supports inserting at a given ordinal [ODATA-820]
<Term Name="PositionalInsert" Type="Core.Tag" Default="true" AppliesTo="Property, NavigationProperty, EntitySet">
<Annotation Term="Core.Description" String="Items can be inserted at a given ordinal index."/>
</Term>
b.For collections of entity, complex, or primitive types annotated with PositionalInsert, client may specify new ?$index= query parameter in POST request to collection to specify where the item is inserted [ODATA-820]
[17:45] Ralf Handl (SAP SE): Allow negative indexes in requests [17:45] Ralf Handl (SAP SE): Require non-negative indexes in responses/context URLs [17:46] Ralf Handl (SAP SE): Index -1 would be the last instance in the collection [17:46] Ralf Handl (SAP SE): This means GET Something/-1 returns the last instance [17:47] Ralf Handl (SAP SE): POST Something?$index=-1 would insert just before the last one because it identifies the last one and the insert always happens before the identified instance [17:51] Mike Pizzo1: 1)Introduce array collections [ODATA-820] a.Define new term, "Ordered", to advertise that a collection has a stable order. If it is a collection of primitive or complex types it can be indexed by ordinal:
< Term Name="Ordered" Type="Core.Tag" DefaultValue="true" AppliesTo="Property,NavigationProperty,EntitySet,ReturnType">
< Annotation Term="Core.Description" String="Collection has a stable order. Ordered collections of primitive or complex types can be indexed by ordinal."/>
< /Term>
b.GET/PUT/PATCH/DELETE to the /{index} of an ordered collection of primitive or complex types retrieves/replaces/modifies/deletes just that item
i./index cannot be appended to collections of entities or non-ordered collections
ii.Index is zero-based ordinal and follows JSONPointer syntax: collection/index
iii. Clients can specify a negative index to say "from the end" with -1 being the last entry. services must not specify a negative value for an index.
c.Update section 7.1.5 of the CSDL spec to note that it is possible to have an ordered collection of complex types with navigation properties.
2) Define a new "PositionalInsert" term to advertise that a collection supports inserting at a given ordinal [ODATA-820]
<Term Name="PositionalInsert" Type="Core.Tag" Default="true" AppliesTo="Property, NavigationProperty, EntitySet">
<Annotation Term="Core.Description" String="Items can be inserted at a given ordinal index."/>
</Term>
b.For collections of entity, complex, or primitive types annotated with PositionalInsert, client may specify new ?$index= query parameter in POST request to collection to specify the non-negative, zero-based ordinal position where the item is inserted [ODATA-820]
I. Clients can specify a negative index to say "from the end" with -1 being "insert before the last entry".
[17:53] Stefan: Sorry, hit the end call instead of the mute again button ... [17:54] Stefan: I am back in the voice loop ;-) [17:55] Gerald Krause (SAP): I move we resolve ODATA-820 as proposed. [17:55] Mike Pizzo1: I second [17:56] Ralf Handl (SAP SE): ODATA-820 is RESOLVED with the amended proposal [17:56] Ralf Handl (SAP SE): b.ODATA-616 Allow POST to collections of complex and primitive types, and DELETE with $filter [17:58] Ralf Handl (SAP SE): Proposal 1) POST of a single item to a collection of complex or primitive types adds that item to the collection (as it does today with entity types.)
2) POST of a collection of items to a collection of complex, primitive, or entity types inserts all of the items of the collection. [ODATA-616]
3)DELETE to any collection without a $filter clears the collection [ODATA-616]
[18:07] Mike Pizzo1: revised proposal: 1) POST of a single item to a collection of complex or primitive types adds that item to the collection (as it does today with entity types.). POST to an ordered collection adds to the end. /$index can be used to insert other locations in an ordered collection 2)DELETE to any collection without a $filter clears the collection [ODATA-616]
[18:09] Mike Pizzo1: 1) POST of a single item to a collection of complex or primitive types adds that item to the collection (as it does today with entity types.). POST to an ordered collection adds to the end. ?$index can be used to insert other locations in an ordered collection 2) DELETE to any collection without a $filter clears the collection [ODATA-616]
[18:10] Mike Pizzo1: I move we resolve ODATA-616 as proposed [18:10] Gerald Krause (SAP): I second [18:11] Ralf Handl (SAP SE): ODATA-616 is RESOLVED as proposed [18:11] Ralf Handl (SAP SE): c.ODATA-615 Allow PATCH and DELETE with $filter on collections to modify or delete all (and only) the matching entities [18:11] Ralf Handl (SAP SE): Proposal 1)DELETE to any collection with a $filter clause removes any element matching that filter. [ODATA-616], [ODATA-615]
a.$select, $orderby, $top, $skip are NOT expected to be supported
2)PUT against a collection of primitive/complex types takes a collection in the payload and replaces the entire collection. [ODATA-615]
a.PUT does not support $filter.
b.This is the existing 4.0 behavior
3)PUT is not supported against an entity collection [ODATA-615]
4)PATCH to any collection with a payload containing a single value updates each element in the collection [ODATA-615]
a.If $filter is present, applies patch to those items matching the $filter [ODATA-615]
5)PATCH to a collection of primitive or complex types with a collection payload is not supported [ODATA-615]
[18:13] Martin Zurmuehl SAP: I kind of deep delete [18:14] Martin Zurmuehl SAP: my microphone is broken [18:14] Martin Zurmuehl SAP: I like the idea [18:14] Martin Zurmuehl SAP: It shapes the delete request ... [18:17] Mike Pizzo1: revised proposal: 1)DELETE to any collection with a $filter clause removes any element matching that filter. [ODATA-616], [ODATA-615] a. $expand can be used to delete related entities (deep delete)
b. $select, $orderby, $top, $skip are NOT expected to be supported
2)PUT against a collection of primitive/complex types takes a collection in the payload and replaces the entire collection. [ODATA-615]
a.PUT does not support $filter.
b.This is the existing 4.0 behavior
3)PUT is not supported against an entity collection [ODATA-615]
4)PATCH to any collection with a payload containing a single instance updates each element in the collection [ODATA-615]
a.If $filter is present, applies patch to those items matching the $filter [ODATA-615]
5)PATCH to a collection of primitive or complex types with a collection payload is not supported [ODATA-615]
[18:20] Mike Pizzo1: Revised: [18:20] Mike Pizzo1: 1)DELETE to any collection with a $filter clause removes any element matching that filter. [ODATA-616], [ODATA-615] a. $expand can be used to delete related entities (deep delete)
b. $select, $orderby, $top, $skip are NOT expected to be supported
2)PUT against a collection of primitive/complex types takes a collection (format is same as for a GET on the collection) in the payload and replaces the entire collection. [ODATA-615] (all or nothing)
a.PUT does not support $filter.
b.This is the existing 4.0 behavior
3)PUT is not supported against an entity collection [ODATA-615]
4)PATCH to any collection with a payload containing a single instance updates each element in the collection [ODATA-615]
a.If $filter is present, applies patch to those items matching the $filter [ODATA-615]
5)PATCH to a collection of primitive or complex types with a collection payload is not supported [ODATA-615]
[18:21] Mike Pizzo1: I move we approve ODATA-615 as proposed. [18:21] Gerald Krause (SAP): I second. [18:22] Ralf Handl (SAP SE): ODATA-615 is RESOLVED as proposed [18:23] Ralf Handl (SAP SE): 10.Next meeting b.Thursday March 17, 2016
[18:24] Ralf Handl (SAP SE): Europeans: note that next meeting starts at 16:00 CET as USA has already switched to daylight saving time From: Handl, Ralf Changed link to Core Errata03 zip file – Part 1 with repaired table of contents Corrected sample motions – zip file now referenced twice From: odata@lists.oasis-open.org [mailto:odata@lists.oasis-open.org]
On Behalf Of Handl, Ralf Here [1] is a proposed agenda for the OData TC (Technical Committee) meeting
scheduled on Thursday March 10 during 8-10am Pacific Time. For additional information, such as dial-in details and chat room, refer to [2]. For TC timeline, see [3]. Feel free to suggest additions or modifications.
[1] Agenda
i. None
i. Review application of
ODATA-803 and
ODATA-912 and any other pending issues
i. Sample motion: I move that the TC approve OData version 4.0 Errata 03 Working Draft 01 and all associated artifacts packaged together in
https://www.oasis-open.org/apps/org/workgroup/odata/download.php/57711/odata-v4.0-errata03-wd01-2016-03-10.zip
as Errata Draft 03 to OData v4.0 OASIS Standard approved on 24 February 2014 and confirm that the errata corrections do not constitute Substantive Changes to the Standard. Further, I move that the
TC approve submitting OData version 4.0 Errata 03 contained in
https://www.oasis-open.org/apps/org/workgroup/odata/download.php/57711/odata-v4.0-errata03-wd01-2016-03-10.zip
for 15 days of public review.
ii. Sample motion: I move that the TC approve OData JSON Format version 4.0 Errata 03 Working Draft 01 and all associated artifacts packaged together in
https://www.oasis-open.org/apps/org/workgroup/odata/download.php/57691/odata-v4.0-errata03-wd01-2016-03-03.zip
as Errata Draft 03 to
OData JSON Format v4.0 OASIS Standard approved on 24 February 2014 and confirm that the errata corrections do not constitute Substantive Changes to the Standard. Further, I move that the TC approve submitting OData JSON Format version 4.0 Errata 03 contained
in in https://www.oasis-open.org/apps/org/workgroup/odata/download.php/57691/odata-v4.0-errata03-wd01-2016-03-03.zip
for 15 days of public review.
a.
Issues
for V4.01_WD01 in New or Open state
i. Set Operations
1.
Review Revised Proposal
2.
Address Issues
a.
ODATA-820
Allow indexing into collections
b.
ODATA-616
Allow POST to collections of complex and primitive types, and DELETE with $filter
c.
ODATA-615
Allow PATCH and DELETE with $filter on collections to modify or delete all (and only) the matching entities
d.
ODATA-876 Allow services to return contained entities inline for delta responses
e.
ODATA-666 Define Deep Update and Deep Upsert operations
f.
ODATA-613 Allow POST to entity sets using the delta-response
ii. New Query Capabilities
3.
ODATA-614 Allow $expand, $select, ... with POST/PATCH/PUT in combination with return=representation to specify the response shape
4.
ODATA-827 introduce $compute query option
iii. Enumerations
5.
ODATA-849 Add possibility for enumeration types to "extend" another enumeration type
6.
ODATA-494 Define inheritance for enumeration types
7.
ODATA-874 Allow Edm.String as underlying type for enumeration types
iv. Simplified Payload
8.
ODATA-818
Omit properties whose value is null or the $metadata-defined default value
9.
ODATA-809
Define non-message format for final response of async request
10.
ODATA-747Allow IEEE 754 constants [-]INF and NaN also for Edm.Decimal and integer types
v. OData protocol
11.
ODATA-480 $batch: remove restriction "within the same change set " for Content-ID referencing 7.
OData JSON CSDL [9:40am]
a.
Parked issues
i. ODATA-910:
Consider format that is tailored for programmatic access (public comment c201602e00002)
ii. ODATA-906 Consider how to specify an included namespace as a default in JSON CSDL
iii. ODATA-890 Specify how to get from a JSON message to a JSON schema for validating this
message
iv. ODATA-863 Represent Terms similar to Types
b.
Next steps
i. Discuss next steps for alignment with Swagger JSON schema
i. ODATA-905 Example 67: result row for USA, Sugar missing, Example 68: last total
should be 7
ii. ODATA-904 Example 55: clarify groupby in combination with relationships of instance
cardinality zero
iii. ODATA-909 ABNF for pathPrefix should also allow qualified ComplexTypeName
b.
Thursday March 17, 2016?
[2] References
[3] Timeline |
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]