[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: RE: Revised Agenda for OData TC meeting 2016-03-17
Please register at https://www.oasis-open.org/apps/org/workgroup/odata/event.php?event_id=41454 as usual.
Agenda draft is at https://www.oasis-open.org/apps/org/workgroup/odata/email/archives/201603/msg00190.html (mail from Ram)
[8:33] Ram (Microsoft): Ralf Handl: Quorum achieved
Ralf Handl: 2.Approve agenda
Ralf Handl: Agenda is approved
Ralf Handl: 3.Approve minutes from previous meeting
Ralf Handl: a.Minutes from March 10, 2016 TC meeting: https://www.oasis-open.org/apps/org/workgroup/odata/download.php/57722/odata-meeting-123_on-20160310-minutes.html
Ralf Handl: Minutes are approved
Ralf Handl: 4.Review action items
Ralf Handl: Action items 33 and 31 are closed
(g) Mike Pizzo: Acion Item 32 wiill be rescheduled for a future date to give Martin time to present on HTTP/2
(g) Ram (Microsoft): Ralf presents the swaggerized JSON CSDL example and highlights what's new
[8:36] anonymous morphed into Matt Borges (SAP)
[8:38] Mike Pizzo1: Thought: perhaps we should provide a service that can generate the path portion of a swagger document given the definitions section. Then, if swagger tools support $ref for the body of the path property, services could put a ref to that service, with a query option pointing back to their definitions document, that would automatically generate the paths section based on that document.
[8:41] Mark Biamonte (Progress): I had a similar thought. I was wondering whether the service could tell if the client was a swagger client and generate the path section for a swagger client and have it empty or omitted for a non-swagger client
[8:49] Mike Pizzo1 morphed into Mike Pizzo
[8:49] Ram (Microsoft): ACTION (Ram): Identify the right open source license for the OASIS Open Source repositories for vocabularies and libraries
[8:49] Ralf Handl (SAP SE): Open Repository on GitHub for Vocabulary evolution: Ram to find out which Open Source license is compatible with our TC IPR mode
[8:50] Ralf Handl (SAP SE) morphed into Ralf Handl (SAP)
[8:53] Ram (Microsoft): Issues discussion
[8:53] Ram (Microsoft): ODATA-876 Allow services to return contained entities inline for delta responses
[9:00] Mike Pizzo: I move we resolve ODATA-876 as proposed
[9:00] Mark Biamonte (Progress): I second
[9:01] Ram (Microsoft): Motion passes, no objections
[9:01] Ram (Microsoft): ODATA-666 Define Deep Update and Deep Upsert operations
[9:10] Mike Pizzo: Added as 2d: d. If present in the top level resource, it must match both the odata.etag value and any if-match header
[9:21] Ram (Microsoft): ACTION: Separate new issue for defining the semantics of PUT for issuing a deep update against a single entity
[9:22] Matt Borges (SAP): I move we resolve ODATA-666 as proposed
[9:22] Gerald Krause (SAP): I second.
[9:23] Ram (Microsoft): ODATA-613 Allow POST to entity sets using the delta-response
[9:37] Ram (Microsoft): PATCH operation is neither safe or idempotent
[9:37] Ram (Microsoft): PATCH operation should be executed atomically
[9:49] Mike Pizzo: Propose that Response, if requested, should be a delta representation, in the same structure and order as the request payload, representing changes. This means that the response has to be constructed as the request is processed, not generated from an after-image.
[9:55] Mike Pizzo: updated proposal from issue: PATCH to a collection of entities can take a delta payload (interpreted as deltas if body represents a collection of entities) ODATA-613
a.MUST NOT have $filter, $select, $orderby, etc.
For PATCH, you don't specify a $expand so the extent of that graph is undefined. Therefore, it is valid to have added/deleted links to anything (at least anything reachable from the target; service probably wouldn't bother validating). So Clients SHOULD make sure added/deleted links are reachable from target, but clients need not validate.
Response, if requested, should be a delta representation, in the same structure and order as the request payload, representing changes.
[9:56] Ram (Microsoft): ODATA-666: Motion passes, no objections
[9:56] Matt Borges (SAP): I move we resolve ODATA-613 as proposed
[9:56] Mike Pizzo: I second
[9:57] Ram (Microsoft): Motion passes, no objections
[9:58] Ram (Microsoft): YAML: http://yaml.org/
[10:00] Ram (Microsoft): RAML: http://raml.org/
[10:03] Ram (Microsoft): Next meeting: March 24 8-10am PT.
[10:03] Ram (Microsoft): Meeting adjourned.
Here  is a revised agenda for the OData TC (Technical Committee) meeting scheduled on Thursday March 17 during 8-10am Pacific Time. For additional information, such as dial-in details and chat room, refer to . For TC timeline, see . Feel free to suggest additions or modifications.
The changes are (based on Mike’s suggestion):
· New issue to 6)a)i): ODATA-922 Support DELETE/PUT to $ref of a collection-valued nav prop to remove/replace all links
· News issues to 6)a)v):
o ODATA-921 Specify operations for keyless nav props
i. #0033: Propose factoring of CSDL documents
ii. #0032: Overview presentation on HTTP/2 features
iii. #0031: Follow up with JSON-Schema on use for modeling
i. Set Operations
1. ODATA-876 Allow services to return contained entities inline for delta responses
2. ODATA-666 Define Deep Update and Deep Upsert operations
4. ODATA-922 Support DELETE/PUT to $ref of a collection-valued nav prop to remove/replace all links
ii. New Query Capabilities
5. ODATA-614 Allow $expand, $select, ... with POST/PATCH/PUT in combination with return=representation to specify the response shape
6. ODATA-827 introduce $compute query option
7. ODATA-849 Add possibility for enumeration types to "extend" another enumeration type
8. ODATA-494 Define inheritance for enumeration types
9. ODATA-874 Allow Edm.String as underlying type for enumeration types
iv. Simplified Payload
10. ODATA-818 Omit properties whose value is null or the $metadata-defined default value
11. ODATA-809 Define non-message format for final response of async request
12. ODATA-747Allow IEEE 754 constants [-]INF and NaN also for Edm.Decimal and integer types
v. OData protocol
13. ODATA-480 $batch: remove restriction "within the same change set " for Content-ID referencing
14. ODATA-921 Specify operations for keyless nav props
15. ODATA-920 Specify overflow for int data types
16. ODATA-919 Specify the result type for each operation based on operator types
17. ODATA-918 Add operator "divideby" that always results in a decimal.
7. OData JSON CSDL [9:20am]
a. Parked issues
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
v. Discuss next steps for alignment with Swagger JSON schema
vi. ODATA-905 Example 67: result row for USA, Sugar missing, Example 68: last total should be 7
vii. ODATA-904 Example 55: clarify groupby in combination with relationships of instance cardinality zero
viii. ODATA-909 ABNF for pathPrefix should also allow qualified ComplexTypeName
b. Thursday March 24, 2016?