[odata] Agenda for OData TC meeting on 2015-11-12

["Handl, Ralf" <ralf.handl@sap.com>]

Here [1] is a draft agenda for the OData TC (Technical Committee) meeting scheduled on Thursday November 12, 2015 during 8-10am PDT (17:00-19:00 CEST). 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 [8:00am PT]

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

 

2.        Approve agenda [8:05am PT]

 

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

a.     Minutes from November 05, 2015 TC meeting: https://www.oasis-open.org/committees/download.php/56868/odata-meeting-112_on-20151105-minutes.html

 

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

a.     Action items due

                                  i.    None

 

5.        JSON Format for CSDL [8:20am PT]

a.     Document Walk-through

                                  i.    https://www.oasis-open.org/committees/download.php/56882/odata-json-csdl-v4.0-wd01-2015-11-09.docx

 

b.    Issues for JSON Format for CSDL in Applied state

                                  i.    ODATA-875             Use of $ref for referencing elements in a JSON Schema

 

6.        V4.0 ERRATA03 [8:50am PT]

a.     Issues for V4.0_ERRATA03 in New or Open state

                                  i.    OData CSDL

1.     ODATA-825             AnnotationPath and Path _expression_: traversal of multiple collection-valued scalar or navigation properties

2.     ODATA-865             14.2.1 Attribute Target: complete list of externally targetable CSDL elements

3.     ODATA-878             Example 84: EntityContainer is a Singleton, not an EntitySet

4.     ODATA-880             14.5.10: edm:Null can have edm:Annotation child elements

 

                                 ii.    OData JSON Format

1.     ODATA-656             Requesting clarity on payload ordering constraints for clients

 

                                iii.    OData Protocol

1.     ODATA-830             Header OData-EntityId: when required

2.     ODATA-837             Example 28: replace $deltaToken with a valid custom query option

3.     ODATA-869             Explicitly state the location of the Content-ID header in a change set

4.     ODATA-870             Round-off description for creating related entities when creating an entity

5.     ODATA-882             Mismatch between 11.2.6 Requesting Related Entities and 11.2.7 Requesting Entity References

 

                                iv.    OData URL Conventions

1.     ODATA-784             Need to specify the behaviour of arithmetic operators on Decimal type

2.     ODATA-785             Numeric promotion (on overflow) across "number type families" is undesirable.

 

7.        V4.01 [9:20am PT]

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

                                  i.    Adoption Blocker

1.     ODATA-881             Add support for Edm.Untyped

2.     ODATA-876             Allow services to return contained entities inline for delta responses

3.     ODATA-814             Don't need TargetId in a deleted link for a to 0..1 relationship

4.     ODATA-613             Allow POST to entity sets using the delta-response format

 

                                 ii.    Simplified Syntax

1.     ODATA-664             Consider supporting parameterless function imports with no parens

2.     ODATA-812             Allow omitting namespaces for unambiguous functions/actions

3.     ODATA-763             Allowing implicit aliasing of parameters (public comment c201412e00001)

4.     ODATA-799             Define Key-As-Segment URL convention for resource paths

5.     ODATA-834             Make type prefix optional for enumeration literals in URLs

 

                                iii.    Enum Types

1.     Proposal by Ken Baclawski: https://www.oasis-open.org/committees/download.php/56805/DerivationForEnumerations_KenBaclawski.html

2.     ODATA-494             Define inheritance for enumeration types

3.     ODATA-849             Add possibility for enumeration types to "extend" another enumeration type

 

                                iv.    Set Operations

1.     ODATA-666             Define Deep Update and Deep Upsert operations

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

3.     ODATA-613             Allow POST to entity sets using the delta-response format

4.     ODATA-615             Allow PATCH and DELETE with $filter on collections to modify or delete all (and only) the matching entities

5.     ODATA-616             Allow POST to collections of complex and primitive types, and DELETE with $filter

6.     ODATA-820             Allow indexing into collections

 

                                 v.    Simplified Payload

1.     ODATA-561             odata.type shouldn't require "#" for primitive types

2.     ODATA-630             Consider making odata the default namespace for annotations

3.     ODATA-813             Allow no metadata for non-OData clients

4.     ODATA-814             Don't need TargetId in a deleted link for a to 0..1 relationship

5.     ODATA-818             Omit properties whose value is null or the $metadata-defined default value

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

 

8.        Next meeting [9:50am PT]

a.     Thursday November 19, 2015 during 8-10am PT?

 

9.        AOB and wrap up [9:55am PT]

 

[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