Proposed Agenda for Face to Face OData TC meeting in Zurich on 2016-03-02 through 2016-03-03

[Michael Pizzo <mikep@microsoft.com>]

Here [1] is a proposed agenda for the OData TC (Technical Committee) face-to-face meeting scheduled on Thursday February 25 and Friday February 26^th, 2016, during 9am-4pm Central European 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.

 

Notes:

1) Times are approximate but, for planning purposes for people on the phone, we will try to break at 12:00 noon Central European Time both days.

2) Issues without solid proposals to discuss will likely be postponed to day 2

 

Location: See email from Hubert Heijkers

 

[1] Agenda

 

1. Roll call [9:00am]
   1. Self-registration link: https://www.oasis-open.org/apps/org/workgroup/odata/event.php?event_id=41452          

 

2. Approve agenda [9:05am]

 

3. Approve minutes from previous meeting(s) [9:10am]
   1. Minutes from Feb 25, 2016 TC meeting: https://www.oasis-open.org/apps/org/workgroup/odata/download.php/57641/odata-meeting-121_on-20160225-minutes.html  

 

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

                                                               i.      None

 

5. Errata 3 Issues [9:20]
   1. Review applications of Errata 3 issue resolutions (This is a carryover from previous meeting)

                                                               i.      Entertain motion to close all applied issues

2. Errata 3 Issues in New/Open State

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

1.       OData Protocol

a.       ODATA-882: Mismatch between 11.2.6 Requesting Related Entities and 11.2.7 Requesting Entity References [Open]

b.       ODATA-908: 8.1.1 Header Content-Type: is only SHOULD in RFC7231

c.       ODATA-916 Define what services (and clients?) do with unknown format parameters

d.       ODATA-913: Should we specify a default response format if neither Accept header nor system query $format are specified

2.       OData URL Conventions

a.       ODATA-784: Need to specify the behaviour of arithmetic operators on Decimal type [Open]

b.       ODATA-785: Numeric promotion (on overflow) across "number type families" is undesirable. [Open]

c.       ODATA-917 5.1.1.2.1 Addition and 5.1.1.2.2 Subtraction: Date add/sub Duration is DateTimeOffset - but in which time zone?

3.       OData CSDL

a.       ODATA-912: Clarify what clients should do if they see an unknown/invalid _expression_ for a known annotation term.

 

6.       OData JSON CSDL [11:30am]

a.       Public Review Comments

                                          i.    ODATA-907: Consider Swagger for describing OData metadata in JSON format (public comment c201602e00000)

                                                             ii.      ODATA-910: Consider format that is tailored for programmatic access (public comment c201602e00002)

                                                           iii.      ODATA-911: Miscellanous feedback (public comment c201602e00003)

                                                           iv.      ODATA-914: Comments from OASIS Technical Advisory Board (TAB)  

b.       Other Issues in New or Open state

                                                               i.      ODATA-906 Consider how to specify an included namespace as a default in JSON CSDL

                                                             ii.      ODATA-902 4.5.2: make "annotations" a hash-map with the target as key

                                                           iii.      ODATA-890 Specify how to get from a JSON message to a JSON schema for validating this message

                                                           iv.      ODATA-889 Make edm.json a stand-alone schema

                                                             v.      ODATA-863 Represent Terms similar to Types

 

7.       Break for Lunch [12:00]

 

8. V4.01 issues [1:00-4:00pm]

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

                                                               i.      Set Operations

1.       Review Revised Proposal

2.       Address Issues

a.       ODATA-820   Allow indexing into collections

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

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

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

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

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

                                                             ii.      OData CSDL

1.       ODATA-887 Should we allow multi-part namespace alias names?

2.       ODATA-894 Support complex property overwriting in derived type [proposed]

3.       ODATA-895 Support keyless entities for singleton

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

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

7.       ODATA-747Allow IEEE 754 constants [-]INF and NaN also for Edm.Decimal and integer types

                                                             v.      Adoption Blocker

1.       ODATA-881   Add support for Edm.Untyped

2.       ODATA-838 Allow inclusion of "untyped JSON" into JSON requests and responses

                                                           vi.      URL Conventions

1.       ODATA-617 Allow eq/ne comparison of instances of same structured (complex or entity) type, allow eq/ne comparison with null for 0..1 nav props

2.       ODATA-572 Clarify that eq, ne can be used with complex type

3.       ODATA-897 Allow the count of a filtered/searched collection in common expressions (proposed)

4.       ODATA-888 Allow $search for all collections

5.       ODATA-482 Allow inlining stream properties and media resources

6.       ODATA-901 substring: Define negative index for substring function

                                                          vii.      OData protocol

1.       ODATA-480 $batch: remove restriction "within the same change set " for Content-ID referencing

 

9. Data aggregation
   1. Hierarchy discussion
   2. 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 qualifiedComplexTypeName

10. OData extension for Temporal Data

 

11. Next meeting

3. Thursday March 17, 2016?

 

12. AOB and wrap up [Day 2: 4:00pm]

 

[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