RE: [odata] Agenda for OData TC meeting on 2017-11-02

[Michael Pizzo <mikep@microsoft.com>]

Slightly edited Chat transcript:

Note: We had issues with the oasis site (for registration) and the normal bridge (didn't have the host code) so we moved to Hubert's bridge and Mike updated attendance after the meeting.

[8:02] Michael Pizzo: Ralf is on vacation, so I will Chair today.  As nobody seems to be able to access the 

 

[8:09] Michael Pizzo: We have quorum with 7/12

 

[8:13] Michael Pizzo: Moving over to Hubert's bridge... see you all there! (and here...)

[8:16] Michael Pizzo: In attendance: George, Gerald, Hubert, Mark, Martin, Matt, Ted, Sefan, and Mike

[8:19] Michael Pizzo: Ramesh has joined. 10/12 voting members.

[8:21] Michael Pizzo: Proposed agenda:

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

2.Approve agenda [8:05 am PT]

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

a.Not yet available

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

5.Issues [8:20 am PT]

a.V4.01 Public Review

i.ODATA-1126 Remove a Reference to an Entity (public review comment c201710e00005)

ii.ODATA-1127 clarify support for navigation properties on deleted entries

iii.ODATA-1128 Clarify function imports in $filter and $orderby

b.Vocabularies: APPLIED

i.ODATA-1064 Add ability to annotate collections to return only count and NextLink

c.Vocabularies: NEW or OPEN

i.ODATA-1124 Authorization vocabulary: KeyLocation - also allow cookie as value?

ii.ODATA-1122 Add singletons for capability term targets

iii.ODATA-1121 Extend FilterExpressionRestrictions with "MultiPredicate"

iv.ODATA-1067 Consider ability to define computed default values

v.ODATA-1005 Make sure we have capabilities for all new 4.01 functionality

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

6.Committee Note on Google Protocol Buffers as an alternative data format [9:30 am PT]

a.George: describe use case and purpose of the proposed committee note

7.Structural Property with Type=Entity Type versus Containment Navigation Property [9:40 am PT]

a.George: describe use case and why containment navigation properties arent sufficient

8.Next meetings [9:50 am PT]

a.Thursday November 09, 2017 during 8-10 am PST (17:00-19:00 CET)

9.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/download.php/61677/TC%20Timeline-2017-09-29.docx

 

[8:23] George Ericson (Dell): Reminder, I need to leave before the first hour is finished.

On 6: A relatively quick look says a lossy transformation from CSDL to protocol buffers is straight forward.  A number of potential clients would like this format.  If this is amenable to a style sheet transform, then we should make that available.

On 7: NavigationProperty has two forms and semantics depending on whether the ContainsTarget attribute is true or false.  Syntactically, when true, the definition is exactly like an EntitySet or Singleton, depending on the presence of Collection.   Thus, really not navigation  When false, the declaration really is equivalent to a UML AssociationEnd.  In the long-run, the meta-model for CSDL is simpler if we do not conflate these two uses.

 

[8:26] Michael Pizzo: Hubert: in investigating this type of interface in the past, knowing the size (particularly of arrays) in advance seemed to be a problem.

[8:26] Michael Pizzo: George: Perhaps can use server side paging?

[8:27] Michael Pizzo: Hubert: issue is performance, particularly converting numbers to strings (in json) and back to doubles.

 

[8:31] Stefan: @Mike: I did upload the minutes from the previous meting last week already and the usual public link is https://www.oasis-open.org/committees/download.php/61889/odata-meeting-193_on-20171026-minutes.html

[8:31] Stefan: Published 2017-OCT- 26

 

[8:34] Michael Pizzo: Minutes are approved.

[8:35] Michael Pizzo: i.ODATA-1126 Remove a Reference to an Entity (public review comment c201710e00005)

 [8:36] Michael Pizzo: https://issues.oasis-open.org/browse/ODATA-1126

[8:36] Michael Pizzo: DELETE http://host/service/Customers(1)/Orders/$ref?$id=../../Orders(4711)

[8:37] Michael Pizzo: Alternate: DELETE http://host/service/Customers(1)/Orders(4711)/$ref

[8:38] Michael Pizzo: DELETE http://host/service/Customers(1)/BestFriend/$ref

[8:42] Michael Pizzo: GET http://host/service/Customers(1)/BestFriend/$ref returns {"@odata.id":"Customers(5)"}

[8:44] Michael Pizzo: DELETE http://host/service/Customers(1)/BestFriend deletes the best friend.

 

[8:56] George Ericson (Dell): I move to accept OData-1126 as proposed.

 

[8:56] Michael Pizzo: Hubert: don't like it, but consistent with singleton case (which he also doesn't care for)

 

[8:56] Hubert Heijkers (IBM): I second

 

[8:56] Michael Pizzo: Mike: Tend to agree. Better syntax, and more consistent, but kinda rubs me wrong...

[8:57] Michael Pizzo: OData-1126 resolved as proposed.

[8:57] Michael Pizzo: https://issues.oasis-open.org/browse/ODATA-1127

[9:07] Michael Pizzo: Matt: are there other ways to do this?

[9:08] Michael Pizzo: Mike: yes, in a flattened manner.  However, we are moving from a flattened representation to the nested representation because it is a more natural representation and in many cases significantly more efficient.

[9:08] Michael Pizzo: Matt: useful (and consistent) in update case.  Maybe not as useful in client case, if the related things are going to be orphaned anyway.

 

[9:09] Matt Borges (SAP): I move to accept OData-1127 as proposed.

 

[9:09] Hubert Heijkers (IBM): I second

 

[9:10] Michael Pizzo: OData-1127 is resolved as proposed.

[9:10] Michael Pizzo: https://issues.oasis-open.org/browse/ODATA-1128

[9:14] Michael Pizzo: I think the text was introduced before we introduced $root, and was intended to differentiate between function imports (which are called from the root) and unbound functions (which can be invoked in a $filter or $orderby as a "global" function.)

[9:15] Michael Pizzo: i.e., syntactically, the function import has to be prefixed with the container.  A function import "binds" the function to the container.

[9:20] Michael Pizzo: Proposal from issue: 

Remove this sentence, or change to 

Function imports can be used inside $filter or $orderby if preceded by the $root literal, see [OData-URL].

 

[9:21] Mark Biamonte (Progress)1: I move that OData-1128 be resoved by making the change specified in the proposal

 

[9:21] Hubert Heijkers (IBM): I second

 

[9:22] Michael Pizzo: OData-1128 is resolved as proposed.

[9:23] Michael Pizzo: https://issues.oasis-open.org/browse/ODATA-1124

[9:26] Michael Pizzo: Mark: is passing security information in a cookie necessarily a good practice?  if not, do we want to encourage it?

[9:28] Michael Pizzo: https://issues.oasis-open.org/browse/ODATA-1122

[9:32] Michael Pizzo: ODATA-1122 is open.

 

[9:33] Hubert Heijkers (IBM): I move to resolve ODATA-1122 with direction to the editors to apply as appropriate and the application be reviewed when approving the changes.

 

[9:33] Mark Biamonte (Progress)1: i second

 

[9:34] Michael Pizzo: OData-1122 is resolved as proposed.

[9:34] Michael Pizzo: https://issues.oasis-open.org/browse/ODATA-1121

[9:35] Michael Pizzo: OData-1121 is held over to next week.

[9:40] Michael Pizzo: OData-884 example:

<Annotation Term="Core.ErrorCodes"> 

<Collection> 

<Record> 

<PropertyValue Property="HttpMethod" String="GET" /> 

<PropertyValue Property="HttpStatusCode" String="400" /> 

<PropertyValue Property="ODataErrorCode" String="QueryFilterFunctionNotSupported" /> 

<PropertyValue Property="Description" 

String="This error indicates that a request was made with a filter function that isnt supported on this entity set. Please refer to the Capabilities.FilterFunctions annotation on this entity set for a list of supported functions, and the exact error message for which function usage triggered this error." /> 

</Record> 

</Collection> 

</Annotation>

[9:45] Michael Pizzo: Questions on proposal: Do we need, then, to define a set of ODataErrorCodes?

[9:46] Michael Pizzo: Other questions from issue comments: Would reorganizing (perhaps hierarchically) work better?

[9:46] Michael Pizzo: Document for OpenAPI mapping: https://www.oasis-open.org/apps/org/workgroup/odata/download.php/61852/latest

[9:53] Michael Pizzo: Discussion on adding version to vocabularies:5.2.1 Proposal: annotate vocabulary schemas with Core.SchemaVersion to make different revisions distinguishable

Major version is 1 will only be changed if we switch to Xxx.V2

Minor version is incremented whenever we add a term, property, or AppliesTo target

Patch version is incremented whenever we fix something typos, descriptions,

[9:55] Michael Pizzo: Next meeting: Thursday November 09, 2017 during 8-10 am PST (17:00-19:00 CET)

[9:58] Michael Pizzo: Meeting adjourned 9:58pm PT

 

 

From: odata@lists.oasis-open.org [mailto:odata@lists.oasis-open.org] On Behalf Of Handl, Ralf
Sent: Friday, October 27, 2017 4:10 AM
To: odata@lists.oasis-open.org
Subject: [odata] Agenda for OData TC meeting on 2017-11-02

 

Here [1] is a draft agenda for the OData TC (Technical Committee) meeting scheduled on Thursday November 02, 2017 during 8-10 am PDT (16:00-18:00 CET – back to “normal” time in Europe, i.e. meeting is one hour earlier for Europeans). 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.

 

This meeting will be moderated by Mike Pizzo.

 

Thanks.

 

[1] Agenda

 

1.        Roll call [8:00 am PT]

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

 

2.        Approve agenda [8:05 am PT]

 

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

1. Not yet available

 

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.        Issues [8:20 am PT]

1. V4.01 Public Review

                                  i.    ODATA-1126 Remove a Reference to an Entity (public review comment c201710e00005)

                                 ii.    ODATA-1127 clarify support for navigation properties on deleted entries

                                iii.    ODATA-1128 Clarify function imports in $filter and $orderby

 

2. Vocabularies: APPLIED

                                  i.    ODATA-1064 Add ability to annotate collections to return only count and NextLink

 

3. Vocabularies: NEW or OPEN

                                  i.    ODATA-1124 Authorization vocabulary: KeyLocation - also allow cookie as value?

                                 ii.    ODATA-1122 Add singletons for capability term targets

                                iii.    ODATA-1121 Extend FilterExpressionRestrictions with "MultiPredicate"

                                iv.    ODATA-1067 Consider ability to define computed default values

                                 v.    ODATA-1005 Make sure we have capabilities for all new 4.01 functionality

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

 

6.        Committee Note on Google Protocol Buffers as an alternative data format [9:30 am PT]

1. George: describe use case and purpose of the proposed committee note

 

7.        Structural Property with Type=Entity Type versus Containment Navigation Property [9:40 am PT]

1. George: describe use case and why containment navigation properties aren’t sufficient

 

8.        Next meetings [9:50 am PT]

1. Thursday November 09, 2017 during 8-10 am PST (17:00-19:00 CET)

 

9.        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/download.php/61677/TC%20Timeline-2017-09-29.docx