[7:43] Room information was updated by: Stefan
Please register as usual at: https://www.oasis-open.org/apps/org/workgroup/odata/event.php?event_id=41455
Agenda draft at (Mail from Ram): https://www.oasis-open.org/apps/org/workgroup/odata/email/archives/201603/msg00220.html
[7:49] Stefan: Voting Members: 1 of 13 (7%) (used for quorum calculation)
[7:56] anonymous111 asked for a victim, I choose... anonymous1
[7:56] anonymous111111 asks: null
Magic 8-Ball says: Reply hazy, try again
[7:56] anonymous2111 asked for a victim, I choose... anonymous211
[7:56] anonymous2111111 asks: null
Magic 8-Ball says: It is decidedly so
[7:56] anonymous3111 asked for a victim, I choose... anonymous111
[7:56] anonymous3111111 asks: null
Magic 8-Ball says: Outlook not so good
Room Information:
Please register as usual at: https://www.oasis-open.org/apps/org/workgroup/odata/event.php?event_id=41455
Agenda draft at (Mail from Ram): https://www.oasis-open.org/apps/org/workgroup/odata/email/archives/201603/msg00220.html
[8:06] Stefan: Voting Members: 10 of 13 (76%) (used for quorum calculation)
[8:10] Ram (Microsoft): minutes from March 17 approved, no corrections, no objections.
[8:11] Ram (Microsoft): Agenda (revised) with ODATA-926 added, approved. No other corrections.
[8:11] Ram (Microsoft): Action item discussion: Hubert - we need to discuss about "Securing OData" AI#0029: https://www.oasis-open.org/apps/org/workgroup/odata/members/action_item.php?action_item_id=3638
[8:14] Ram (Microsoft): SASL mechanism: http://www.ietf.org/rfc/rfc4422.txt
[8:17] Hubert Heijkers: Apparently integration of SAML for SASL has been defined already here: https://tools.ietf.org/html/rfc6595
[8:18] Ram (Microsoft): Issues discussion
[8:18] Ram (Microsoft): ODATA-922 Support DELETE/PUT to $ref of a collection-valued nav prop to remove/replace all links
[8:19] Ram (Microsoft): Issue open, no objections
[8:25] Mike Pizzo: For containment, the specified links would have to already be in the collection; any links not in the collection would be removed (and, because it's containment, deleted).
[8:26] Mike Pizzo: I move we approve ODATA-922 as proposed.
[8:27] Ramesh Reddy(RedHat): I second
[8:29] Ram (Microsoft): No objections, ODATA-922 resolved as proposed.
[8:29] Ram (Microsoft): ODATA-924: Define semantics for PUT against a single entity with nested content
[8:32] Ramesh Reddy(RedHat): I have conflict in meeting schedule, I join again after
[8:55] Mike Pizzo: Discussion: Semantics should align with POST;
1) You can include references (only) to existing entities (no content)
2) The end result of the PUT is that the existing (references) and new (entities) are the full set of entities related according to that relationship.
[8:57] Mike Pizzo: Define that, when you do a PUT,
1) You can include new entities and references to existing entities, but not content for existing entities
2) The end result of the PUT is that the existing (references) and new (entities) are the full set of entities related according to that relationship.
[8:58] Ram (Microsoft): ODATA-924 is open, no objections
[8:58] Mike Pizzo: I move we resolve ODATA-924 as proposed
[8:58] Mark Biamonte (Progress): I second
[8:59] Ram (Microsoft): No objections, issue resolved as proposed.
[8:59] Mike Pizzo: new related issue: https://issues.oasis-open.org/browse/ODATA-927, Explicitly disallow existing nested items in Deep Insert
[9:01] Mike Pizzo: Copied proposal from PUT:
[9:01] Mike Pizzo: Clarify that, when doing a POST:
1) You can include new entities and references to existing entities, but not content for existing entities
2) The end result of the POST is that the existing (references) and new (entities) are the full set of entities related according to that relationship.
[9:01] Ram (Microsoft): issue is now open, no objections.
[9:10] Ram (Microsoft): Related issue, ODATA-876. See for reference
[9:36] Matt Borges (SAP): https://issues.oasis-open.org/browse/ODATA-873
[9:37] Mike Pizzo: Back to ODATA-927:
[9:37] Mike Pizzo: Clarify that, when doing a POST:
1) You can include new entities and references to existing entities, but not content for existing entities
2) The end result of the POST is that the existing (references) and new (entities) are the full set of entities related according to that relationship.
[9:38] Mike Pizzo: I move we resolved ODATA-927 as proposed.
[9:39] Matt Borges (SAP): I second
[9:40] Ram (Microsoft): No objections, issue resolved.
[9:41] Ram (Microsoft): Back to ODATA-924
[9:42] Ram (Microsoft): No objection to opening the discussion on the proposal for ODATA-924.
[9:42] Ram (Microsoft): The intention is to revise the previous resolution.
[9:42] Mike Pizzo: Revised proposal to align with PATCH (as per ODATA-876)
[9:42] Mike Pizzo: Define that, when you do a PUT,
1) You can include new entities, existing entities, and references to existing entities
2) Existing entities are updated using PUT semantics
a) entities to be updated must have either @odata.id or key fields, otherwise interpreted as an insert
3) The end result of the PUT is that the specified entities and entity references are the full set of entities related according to that relationship.
[9:50] Ram (Microsoft): Sample motion (for revising the previously approved proposal to ODATA-924): I move to revise the previously approved resolution to ODATA-924 as described in the revised proposal.
[9:50] Ralf Handl (SAP): From 11.4.3: Key and other non-updatable properties, as well as dependent properties that are not tied to key properties of the principal entity, can be omitted from the request. If the request contains a value for one of these properties, the service MUST ignore that value when applying the update.
[9:50] Ram (Microsoft): Note, this motion requires unanimity.
[9:52] Mike Pizzo: Revised proposal for ODATA-924, to align with previously approved ODATA-876:
[9:52] Mike Pizzo: Align Semantics of PUT with PATCH, as specified in ODATA-876, by specifying that, when you do a PUT,
1) You can include new nested entities, existing entities, and references to existing entities
2) Existing entities are updated using PUT semantics
a) entities to be updated must have either @odata.id or key fields, otherwise interpreted as an insert
b) if @odata.id and key fields both exist but don't match, then request is invalid
3) The end result of the PUT is that the specified entities and entity references are the full set of entities related according to that relationship.
[9:53] Mike Pizzo: I move to revise the previously approved resolution to ODATA-924 as described in the revised proposal.
[9:53] Matt Borges (SAP): I second
[9:56] Ram (Microsoft): No objections, the motion passes with unanimous support.
[9:56] Ram (Microsoft): Next meeting: Next week same time.
[9:56] Ram (Microsoft): Meeting adjourned.
From: odata@lists.oasis-open.org [mailto:odata@lists.oasis-open.org]
On Behalf Of Ram Jeyaraman
Sent: March 24, 2016 7:56 AM
To: odata@lists.oasis-open.org
Subject: [odata] RE: Agenda for OData TC meeting 2016-03-24
One correction: Add
ODATA-926 (OData should not require 202 response to be empty) to section 5.a.v.
Here [1] is the agenda for the OData TC (Technical Committee) meeting
scheduled on Thursday March 24, 2016 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.
Thanks.
[1] Agenda
- Roll call [8:00am]
- Self-registration link:
https://www.oasis-open.org/apps/org/workgroup/odata/event.php?event_id=41455
- Approve agenda [8:05am]
- Approve minutes from previous meeting(s) [8:10am]
- Minutes from March 17, 2016 TC meeting:
https://www.oasis-open.org/apps/org/workgroup/odata/download.php/57790/odata-meeting-124_on-20160317-minutes.html
- Review action items [Action item list:
https://www.oasis-open.org/apps/org/workgroup/odata/members/action_items.php] [8:15am]
- Action items due
i. #0032:
Overview presentation on HTTP/2 features (due May 19, 2016)
ii. #0035:
Identify the right open source license for the OASIS Open Source repositories for vocabularies and libraries (due March 31, 2016)
- V4.01 issues [8:20am]
a.
Issues
for V4.01_WD01 in New or Open state
i. Set Operations
1.
ODATA-922
Support DELETE/PUT to $ref of a collection-valued nav prop to remove/replace all links
2.
ODATA-924:
Define semantics for PUT against a single entity with nested content
ii. New Query Capabilities
1.
ODATA-614 Allow $expand, $select, ... with POST/PATCH/PUT in combination with return=representation to specify the response shape
2.
ODATA-827 introduce $compute query option
iii. Enumerations
1.
ODATA-849 Add possibility for enumeration types to "extend" another enumeration type
2.
ODATA-494 Define inheritance for enumeration types
3.
ODATA-874 Allow Edm.String as underlying type for enumeration types
iv. Simplified Payload
1.
ODATA-818
Omit properties whose value is null or the $metadata-defined default value
2.
ODATA-809
Define non-message format for final response of async request
3.
ODATA-747Allow IEEE 754 constants [-]INF and NaN also for Edm.Decimal and integer types
v. OData protocol
1.
ODATA-480 $batch: remove restriction "within the same change set " for Content-ID referencing
2.
ODATA-921
Specify operations for keyless nav props
3.
ODATA-920 Specify overflow for int data types
4.
ODATA-919 Specify the result type for each operation based on operator types
5.
ODATA-918 Add operator "divideby" that always results in a decimal.
6.
ODATA-921:
Specify operations for keyless nav props
vi. OData CSDL
1.
ODATA-923:
$expand for $metadata to include referenced schemas
6.
OData JSON CSDL [9:20am]
a.
New issues
i. ODATA-925:
Define Core term for service/schema/model version
b.
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
c.
Next steps
i. Discuss next steps for alignment with Swagger JSON schema
- Data aggregation [9:30am]
a.
Hierarchy discussion
b.
Issues
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
- OData extension for Temporal Data [9:40am]
- Next meeting [9:50am]
b.
Thursday March 31, 2016?
- AOB and wrap up [9:55am]
[2] References
[3] Timeline