RE: [odata] Agenda for OData TC meeting on 2016-10-13 - chat transcript

["Handl, Ralf" <ralf.handl@sap.com>]

Please change your name from 'anonymous' using the Settings button

[16:47] anonymous morphed into Ralf Handl (SAP SE)

[16:56] Room information was updated by: Stefan Hagen

Register: https://www.oasis-open.org/apps/org/workgroup/odata/event.php?event_id=41484  (please do so as usual, thanks).

Agenda draft: https://www.oasis-open.org/apps/org/workgroup/odata/email/archives/201610/msg00064.html

Minutes draft of previous meeting: https://www.oasis-open.org/committees/download.php/59098/odata-meeting-147_on-20161006-minutes.html

 

[16:56] Stefan Hagen: ParticipationInfo from kava Voting Members: 3 of 12 (25%) (used for quorum calculation)

[17:00] Stefan Hagen: ... Voting Members: 5 of 12 (41%) (used for quorum calculation)

[17:04] Stefan Hagen: ... Voting Members: 7 of 12 (58%) (used for quorum calculation)

[17:04] Stefan Hagen: quorate ...

 

[17:04] Ralf Handl (SAP SE): 2.Approve agenda [8:05 am PT]

[17:05] Ralf Handl (SAP SE): Add new Jira issue  https://issues.oasis-open.org/browse/ODATA-986 to agenda item #5

[17:06] Ralf Handl (SAP SE): No further changes, agenda is approved

[17:07] Ralf Handl (SAP SE): 3.Approve minutes from previous meeting(s) [8:10 am PT]

a.Minutes from October 06, 2016 TC meeting: https://www.oasis-open.org/committees/download.php/59098/odata-meeting-147_on-20161006-minutes.html

[17:08] Ralf Handl (SAP SE): Minutes are approved

[17:08] Ralf Handl (SAP SE): 4.Review action items [Action item list: https://www.oasis-open.org/apps/org/workgroup/odata/members/action_items.php] [8:15am PT]

a.Action items due

i.#0036 Register the OData- headers and preferences with IANA

[17:09] Ralf Handl (SAP SE): @Mike: dial-back goes to your answering machine

 

[17:09] Mike Pizzo: Sorry; Skype issues.  I'm in now...

 

[17:13] Ralf Handl (SAP SE): 5.V4.01 [9:20 am PT]

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

[17:14] Ralf Handl (SAP SE): https://issues.oasis-open.org/browse/ODATA-986

[17:14] Ralf Handl (SAP SE): Support POST to cast segment following a collection

[17:16] Ralf Handl (SAP SE): ODATA-986 is OPEN

 

[17:17] Mike Pizzo: I move we resolve ODATA-986 as proposed.

[17:20] Mike Pizzo: Mark asks about DELETE; it should be the same semantics.

[17:20] Mike Pizzo: Updated proposal:

[17:20] Mike Pizzo: Support posting/deleting to a type cast segment following a collection. 

For Post, the payload must be an instance of the type specified by the cast segment (or a type derived from the type specified by the cast segment) and does not require the @odata.type attribute unless it is of a derived type of the type specified in the type cast segment.

For DELETE, only those instances matching or derived from the cast segment are deleted.

[17:22] Mike Pizzo: For PATCH/DELETE, only those instances matching or derived from the cast segment are updated/deleted.

[17:25] Mike Pizzo: I move we resolve ODATA-986 according to the updated proposal: 

Support posting/deleting to a type cast segment following a collection. 

For Post, the payload must be an instance of the type specified by the cast segment (or a type derived from the type specified by the cast segment) and does not require the @odata.type attribute unless it is of a derived type of the type specified in the type cast segment. 

For PATCH/DELETE, only those instances matching or derived from the cast segment are updated/deleted.

 

[17:25] Hubert Heijkers: I second

 

[17:26] Ralf Handl (SAP SE): ODATA-986 is RESOLVED with the revised proposal

[17:26] Ralf Handl (SAP SE): i.OData CSDL

1.ODATA-743 Restructure Part 3: CSDL into CSDL Core, CSDL XML, and CSDL JSON

[17:28] Ralf Handl (SAP SE): ODATA-743 is OPEN

 

[17:41] Mike Pizzo: If we only publish the CSDL XML document for now, we may have to fix references from Parts 1 (and Part 2?) that currently reference Part 3.

 

[17:43] Ralf Handl (SAP SE): Mike to check how this affects Part 1 and Part 2

 

[17:47] Mike Pizzo: Goals:

0) Make sure both formats define the same data model

1) Not have to mantain same text in multiple places

2) Not require someone who cares about JSON have to read XML (and vice-versa)

3) Reduce number of documents someone has to read to understand OData

4) Reduce amount of text someone has to read to understand OData

 

[17:52] Ralf Handl (SAP SE): Ralf to prepare a preview of an XML-only format document without consistency rules

[17:52] Ralf Handl (SAP SE): 2.ODATA-959 Allow path in an edm:key to also use a primitive property of a non null-able navigation property (recursively) of the entity type.

[17:53] Ralf Handl (SAP SE): ODATA-959 is OPEN

[17:53] Ralf Handl (SAP SE): Allow the path _expression_ to include references to primitive properties of non null-able navigation properties (recursively). 

8.3.1 Attribute Name could be simply amended as in: 

The edmropertyRef element MUST specify a value for the Name attribute which MUST be a path _expression_ resolving to a primitive property of the entity type itself or to a primitive property of a complex or navigation property (recursively) of the entity type. The names of the properties in the path are joined together by forward slashes.

[18:12] Ralf Handl (SAP SE): Hubert to refine the proposal and add rules on default responses in case no specific metadata level or $expand/$select is requested

[18:12] Ralf Handl (SAP SE): ii.OData JSON Format

1.ODATA-982 Chapter 11: Annotations on properties in single-property messages

#

[18:13] Ralf Handl (SAP SE): As the property name is not part of the single-property response and the property's value is represented as 

  "value": <property value> 

the annotations should be next to "value" and not prefixed with "value": 

  "@Namespace.Term": <annotation value> 

  "value": <property value>

[18:19] Ralf Handl (SAP SE): Same pattern that is already used for @odata.count

[18:19] Ralf Handl (SAP SE): ODATA-982 is OPEN

 

[18:20] Mike Pizzo: Note that structured properties may still be internally annotated, just as they would in an entity response.

 

[18:20] Ralf Handl (SAP SE): Pattern only applies to primitive properties and collection-valued properties

 

[18:21] Mike Pizzo: Added to proposal: "For primitive/collection-valued properties:

"

 

[18:21] Hubert Heijkers: I move to resolve ODATA-982 as per the amended proposal

 

[18:21] Martin Zurmuehl (SAP): I second

 

[18:22] Ralf Handl (SAP SE): ODATA-982 is RESOLVED with the amended proposal

[18:22] Ralf Handl (SAP SE): 2.ODATA-983 Chapter 15/16: advertise actions on collection-valued properties

[18:22] Ralf Handl (SAP SE): Prefix the advertisement with the navigation property name and place it next to the navigation property, similar to annotations on navigation properties: 

  "NavProp#Model.SomeAction": { 

    "title": "Do Something", 

    "target": "Managers(22)/Employees/DoSomething" 

    }, 

    "NavProp": [ ... ]

[18:23] Ralf Handl (SAP SE): ODATA-983 is OPEN

[18:24] Ralf Handl (SAP SE): Mike: use cases

[18:24] Ralf Handl (SAP SE): - non-canonical action URL

[18:24] Ralf Handl (SAP SE): - instance-dependent applicability

[18:34] Ralf Handl (SAP SE): Pack this with ODATA-978 in a change set

 

[18:34] Mike Pizzo: Advertise non-availability by providing null as the advertisement value: 

"#Model.FirstAction": {} --> available 

"#Model.SecondAction": null --> not available

 

[18:39] Ralf Handl (SAP SE): Amended proposal: return only first form (available) for 4.0 responses

 

[18:39] Mike Pizzo: Note that services must only return the null value in a 4.01 or greater response.

[18:43] Mike Pizzo: I move we resolve ODATA-978 as proposed.

 

[18:43] Martin Zurmuehl (SAP): I second

 

[18:44] Ralf Handl (SAP SE): ODATA-978 is RESOLVED with the amended proposal

 

[18:53] Mike Pizzo: Question: when does this appear?

1) Only when expanded?

2) Only when expanded and selected?

3) If I expand and select only action, do I have the object or just the action advertisement?

[18:54] Mike Pizzo: (related to advertising actions on collection/primitive values in ODATA-983)

 

[18:57] Ralf Handl (SAP SE): 6.Next meetings [9:50 am PT]

a.Thursday October 20, 2016 during 8-10 am PT?

a.Thursday October 27, 2016 during 8-12 am PT?

[18:59] Ralf Handl (SAP SE): Both proposed meeting slots are accepted

[18:59] Ralf Handl (SAP SE): 7.AOB and wrap up [9:55 am PT]

[18:59] Ralf Handl (SAP SE): Meeting is adjourned

 

 

From: odata@lists.oasis-open.org [mailto:odata@lists.oasis-open.org] On Behalf Of Handl, Ralf
Sent: Mittwoch, 12. Oktober 2016 11:06
To: odata@lists.oasis-open.org
Subject: [odata] Agenda for OData TC meeting on 2016-10-13

 

Here [1] is a draft agenda for the OData TC (Technical Committee) meeting scheduled on Thursday October 13, 2016 during 8-10 am 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:00 am PT]

a.     Self-registration link: https://www.oasis-open.org/apps/org/workgroup/odata/event.php?event_id=41484

 

2.        Approve agenda [8:05 am PT]

 

3.        Approve minutes from previous meeting(s) [8:10 am PT]

a.     Minutes from October 06, 2016 TC meeting: https://www.oasis-open.org/committees/download.php/59098/odata-meeting-147_on-20161006-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]

a.     Action items due

                                  i.    #0036 Register the OData- headers and preferences with IANA

 

5.        V4.01 [9:20 am PT]

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

                                  i.    OData CSDL

1.     ODATA-743 Restructure Part 3: CSDL into CSDL Core, CSDL XML, and CSDL JSON

2.     ODATA-959 Allow path in an edm:key to also use a primitive property of a non null-able navigation property (recursively) of the entity type.

                                 ii.    OData JSON Format

1.     ODATA-982 Chapter 11: Annotations on properties in single-property messages

2.     ODATA-983 Chapter 15/16: advertise actions on collection-valued properties

                                iii.    Interfaces

1.     ODATA-619 Attach action and function signatures to terms, i.e. make a term definition an interface definition

                                iv.    Waiting for refined proposal

1.     ODATA-557 Allow exponential notation for Edm.Decimal

2.     ODATA-618 Allow using term names in positions that allow type names

3.     ODATA-674 Specify navigation property binding combined with containment

4.     ODATA-735 Enhance the CSDL for instance annotations

5.     ODATA-760 Add to depth restrictions to Capabilities Vocabulary

6.     ODATA-811 Define propagation and (partial) overriding of annotations

7.     ODATA-817 Add client-side function odata.matchesRegularExpression

8.     ODATA-854 Consider use of OPTIONS for discovering formats, other capabilities and features

9.     ODATA-868 Describe HTTP encoding for streamed requests and responses

10.  ODATA-879 Support Arrays of Arrays

11.  ODATA-884 Add term ErrorCodes to describe possible codes in error messages (public comment c201510e00019)

12.  ODATA-919 Specify the result type for each operation based on operator types

13.  ODATA-920 Specify overflow for int data types (-INF, INF, NaN)

14.  ODATA-923 $expand (or $include) for $metadata to include referenced schemas

15.  ODATA-950 Clarify what requests can be delta enabled

16.  ODATA-964 Need to clarify nested delta representation

17.  ODATA-965 UpdateGeoJSON Reference to RFC7946

18.  ODATA-966 13.4 Add example for navigation property bindings for containment navigation property

19.  ODATA-969 Chapter 15, Example 32: syntax of "target" URL

20.  ODATA-974 Flesh out recommendations around OAuth support in OData

21.  ODATA-976 Support partial keys

22.  ODATA-978 New annotation for availability/advertisement of bound actions/functions

23.  ODATA-979 Recursive containment navigation properties and Partner attribute

24.  ODATA-980 SchemaVersion header, $SchemaVersion query option, or root URL versioning

25.  ODATA-985 The HTTP Specification document referenced in the OData Protocol Spec has been obsoleted

 

6.        Next meeting [9:50 am PT]

a.     Thursday October 20, 2016 during 8-10 am PT?

 

7.        AOB and wrap up [9:55 am 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