[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Agenda for OData TC meeting 2016-03-17
Here [1] is a proposed 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 [2]. For TC timeline, see [3]. Feel free to suggest additions or modifications.
[1] Agenda
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
a.
Issues
for V4.01_WD01 in New or Open state
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
3.
ODATA-613 Allow POST to entity sets using the delta-response
ii. New Query Capabilities
4.
ODATA-614 Allow $expand, $select, ... with POST/PATCH/PUT in combination with return=representation to specify the response shape
5.
ODATA-827 introduce $compute query option
iii. Enumerations
6.
ODATA-849 Add possibility for enumeration types to "extend" another enumeration type
7.
ODATA-494 Define inheritance for enumeration types
8.
ODATA-874 Allow Edm.String as underlying type for enumeration types
iv. Simplified Payload
9.
ODATA-818
Omit properties whose value is null or the $metadata-defined default value
10.
ODATA-809
Define non-message format for final response of async request
11.
ODATA-747Allow IEEE 754 constants [-]INF and NaN also for Edm.Decimal and integer types
v. OData protocol
12.
ODATA-480 $batch: remove restriction "within the same change set " for Content-ID referencing 7.
OData JSON CSDL [9:20am]
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
v. Discuss next steps for alignment with Swagger JSON schema
a.
Hierarchy discussion
b.
Issues:
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?
[2] References
[3] Timeline |
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]