OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

odata message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]

Subject: Agenda for OData TC meeting on 2016-01-28

Here [1] is a draft agenda for the OData TC (Technical Committee) meeting scheduled on Thursday January 28, 2016 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.




[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=41447      


  1. Approve agenda [8:05am PT]


  1. Approve minutes from previous meeting(s) [8:10am PT]
    1. Minutes from Jan 21, 2015 TC meeting: https://www.oasis-open.org/apps/org/workgroup/odata/download.php/57367/odata-meeting-117_on-20160121-minutes.html   


  1. 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.     #0034: Ram to put together the OData vocabularies doc


  1. OData JSON Format for CSDL
    1. First public review ends Feb 26, 2016

  2. V4.0 ERRATA03 [8:20am PT]
    1. Issues for V4.0_ERRATA03 in New or Open state

                                                    i.     OData Protocol

1.      ODATA-781: substring: what to return if the start index is outside the first argument string, or the desired length exceeds the remaining string length [Open]


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

                                                    i.     Set Operations

Proposal by Gerald Krause: https://www.oasis-open.org/apps/org/workgroup/odata/download.php/57355/Index-Based%20Operations%20on%20Collections.docx

1.      ODATA-820   Allow indexing into collections

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

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

                                                   ii.     Simplified Syntax

      Proposal by Mike Pizzo: OData 4.1 URL Syntax Simplification Proposal

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

6.      ODATA-563 Allow casting strings to primitive types if the string contains the literal representation of an instance of the target type

7.      ODATA-556  Add "in" operator as syntactic sugar for a chain of "or" expressions

                                                  iii.     Adoption Blocker

1.      ODATA-881   Add support for Edm.Untyped

                                                  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

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

                                                  vi.     URL Conventions

1.      ODATA-617Allow 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-572Clarify 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

                                                vii.     Other

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

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

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

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


  1. Next meeting [9:50am PT]
    1. Thursday February 4, 2016 during 8-10am PT?


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


[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]