RE: Agenda for OData TC meeting 2016-05-19

[8:00] Room information was updated by: Stefan Hagen

Please register at: https://www.oasis-open.org/apps/org/workgroup/odata/event.php?event_id=41463

Agenda-Draft-E-Mail available at: https://www.oasis-open.org/apps/org/workgroup/odata/email/archives/201605/msg00034.html

Minutes of previous meeting at:  https://www.oasis-open.org/committees/download.php/58164/odata-meeting-130_on-20160512-minutes.html

[8:01] Stefan Hagen: Info: Voting Members: 4 of 13 (30%) (used for quorum calculation)

[8:02] Ram (Microsoft): waiting for the conference call host to arrive

[8:07] Stefan Hagen: From registration page: Voting Members: 8 of 13 (61%) (used for quorum calculation)

[8:15] Stefan Hagen: ...: Voting Members: 9 of 13 (69%) (used for quorum calculation)

[8:27] Ram (Microsoft): No corrections to the agenda.Approval of minutes deferred to next meeting.

[8:27] Ram (Microsoft): Ram will send an approval package for OASIS OData Open Repos in the next day or two.

[8:27] Ram (Microsoft): Action #35 remains open

[8:28] Ram (Microsoft): Section 5 Errata 3 approval

[8:28] Ram (Microsoft): Reviewed the application of the resolutions

[8:29] Ram (Microsoft): Ram will work with Stefan to post the minutes for the May 5th meeting (which did not have a quorum)

[8:31] Ram (Microsoft): Sample motion: I move to close issues ODATA-936, ODATA-932, ODATA-931, ODATA-930, and ODATA-934 as applied

[8:34] Martin Z. SAP SE: I move to close issues ODATA-936, ODATA-932, ODATA-931, ODATA-930, and ODATA-934 as applied

[8:34] Mark Biamonte (Progress): I second

[8:35] Ram (Microsoft): motion passes, no objections

[8:39] Ram (Microsoft): Section 6 v4.01 issues

[8:39] Ram (Microsoft): ODATA-818   Omit properties whose value is null or the $metadata-defined default value

[8:50] Ralf Handl (SAP): omit-values=nulls+defaults

[9:00] KenBaclawski: I have an article that discusses the meaning of null in programming languages and databases that might be interesting for this discussion: http://www.ccs.neu.edu/home/kenb/MeaningOfNull.html

[9:00] Ram (Microsoft): Thanks Ken!

[9:02] Matt Borges (SAP): I move we resolve OData-818 as proposed

[9:03] Hubert Heijkers: I second

[9:03] Ram (Microsoft): motion passes, no objections, ODATA-818 has been resolved.

[9:16] Susan Malaika (IBM):  great nulls discussion

[9:20] Ram (Microsoft): ODATA-937: Consider making odata- prefix optional in headers, preference values, format parameters

[9:55] Mike Pizzo: Updated proposal:

For all except OData-Version and OData-MaxVersion, define the forms without the OData- prefix as aliases to the OData forms.

 Register the non-OData forms of the headers and preferences with IANA.

[9:55] Martin Z. SAP SE: I move we resolve OData-937 as proposed

[9:55] Mark Biamonte (Progress): i second

[9:55] Ram (Microsoft): no objections, ODATA-937 resolved as proposed

[9:56] Ram (Microsoft): ACTION: Register the OData- headers and preferences with IANA.

[10:00] Matt Borges (SAP): I have to drop off for another call

[10:03] Mike Pizzo: Consider modifying the proposal for ODATA-937 by not adding the OData prefix to new headers, preferences, and format parameters added in 4.01 and beyond that have a generic meaning (in particular, omit-values and SchemaVersion).

[10:05] Ram (Microsoft): next meeting: June 2.

[10:05] Ram (Microsoft): Meeting adjourned

From: odata@lists.oasis-open.org [mailto:odata@lists.oasis-open.org] On Behalf Of Ram Jeyaraman
Sent: May 18, 2016 6:28 PM
To: odata@lists.oasis-open.org
Subject: [odata] Agenda for OData TC meeting 2016-05-19

Here [1] is the agenda for the OData TC (Technical Committee) meeting scheduled on Thursday May 19, 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]
1. Self-registration link: https://www.oasis-open.org/apps/org/workgroup/odata/event.php?event_id=41463

Approve agenda [8:05am]

Approve minutes from previous meeting(s) [8:10am]
1. Minutes from May 5, 2016 TC meeting: TBD
2. Minutes from May 12, 2016 TC meeting: TBD

Review action items [Action item list: https://www.oasis-open.org/apps/org/workgroup/odata/members/action_items.php] [8:15am]
1. Action items due

i. #0035: Identify the right open source license for the OASIS Open Source repositories for vocabularies and libraries (due March 31, 2016)

V4.0 Errata 3 [8:20am]
1. Public review comment resolution log

i. https://lists.oasis-open.org/archives/odata/201605/msg00033.html

b. Next step

i. Approve Errata 3 docs as Approved Errata

c. Sample approval motions (needs Full Majority vote)

i. I move that the TC approve OData version 4.0 Errata 03 Working Draft 02 and all associated artifacts packaged together in <link to ZIP file> as an Approved Errata and make it available with OData version 4.0 OASIS Standard. Further, I confirm that the errata corrections do not constitute Substantive Changes to the Standard.

ii. I move that the TC approve OData JSON Format version 4.0 Errata 03 Working Draft 02 and all associated artifacts packaged together in <link to ZIP file> as an Approved Errata and make it available with OData JSON Format version 4.0 OASIS Standard. Further, I confirm that the errata corrections do not constitute Substantive Changes to the Standard.

V4.01 issues [8:40am]

a. Issues for V4.01_WD01 in New or Open state

i. 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

ii. Complex Types

1. ODATA-560 - Allow arbitrary properties in referential constraints

iii. OData protocol

1. ODATA-937: Consider making odata- prefix optional in headers, preference values, format parameters

2. ODATA-919 Specify the result type for each operation based on operator types

3. ODATA-846: Add version 4.01 (resolve as we get close to CSD01)

iv. Batch

1. ODATA-541 - Allow the If-Match header to reference the ETag that resulted from an earlier operation in a batch request

v. Annotations

1. ODATA-516 - Add super type Edm.AnyPath for Edm.PropertyPath, Edm.NavigationPropertyPath, and Edm.AnnotationPath

2. ODATA-545 - Allow applying Capability terms CountRestrictions, TopSupported, SkipSupported etc. to all resources returning collections

3. ODATA-571 - Add annotation for properties that are (not) part of the default selection if no $select is specified

4. ODATA-631 - Allow expressing that a term can be applied any collection and is not restricted to entity sets

5. ODATA-735 - Enhance the CSDL for instance annotations

6. ODATA-811 - Define propagation and (partial) overriding of annotations

7. ODATA-816 - Add Capability term for filter _expression_ restrictions

8. ODATA-859 - Define term, semantics for inserting error information into a (mostly) successful response

9. ODATA-884 - Add term ErrorCodes to describe possible codes in error messages (public comment c201510e00019)

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

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 2, 2016?

AOB and wrap up [9:55am]

[2] References

Conference call details: https://www.oasis-open.org/apps/org/workgroup/odata/download.php/56760/TC%20meeting%20dial-in%20details.htm
Chat room: http://webconf.soaphub.org/conf/room/odatatc

[3] Timeline

https://www.oasis-open.org/committees/document.php?document_id=56024&wg_abbrev=odata

odata message