RE: Proposed Agenda for Face to Face OData TC meeting in Zurich on 2016-

[9:03] Ralf Handl (SAP): OData TC Face-to-Face meeting continues

[9:03] Ralf Handl (SAP): Good morning, Stefan!

[9:04] Ralf Handl (SAP): I've started the screen-sharing connection, use https://sap.emea.pgiconnect.com/OData-TC/ to join

[9:04] Ralf Handl (SAP): First agenda item:

[9:04] Ralf Handl (SAP): Review application of Errata03 issues resolved yesterday

[9:04] Ralf Handl (SAP): Mike will walk through the documents

[9:05] Ralf Handl (SAP): Screen sharing session will start ~09:10 CET

[9:22] Stefan: @Ralf: I will join in a few minutes. Thanks!

[9:30] Ralf Handl (SAP): @Stefan: good morning! Good to have you join!

[10:10] Stefan: I second

[10:17] Stefan: ... in a minute ...

[10:25] Mike Pizzo1:

[10:26] Mike Pizzo1:

[10:28] Ralf Handl (SAP): I move to CLOSE issues ODATA-882, ODATA-908, ODATA-916, ODATA-913, ODATA-784, ODATA-785, ODATA-917, and ODATA-915 as applied

[10:28] Stefan: I second the motion

[10:28] Ralf Handl (SAP): Motion passes

[10:34] Ralf Handl (SAP): Next agenda item: V4.01 issues

[12:48] Stefan: Lunch break until 2pm CET

[12:49] Mike Pizzo1: Discussion of SET operations prior to lunch

[12:54] Stefan: Corresponding to date revision of minutes draft: https://www.oasis-open.org/committees/download.php/57665/odata-meeting-122_on-20160302_03-F2F_minutes.html

[12:56] Stefan: Page history, ... is history - sorry yesterdays link ... the fresh one is: https://www.oasis-open.org/committees/download.php/57672/odata-meeting-122_on-20160302_03-F2F_minutes.html

[14:04] Ralf Handl (SAP): Lunch break is over

[14:04] Ralf Handl (SAP): Next agenda item: extensions to URL conventions

[14:05] Ralf Handl (SAP): 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

[14:26] Mike Pizzo1: Proposal:

[14:26] Mike Pizzo1: can compare ordered collections: same members, same position

can compare unordered collections: same members, any order. don't expect this to work though...

can compare complex types by value (may fail if complex type contains unordered collection)

can compare two entities (as being the same reference)

  ex: Person(1)/BestFriend eq Person(2)/WorstEnemy

  ex: Person(1)/BestFriend eq {"@odata.id":"/People(1)"}

can compare entities to null:

  ex: Person(1)/BestFriend eq null

[14:26] Mike Pizzo1: I move we resolve as proposed

[14:26] Mark Biamonte (Progress): I second

[14:27] Mike Pizzo1: (restating) I move we resolve ODATA-617 as proposed

[14:27] Mark Biamonte (Progress): I second

[14:27] Ralf Handl (SAP): ODATA-617 is RESOLVED as proposed

[14:28] Mike Pizzo1: I propose we resolve ODATA-572 as a duplicate of ODATA-617

[14:28] Mark Biamonte (Progress): I second

[14:29] Ralf Handl (SAP): Objection: need to open it first

[14:29] Ralf Handl (SAP): ODATA-572 is OPEN

[14:29] Mike Pizzo1: I propose we resolve the now opened ODATA-572 as a duplicate of ODATA-617

[14:31] Mark Biamonte (Progress): I second

[14:31] Ralf Handl (SAP): ODATA-572 is RESOLVED as proposed

[14:37] Mike Pizzo1: I propose we further clarify the rules around comparing complex types containing navigation properties:

[14:37] Mike Pizzo1: -single-valued navigation properties reference the same entities

-any collections of entities compare as equal

   -if unordered, reference the same entities in any order

   -if ordered, reference the same entities in same order

[14:37] Mark Biamonte (Progress): I second

[14:38] Ralf Handl (SAP): Motion passes

[14:38] Ralf Handl (SAP): ODATA-897 Allow the count of a filtered/searched collection in common expressions (proposed)

[14:38] Stefan requests a private chat with you

[14:49] Ralf Handl (SAP): Already allowed:

[14:49] Ralf Handl (SAP): expandItem        = STAR [ ref / OPEN levels CLOSE ]

                  / expandPath

                    [ ref   [ OPEN expandRefOption   *( SEMI expandRefOption   ) CLOSE ]

                    / count [ OPEN expandCountOption *( SEMI expandCountOption ) CLOSE ]

[14:49] Ralf Handl (SAP): expandCountOption = filter

                  / search

[14:50] Mike Pizzo1: So we already support this in expand; we just can't use it in an _expression_ ($filter or $orderby)

[14:51] Ralf Handl (SAP): ODATA-897 is OPEN

[14:51] Mike Pizzo1: I move we resolve ODATA-897 as proposed

[14:51] Mark Biamonte (Progress): I second

[14:51] Ralf Handl (SAP): ODATA-897 is RESOLVED as proposed

[14:52] Ralf Handl (SAP): ODATA-888 Allow $search for all collections

[14:52] Ralf Handl (SAP): ODATA-888 is OPEN

[14:56] Mark Biamonte (Progress): I move that ODATA-888 be RESOLVED as proposed

[14:56] Mike Pizzo1: I second

[14:56] Ralf Handl (SAP): ODATA-888 is RESOLVED as proposed

[14:57] Ralf Handl (SAP): ODATA-901 substring: Define negative index for substring function

[14:57] Ralf Handl (SAP): ODATA-901 is OPEN

[15:09] Mike Pizzo1: Discussion of ODATA-901

[15:09] Mark Biamonte (Progress): I move we resolve ODATA-901 as proposed

[15:09] Gerald Krause (SAP): I second.

[15:09] Mike Pizzo1: Seems a useful shorthand, especially for long expressions.

[15:10] Ralf Handl (SAP): ODATA-901 is resolved as proposed

[15:10] Ralf Handl (SAP): ODATA-482 Allow inlining stream properties and media resources

[15:10] anonymous morphed into Ramesh Reddy(RedHat)

[15:23] Ram (Microsoft): Ralf, could you please admit me to the Adobe connect conference call? I am on the queue.

[15:24] Ralf Handl (SAP): Done

[15:28] Ralf Handl (SAP): http://services.odata.org/V4/OData/OData.svc/PersonDetails?$select=Photo&$format=application/json;odata.metadata=full

[15:41] Mike Pizzo1: Proposal:

[15:41] Mike Pizzo1: 1) Allow payloads to contain Base64-encoded streams

    a) GET response payloads

    b) POST/PUT/PATCH requests

    c) Delta payloads

2) Media streams in the payload are named using the name of the property

3) Media-entity stream is represented with a property named "$value"

4) Generalize $expand to also allow stream properties and represent the related content in Base64-encoded form.

For stream property: GET People(1)?$expand=photo

For media entity: GET Resumes(1)?$expand=$value

Expand=*  =>only navigation properties - streams are not included automatically by * but may be included explicitly.

[15:43] Ramesh Reddy(RedHat): I move ODATA-482 be resolved as proposed

[15:44] Mark Biamonte (Progress): I second

[15:44] Ralf Handl (SAP): ODATA-482 is resolved as proposed

[15:45] Ralf Handl (SAP): Break of 5 minutes

[16:22] Mike Pizzo1: Discussion on ODATA-881 and ODATA-838. Both provide similar extensibility.

[16:24] Mike Pizzo1: I move we approve ODATA-881 as proposed.

[16:25] Mark Biamonte (Progress): I second

[16:30] Ralf Handl (SAP): ODATA-881 is RESOLVED as proposed

[16:34] Mike Pizzo1: ODATA-881 addresses having untyped content. The only remaining issue from ODATA-883 is the ability have property names that were not valid OData identifiers (but may be legal in, i.e., JSON).

[16:36] Mike Pizzo1: I move we RESOLVE ODATA-838 without action.

[16:36] Stefan: I second

[16:36] Ralf Handl (SAP): ODATA-838 is CLOSED without action

[16:37] Mike Pizzo1: (note: in my comment on what ODATA-881 addresses, I meant ODATA-838, not 883.

[16:38] Stefan: @Mike: Thanks, already corrected in minutes.

[16:39] Mike Pizzo1: @Stefan; thanks!

[16:39] Mike Pizzo1: I move we resolve ODATA-887 with no action.

[16:39] Ramesh Reddy(RedHat): I second

[16:40] Ralf Handl (SAP): ODATA-887 is CLOSED without action

[16:44] Ralf Handl (SAP): ODATA-894 is OPEN

[16:44] Mike Pizzo1: I move we resolve ODATA-894 as proposed.

[16:44] Ramesh Reddy(RedHat): I second

[16:45] Ralf Handl (SAP): ODATA-894 is RESOLVED as proposed

[16:52] Ralf Handl (SAP): ODATA-895 is OPEN

[16:52] Stefan: Shared screen is black, mouse moving - but not a blocker for me (audio and chat working)

[16:56] Mike Pizzo1: I move we resolve ODATA-895 as proposed.

[16:56] Mark Biamonte (Progress)1: I second

[16:56] Ralf Handl (SAP): ODATA-895 is RESOLVED as proposed

[16:58] Stefan: Is currently ODATA-561   odata.type shouldn't require "#" for primitive types from Simplified Payload in discussion?

[17:03] Stefan: Shared screen visible again at my end #STefan

[17:03] Ralf Handl (SAP): ODATA-561 is OPEN

[17:04] Mark Biamonte (Progress)1: I move we resolve ODATA-561 as proposed

[17:04] Mike Pizzo1: I second

[17:04] Mike Pizzo1: (sorry Stefan; our connection to Adobe connect keeps coming and going)

[17:04] Ralf Handl (SAP): ODATA-561 is RESOLVED as proposed

[17:07] Ralf Handl (SAP): ODATA-630 is OPEN

[17:14] Ramesh Reddy(RedHat): I second

[17:15] Mark Biamonte (Progress)1: I move that ODATA-630 be resolved as proposed

[17:15] Ramesh Reddy(RedHat): I second

[17:15] Ralf Handl (SAP): ODATA-630 is resolved as proposed

[17:17] Stefan: @Ralf: Will there be some trace of ODATA-818 -  Omit properties whose value is null or the $metadata-defined default value in minutes?

[17:23] Mark Biamonte (Progress)1: I move that we resolve ODATA-813 as proposed

[17:23] Ralf Handl (SAP): ODATA-813 is OPEN

[17:24] Mark Biamonte (Progress)1: I move that we resolve ODATA-813 as proposed

[17:24] Ramesh Reddy(RedHat): I second

[17:24] Ralf Handl (SAP): ODATA-813 is RESOLVED as proposed

[17:27] Ralf Handl (SAP): ODATA-814 is OPEN

[17:28] Mark Biamonte (Progress)1: I move that ODATA-814 be resolved as proposed

[17:28] Mike Pizzo1: I second

[17:28] Ralf Handl (SAP): ODATA-814 is RESOLVED as proposed

[17:31] Ralf Handl (SAP): Next agenda item

[17:32] Ralf Handl (SAP): 11.Next meeting

c.Thursday March 10, 2016

[17:32] Stefan: Please one hint w.r.t. ODATA-818 ...?

[17:33] Stefan: Did we achieve progress during the meeting ...?

[17:33] Ralf Handl (SAP): No, too complicated

[17:33] Stefan: @Ralf: Thanks.

[17:38] Ralf Handl (SAP): Last agenda item: Any Other Business?

[17:38] Ralf Handl (SAP): None

[17:38] Ralf Handl (SAP): Meeting is adjourned

[17:38] Ralf Handl (SAP): Thank you and see you next week!

From: odata@lists.oasis-open.org [mailto:odata@lists.oasis-open.org] On Behalf Of Michael Pizzo
Sent: Mittwoch, 2. März 2016 02:21
To: odata@lists.oasis-open.org
Subject: [odata] Proposed Agenda for Face to Face OData TC meeting in Zurich on 2016-03-02 through 2016-03-03

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

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

Approve agenda [9:05am]

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

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

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

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]

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

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

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

OData extension for Temporal Data

Next meeting

Thursday March 17, 2016?

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

odata message