RE: Agenda for OData TC meeting on 2016-01-21

[Michael Pizzo <mikep@microsoft.com>]

Going through the list of issues, I observe that the agenda below does not represent issues added since November 20^th.  Some of these issues might be easy wins to get resolved prior to the face to face. As such, I would like to add discussion of the following topics to their respective sections below.

 

Errata 3

Url Conventions:

ODATA-891 Misleading reference to "open" in description of $select (proposed)

ODATA-892 Clarify dynamic properties support in $filter, $orderby, $expand (proposed)

JSON Format:

ODATA-896 Reconsider guidance on odata.count position (public comment c201512e00001)

ABNF:

ODATA-899 Type cast segment after $all (proposed)

 

4.01

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

CSDL:

ODATA-894 Support complex property overwriting in derived type (proposed)

ODATA-895 Support keyless entities for singletons

URL Conventions:

ODATA-888 Allow $search for all collections

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

ODATA-900 Cross-service naviation and service versioning

JSON Schema

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

Atom

ODATA-898 Note the different sets of properties to be expected within atom:content

 

I would also propose that we handle Errata before 4.01; skipping topics that we intend to cover at the Face to Face.

 

Finally, based on past discussions, I suggest we defer the following issues to the face to face as they have been discussed in the weekly TC meeting and seem to need deeper discussion:

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

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

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

 

Applying these changes, I would propose the following revised agenda be discussed during agenda item 2:

 

[1] Agenda

 

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

 

2. Approve agenda [8:05am PT]

 

3. Approve minutes from previous meeting(s) [8:10am PT]
   1. Minutes from Jan 7, 2015 TC meeting: https://www.oasis-open.org/apps/org/workgroup/odata/download.php/57258/odata-meeting-116_on-20160107-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]
   1. Action items due

                                                               i.      None

 

5. Next TC F2F meeting [8:20am PT]
   1. Confirmed - In Zürich during March 02 (Wednesday) and March 03 (Thursday), 2016.
   2. Proposed agenda topics: JSON Schema, v4 errata 3, OData 4.1, OData Extensions for Data Aggregation and Temporal Data
   3. Hubert will soon provide information about logistics (location information and related information)

 

6. Timeline (preferred state of various docs by June 2016) [8:30am PT]
   1. OData v4 Errata (Approved Errata)
   2. OData v4.1 (Committee Specification Draft 01)
   3. Extensions for Data Aggregation (Committee Specification 02) – already in projected state
   4. Extensions for Temporal Data (Committee Specification Draft 01)
   5. OData JSON Schema for CSDL (Committee Specification 01)

 

7. V4.0 ERRATA03 [9:40am PT]
   1. Issues for V4.0_ERRATA03 in New or Open state

                                                               i.      OData Protocol

1.       ODATA-882: Mismatch between 11.2.6 Requesting Related Entities and 11.2.7 Requesting Entity References [Defer to F2F]

                                                             ii.      OData URL Conventions

1.       ODATA-784: Need to specify the behaviour of arithmetic operators on Decimal type [Defer to F2F]

2.       ODATA-785: Numeric promotion (on overflow) across "number type families" is undesirable. [Defer to F2F]

3.       ODATA-891 Misleading reference to "open" in description of $select [New][Proposed]

4.       ODATA-892 Clarify dynamic properties support in $filter, $orderby, $expand [New][Proposed]

                                                           iii.      Vocabularies

1.       ODATA-886: Need a stable reference to latest/current OASIS OData vocabularies  [Open] [Proposed]

2.       ODATA-885: Permissions should apply to more than just properties [Open]

                                                           iv.      JSON Format

1.       ODATA-896 Reconsider guidance on odata.count position (public comment c201512e00001) [New]

                                                             v.      ABNF

1.       ODATA-899 Type cast segment after $all [New][Proposed)

 

8. V4.01 [8:40am PT]
   1. Issues for V4.01_WD01 in New or Open state

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

                                                             ii.      Adoption Blocker

1.       ODATA-881             Add support for Edm.Untyped

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

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

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

                                                           vi.      OData CSDL

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

                                                          vii.      Other

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

2.      ODATA-894 Support complex property overwriting in derived type (proposed)

3.      ODATA-895 Support keyless entities for singleton

4.      ODATA-888 Allow $search for all collections

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

6.      ODATA-900 Cross-service navigation and service versioning

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

8.      ODATA-898 Note the different sets of properties to be expected within atom:content

 

 

9. Next meeting [9:50am PT]
   1. Thursday January 28, 2015 during 8-10am PT?

 

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