RE: Agenda for OData TC meeting 2016-06-23

Room information was updated by: Stefan Hagen

Please register as usual and today at https://www.oasis-open.org/apps/org/workgroup/odata/event.php?event_id=41468

Room information was updated by: Stefan Hagen

Please register as usual and today at https://www.oasis-open.org/apps/org/workgroup/odata/event.php?event_id=41468

Agenda draft submitted via Email at https://www.oasis-open.org/apps/org/workgroup/odata/email/archives/201606/msg00095.html

Stefan Hagen: Voting Members: 5 of 13 (38%) (used for quorum calculation)

Ralf Handl (SAP): Voting Members: 7 of 13 (53%) (used for quorum calculation)

Ralf Handl (SAP): Achieved quorum:yes

Ralf Handl (SAP): 2.Approve agenda [6:05am]

Ralf Handl (SAP): Agenda is approved

Ralf Handl (SAP): 3.Approve minutes from previous meeting(s) [6:10am]

Ralf Handl (SAP): b.Minutes from June 16, 2016 TC meeting: https://www.oasis-open.org/committees/document.php?document_id=58372&wg_abbrev=odata

Ralf Handl (SAP): Minutes are approved

Ralf Handl (SAP): 4.Review action items [Action item list: https://www.oasis-open.org/apps/org/workgroup/odata/members/action_items.php] [8:15am]

c.Action items due

i.#0036: Register the OData- headers and preferences with IANA (due July 31, 2016)

Ralf Handl (SAP): Shift to next week, not due yet

Ralf Handl (SAP): 5.OData CSDL JSON [6:15]

d.Walkthrough WD02 based on OpenAPI 2.0

ii.Document (redlined): https://www.oasis-open.org/apps/org/workgroup/odata/download.php/58159/odata-json-csdl-v4.0-wd02-2016-05-18.docx

iii.Document (clean): https://www.oasis-open.org/apps/org/workgroup/odata/download.php/58174/odata-json-csdl-v4.0-wd02-2016-05-18-clean.docx

Ralf Handl (SAP): I move to require x-nullable for all nullable properties, and use JSON Schema type array syntax in addition where possible.

Mike Pizzo: I second

Ralf Handl (SAP): No objections, motion passes

Ralf Handl (SAP): I move to express the numeric value of an annotation member with an annotation @value instead of @odata.value

Mike Pizzo: I second

Ralf Handl (SAP): No objections, motion passed

Mike Pizzo: I move we merge functions and actions into an x-operations property

Ralf Handl (SAP): I second

Ralf Handl (SAP): Consensus: as "operation" already has a different meaning in OpenAPI this would add confusion, motion rejected

Ralf Handl (SAP): I move to represent annotations on null annotation values with shorter syntax, e.g. "@Some.Term:null@Within.Null":true

Hubert Heijkers: I second

Ralf Handl (SAP): No objections, motion passes

Hubert Heijkers: I move to resolve ODATA-890 as proposed.

Ralf Handl (SAP): I second

Ralf Handl (SAP): No objection, motion passes

Ralf Handl (SAP): 6.V4.01 issues [7:00am]

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

i.Ripe for resolution

Ralf Handl (SAP): Break until 17:55 / 8:55

Ralf Handl (SAP): ODATA-846

Hubert Heijkers: I move to approve ODATA-846 as proposed.

Mike Pizzo: I second

Ralf Handl (SAP): No objections, motion passes

Ralf Handl (SAP): https://issues.oasis-open.org/browse/ODATA-545

Ralf Handl (SAP): Allow applying Capability terms CountRestrictions, TopSupported, SkipSupported etc. to all resources returning collections

Ralf Handl (SAP): Postpone until we have feedback from implementation teams

Ralf Handl (SAP): 3.ODATA-948 Versions of vocabularies and their relation with a version of the specification

Ralf Handl (SAP): 1) We should not add 4.01 to the edmx Version element, as we are not defining a new version of the edmx (i.e., no new elements or attributes).

2) Clarify that the new "Collection" value added in ODATA-631 can only be returned for 4.01 and greater payloads

3) For 4.0 clients, the service can include a subset of valid values (i.e., just entityset) or can specify more generically (i.e., property, navigationproperty).

4) Tell 4.01 clients that they should be prepared for this set to expand in the future.

Ralf Handl (SAP): ODATA-948 is OPEN

Ralf Handl (SAP): Proposal updated after discussion, postponed until ODATA-545 is resolved

Ralf Handl (SAP): 4.ODATA-696 Support "interfaces" for casting entities to multiple different types

Ralf Handl (SAP): Services MAY support casting any entity type, complex type, primitive type, or type definition to a type outside of the type hierarchy, following standard cast semantics including path constructs in URLs. If an instance of the type doesn't support the cast, a null is returned.

The target type of the cast may have some or no properties in common with the source type, and properties with the same name may have different values and even different types.

If casting to an entity type, the entity type may have an entity key which may or may not match the entity key of the type that implements it.

A new term is added to the Core vocabulary to advertise the set of types outside of the type hierarchy that a type may be cast to:

<Annotation Term="Core.Description"

String="A space-delimited list of types that this type can be cast to."/>

</Term>

Services MUST support casting instances of the annotated type to the target type(s) using existing cast segments and semantics. If an instance of the type doesn't support the cast, the cast results in a null value.

Mike Pizzo: Updated proposal:

Mike Pizzo: <Term Name="MayImplement" Type="Collection(Edm.String)">

<Annotation Term="Core.Description"

String="A collection of types that this type may be cast to."/>

</Term>

Hubert Heijkers: I move to resolve ODATA-696 as proposed.

Mike Pizzo: I second

Ralf Handl (SAP): No objections, the motion passes

Ralf Handl (SAP): 7.Next meeting [9:50am]

b.Thursday July 07, 2016 6-10am PT again a longer meeting

Ralf Handl (SAP): 8.AOB and wrap up [9:55am]

Ralf Handl (SAP): Meeting is adjourned

From: odata@lists.oasis-open.org [mailto:odata@lists.oasis-open.org] On Behalf Of Handl, Ralf
Sent: Donnerstag, 23. Juni 2016 13:04
To: odata@lists.oasis-open.org
Subject: [odata] Agenda for OData TC meeting 2016-06-23

Here [1] is the agenda for the OData TC (Technical Committee) meeting scheduled on Thursday June 23, 2016 during 6-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

1. Roll call [6:00am]

a. Self-registration link: https://www.oasis-open.org/apps/org/workgroup/odata/event.php?event_id=41468

2. Approve agenda [6:05am]

3. Approve minutes from previous meeting(s) [6:10am]

b. Minutes from June 16, 2016 TC meeting: https://www.oasis-open.org/committees/document.php?document_id=58372&wg_abbrev=odata

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

c. Action items due

i. #0036: Register the OData- headers and preferences with IANA (due July 31, 2016)

5. OData CSDL JSON [6:15]

d. Walkthrough WD02 based on OpenAPI 2.0

ii. Document (redlined): https://www.oasis-open.org/apps/org/workgroup/odata/download.php/58159/odata-json-csdl-v4.0-wd02-2016-05-18.docx

iii. Document (clean): https://www.oasis-open.org/apps/org/workgroup/odata/download.php/58174/odata-json-csdl-v4.0-wd02-2016-05-18-clean.docx

e. Discuss next steps

iv. Publish CSD02 right away to get feedback on OpenAPI mapping

6. V4.01 issues [7:00am]

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

i. Ripe for resolution

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

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

3. ODATA-948 Versions of vocabularies and their relation with a version of the specification

4. ODATA-696 Support "interfaces" for casting entities to multiple different types

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

6. ODATA-809 Define non-message format for final response of async request

7. ODATA-798 Semantic Key or Alternate Key for entity types

8. ODATA-938 In 4.01 decide if we can support invoking actions with no params with no body

9. ODATA-935: Allow singletons to be members of an entity set

10. ODATA-952 Replace multiple batch capability term with single "BatchSupport" term

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

12. ODATA-923: $expand for $metadata to include referenced schemas

13. ODATA-798 Semantic Key or Alternate Key for Entity Types

ii. OData protocol

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

2. ODATA-942: How should headers applied to a batch affect statements within a batch?

iii. Annotations

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

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

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

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

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

iv. 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-933: Allow using instance annotations in $filter

v. Set operations

14. ODATA-836: Allow applying actions to a filtered collection of entities

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

vii. OData CSDL

1. ODATA-618: Allow using term names in positions that allow type names

2. ODATA-929: Nullable facet should default to false for collection types, rather than being unspecified

3. ODATA-674: Specify navigation property binding combined with containment *

viii. JSON Format

1. ODATA-868 - Describe format for In-Stream errors

2. ODATA-557 - Allow exponential notation for Edm.Decimal

i. Interfaces

3. ODATA-619: Attach action and function signatures to terms, i.e. make a term definition an interface definition

7. Next meeting [9:50am]

b. Thursday July 07, 2016 6-10am PT – again a longer meeting

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