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: RE: Agenda for OData TC meeting on 2015-12-03 - chat transcript

Room information was updated by: Stefan
Please register your attendance as usual at https://www.oasis-open.org/apps/org/workgroup/odata/event.php?event_id=39127 - registration is now open. Thanks.

 

Stefan: Voting Members: 1 of 13 (7%) (used for quorum calculation)
Stefan: Voting Members: 3 of 13 (23%) (used for quorum calculation)

 

anonymous morphed into Matt Borges (SAP)

 

Ralf Handl (SAP): Voting Members: 7 of 13 (53%)
Ralf Handl (SAP): Achieved quorum: yes

 

Susan Malaika (IBM): i move http://webconf.soaphub.org/conf/images/smile.gif

 

Ramesh Reddy(Redhat): I move I move I second

 

Ram (Microsoft): Sample motion: I move that the TC approve OData JSON Format for Common Schema Definition Language (CSDL) Version 4.0 Working Draft 01 and all associated artifacts packaged together in https://www.oasis-open.org/apps/org/workgroup/odata/download.php/57012/odata-json-csdl-v4.0-wd01-2015-11-20-final.zip as a Committee Specification Draft 01 and designate the Microsoft Word version of the specification as authoritative. I further move that the TC approve submitting the aforementioned Committee Specification Draft 01 for 30 days of public review and notifying the following external stakeholders <TBD>.

 

Susan Malaika (IBM): I move that the TC approve OData JSON Format for Common Schema Definition Language (CSDL) Version 4.0 Working Draft 01 and all associated artifacts packaged together in https://www.oasis-open.org/apps/org/workgroup/odata/download.php/57012/odata-json-csdl-v4.0-wd01-2015-11-20-final.zip as a Committee Specification Draft 01 and designate the Microsoft Word version of the specification as authoritative.
Susan Malaika (IBM): I further move that the TC approve submitting the aforementioned Committee Specification Draft 01 for 30 days of public review and notifying the following external stakeholders <TBD>.

 

Ramesh Reddy(Redhat): I second

 

Mike Pizzo: I move we hold our next Face to Face Meeting in Zurich March 2-3, 2016.

 

Ralf Handl (SAP): I second

 

Ram (Microsoft): Both the motions above (JSON CSDL spec) and F2F was approved unanimously.

 

Matt Borges (SAP): I move we close ODATA-800 as not fixed

 

Ralf Handl (SAP): I second

 

Ram (Microsoft): motion approved
Ram (Microsoft): OData-891 is open

 

Mike Pizzo: I move we resolve ODATA-891 as proposed.

 

Matt Borges (SAP): I second

 

Room Information:
Please register your attendance as usual at https://www.oasis-open.org/apps/org/workgroup/odata/event.php?event_id=39127 - registration is now open. Thanks.

 

Ram (Microsoft): ODATA-891 has been resolved. Motion passes.
Ram (Microsoft): ODATA-892 is now open

 

Mike Pizzo: I move we resolve ODATA-892 as proposed.

 

Ralf Handl (SAP): I second

 

Ram (Microsoft): ODATA-892 has been resolved. Motion passes unanimously.
Ram (Microsoft): ODATA-887 is now open
Ram (Microsoft): Move this from Errata03 to V4.01

 

Ramesh Reddy(Redhat): I see the XML define it as [4]   NCName   ::=   Name - (Char* ':' Char*)

 

anonymous111 asked for a victim, I choose... Ramesh Reddy(Redhat)
anonymous111111 asks: null
Magic 8-Ball says: It is certain
anonymous2111 asked for a victim, I choose... anonymous11111111111
anonymous2111111 asks: null
Magic 8-Ball says: Very doubtful

 

Ram (Microsoft): ODATA-893 is now open

 

Mike Pizzo: I propose we resolve ODATA-893 by clarifying the protocol section that, as per the format specification, the type must be specified for derived types.

 

Mark Biamonte (Progress): I second

 

Mike Pizzo: Further that we call out explicitly our intention that the type (and id) cannot be changed on update.

 

Mark Biamonte (Progress): I second

 

Ram (Microsoft): Further, we intend to open a separate issue in V4.01 relax this and services to support this capability.
Ram (Microsoft): ODATA-893 has been resolved as proposed above

 

Mike Pizzo: Ram to request a new standards track work product for "Vocabularies" that will contain a small prose document and pointer to the vocabularies as additional artifacts.

 

Ram (Microsoft): ODATA-886 is now open.

 

anonymous111 asked for a victim, I choose... Matt Borges (SAP)
anonymous111111 asks: null
Magic 8-Ball says: As I see it, yes

 

Ram (Microsoft): ODATA-885 is now open.  Proposers to come up with a concrete proposal.

 

Mike Pizzo: Happy holidays everyone!

 

anonymous111 asked for a victim, I choose... anonymous
anonymous111111 asks: null
Magic 8-Ball says: Yes

 

Ralf Handl (SAP): Next meeting on Thursday January 07 2016

 

 

From: odata@lists.oasis-open.org [mailto:odata@lists.oasis-open.org] On Behalf Of Ram Jeyaraman
Sent: Mittwoch, 2. Dezember 2015 18:19
To: odata@lists.oasis-open.org
Subject: [odata] Agenda for OData TC meeting on 2015-12-03

 

Here [1] is a draft agenda for the OData TC (Technical Committee) meeting scheduled on Thursday December 3, 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]
    1. Self-registration link: https://www.oasis-open.org/apps/org/workgroup/odata/event.php?event_id=39127  

 

  1. Approve agenda [8:05am PT]

 

  1. Approve minutes from previous meeting(s) [8:10am PT]
    1. Minutes from November 19, 2015 TC meeting: https://www.oasis-open.org/apps/org/workgroup/odata/download.php/57014/odata-meeting-114_on-20151119-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.      None

 

  1. Approve OData JSON Format for CSDL as CSD01 and initiate public review [8:20am PT]
    1. Sample motion: I move that the TC approve OData JSON Format for Common Schema Definition Language (CSDL) Version 4.0 Working Draft 01 and all associated artifacts packaged together in https://www.oasis-open.org/apps/org/workgroup/odata/download.php/57012/odata-json-csdl-v4.0-wd01-2015-11-20-final.zip as a Committee Specification Draft 01 and designate the Microsoft Word version of the specification as authoritative. I further move that the TC approve submitting the aforementioned Committee Specification Draft 01 for 30 days of public review and notifying the following external stakeholders <TBD>.

 

  1. Approve next TC F2F meeting [8:30am PT]
    1. Sample motion: I move to hold the next F2F Meeting in Zürich during March 02 (Wednesday) and March 03 (Thursday), 2016.

 

  1. OData international standardization status [8:40am PT]
    1. ISO/IEC DIS 20802-1: 3720. Information technology -- Open data (OData) protocol -- Part 1: Protocol plus errata 02 
    2. ISO/IEC DIS 20802-2: 3721. Information technology -- Open data (OData) protocol -- Part 2: JSON format version 4.0 plus errata 02 
    3. The Draft International Standard (DIS) ballot to approve the OData v4 as an international standard is on (Nov 2015 through Jan 2016).
    4. The eventual approved international standard would have two parts (OData v4 Core and OData JSON Format v4).

 

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

                                                       i.      OData Protocol

1.      ODATA-800: Media streams section does not reference the AtomPub spec [Open]

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

                                                     ii.      OData URL Conventions

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

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

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

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

                                                    iii.      OData CSDL

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

                                                    iv.      OData JSON Format

1.      ODATA-893: Is @odata.type required on update of a derived type

                                                     v.      Vocabularies

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

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

 

  1. V4.01 [9:30am PT]
    1. 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

 

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

 

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

 

[2] References

 

[3] Timeline

 

 

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