[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Agenda for OData TC meeting 2016-03-10
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 <URL to ZIP file in TC's Kavi document
repository> 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/57686/odata-v4.0-errata03-wd01-2016-03-03.docx 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/57690/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 <URL to ZIP file in TC's Kavi document repository> 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]