[7:55] Room information was updated by: Stefan Hagen
Please register your selves at https://www.oasis-open.org/apps/org/workgroup/odata/event.php?event_id=41467
Agenda draft in mail from Ram at: https://www.oasis-open.org/apps/org/workgroup/odata/email/archives/201606/msg00040.html
[7:55] Stefan Hagen: Info on participation: Voting Members: 1 of 13 (7%) (used for quorum calculation)
[8:00] anonymous morphed into Matt Borges (SAP)
[8:02] anonymous morphed into Mark Biamonte (Progress)
Room Information:
Please register your selves at https://www.oasis-open.org/apps/org/workgroup/odata/event.php?event_id=41467
Agenda draft in mail from Ram at: https://www.oasis-open.org/apps/org/workgroup/odata/email/archives/201606/msg00040.html
[8:09] Stefan Hagen: Voting Members: 8 of 13 (61%) (used for quorum calculation)
[8:11] Ram (Microsoft): Agenda approved. No corrections.
[8:12] Ram (Microsoft): Minutes approved. No corrections.
[8:12] Ram (Microsoft): No progress on the one open action item.
[8:12] Ram (Microsoft): Discussion on Null (by Ken)
[8:12] Ram (Microsoft): Ken: _javascript_ distinguishes between null and undefined
[8:14] anonymous morphed into Ralf Handl (SAP)
[8:24] Ram (Microsoft): We should have a section on treatment of null in the spec
[8:43] Ram (Microsoft): Ken to open issues related to null treatment in OData
[8:58] Ram (Microsoft): v4.01 issues
[8:59] Mike Pizzo: I think the following issues are reasonably well understood and could be processed:
[8:59] Mike Pizzo: ODATA-940: Define a validation term for valid values
ODATA-560 - Allow arbitrary properties in referential constraints
ODATA-696: Support "interfaces" for casting entities to multiple different types
ODATA-809 Define non-message format for final response of async request
ODATA-798 - Semantic Key or Alternate Key for entity types
ODATA-816 - Add Capability term for filter _expression_ restrictions
[8:59] Ram (Microsoft): ODATA-940: Define a validation term for valid values
[9:06] Ram (Microsoft): Issue is now open, no objections
[9:15] Mike Pizzo: Modified proposal based on Ralf's comments that we don't need "Extends" or "Merges" (at this point) but should keep the structure for extensibility:
[9:15] Mike Pizzo: <Term Name="AllowedValues" Type="Validation.ValueEnumeration">
<Annotation Term="Core.Description"
String="A collection of valid values for the annotated property, parameter, or type definition" />
</Term>
<ComplexType Name="ValueEnumeration">
<Property Name="Values" Type="Collection(Validation.AllowedValue)" />
</ComplexType>
<ComplexType Name="AllowedValue">
<Property Name="Value" Type="Edm.PrimitiveType">
<Annotation Term="Core.Description" String="An allowed value for the property, parameter, or type definition" />
</Property>
</ComplexType>
[9:19] Mike Pizzo: Further simplifying the proposal:
[9:19] Mike Pizzo: <Term Name="AllowedValues" Type="Collection(Validation.AllowedValue)">
<Annotation Term="Core.Description"
String="A collection of valid values for the annotated property, parameter, or type definition" />
</Term>
<ComplexType Name="AllowedValue">
<Property Name="Value" Type="Edm.PrimitiveType">
<Annotation Term="Core.Description" String="An allowed value for the property, parameter, or type definition" />
</Property>
</ComplexType>
[9:20] Mike Pizzo: I move to resolve ODATA-940 according to the revised proposal.
[9:20] Ralf Handl (SAP): I second
[9:21] Ram (Microsoft): ODATA-940 has been resolved, no objections
[9:26] Ram (Microsoft): ODATA-560 - Allow arbitrary properties in referential constraints
[9:45] Ralf Handl (SAP): I move to resolve ODATA-560 as proposed
[9:45] Mike Pizzo: I second
[9:45] Ram (Microsoft): ODATA-560 has been resolved, no objections
[9:45] Ram (Microsoft): ODATA-696: Support "interfaces" for casting entities to multiple different types
[10:03] Ram (Microsoft): issue open, no objections
[10:04] Ram (Microsoft): Issue proposal needs further discussion. We will do this at the next meeting
[10:07] Ram (Microsoft): No other business.
[10:07] Ram (Microsoft): Next meeting: 6-10am PT June 23rd.
[10:07] Ram (Microsoft): Meeting adjourned
From: Ram Jeyaraman
Sent: June 15, 2016 6:33 PM
To: odata@lists.oasis-open.org
Subject: Agenda for OData TC meeting 2016-06-16
Here [1] is the agenda for the OData TC (Technical Committee) meeting
scheduled on Thursday June 16, 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=41467
- Approve agenda [8:05am]
- Approve minutes from previous meeting(s) [8:10am]
- Minutes from June 9, 2016 TC meeting:
https://www.oasis-open.org/apps/org/workgroup/odata/download.php/58354/odata-meeting-133_on-20160609-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. #0036:
Register the OData- headers and preferences with IANA (due July 31, 2016)
- Use of null in OData [8:20am]
- Null in the OData Standard [by
Ken Baclawski]
- V4.01 issues [8:40am]
a.
Issues
for V4.01_WD01 in New or Open state
i. OData protocol
1.
ODATA-919 Specify the result type for each operation based on operator types
2.
ODATA-846: Add version 4.01 (resolve as we get close to CSD01)
3.
ODATA-942: How should headers applied to a batch affect statements within a batch?
4.
ODATA-948: Versions of vocabularies and their relation with a version of the specification
ii. Annotations
1.
ODATA-545 - Allow applying Capability terms CountRestrictions, TopSupported, SkipSupported etc. to all resources returning collections
2.
ODATA-571 - Add annotation for properties that are (not) part of the default selection if no $select is specified
3.
ODATA-735 - Enhance the CSDL for instance annotations
4.
ODATA-811 - Define propagation and (partial) overriding of annotations
5.
ODATA-816 - Add Capability term for filter _expression_ restrictions
6.
ODATA-859 - Define term, semantics for inserting error information into a (mostly) successful
response
7.
ODATA-884 - Add term ErrorCodes to describe possible codes in error messages (public comment
c201510e00019)
8.
ODATA-940: Define a validation term for valid values
iii. Complex Types
1.
ODATA-560 - Allow arbitrary properties in referential constraints
iv. Simplified Payload
1.
ODATA-809
Define non-message format for final response of async request
v. Batch
1.
ODATA-541 - Allow the If-Match header to reference the ETag that resulted from an earlier operation in a batch request
vi. 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
3.
ODATA-798 - Semantic Key or Alternate Key for entity types
vii. 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
viii. OData CSDL
1.
ODATA-923:
$expand for $metadata to include referenced schemas
2.
ODATA-618: Allow using term names in positions that allow type names
3.
ODATA-929: Nullable facet should default to false for collection types, rather than being unspecified
4.
ODATA-674:
Specify navigation property binding combined with containment *
5.
ODATA-935: Allow singletons to be members of an entity set
ix. JSON Format
1.
ODATA-868 - Describe format for In-Stream errors
2.
ODATA-938: In 4.01 decide if we can support invoking actions with no params with no body
x. Decimal
1.
ODATA-557 - Allow exponential notation for Edm.Decimal
ii. URL Conventions
1.
ODATA-933: Allow using instance annotations in $filter
iii. Interfaces
1.
ODATA-619: Attach action and function signatures to terms, i.e. make a term definition an interface definition
2.
ODATA-696: Support "interfaces" for casting entities to multiple different types
iv. Set operations
1.
ODATA-836: Allow applying actions to a filtered collection of entities
- 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
iv. ODATA-939: Add example for groupby single-valued navigation property
v. ODATA-943: Correct broken link for Groupable Property
vi. ODATA-944: Clarify scope of property paths in transformations
vii. ODATA-945: Correct examples 53 and 54
viii. ODATA-946: Clarify scope for $apply
ix. ODATA-947: Transformation for computing ratios with aggregated values
8.
OData CSDL JSON [9:40am]
a.
Parked issues
i. ODATA-906 Consider how to specify an included namespace as a default in JSON CSDL
ii. ODATA-890 Specify how to get from a JSON message to a JSON schema for validating this
message
iii. ODATA-863 Represent Terms similar to Types
- Next meeting [9:50am]
b.
Thursday June 23, 2016 6-10am PT
- AOB and wrap up [9:55am]
[2] References
[3] Timeline