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 2019-03-14 - chat transcript


[15:46] Room information was updated by: Ralf Handl (SAP)
Here [1] is a draft agenda for the OData TC (Technical Committee) meeting scheduled on Thursday March 14, 2019 during 8-10 am PDT (16:00-18:00 CET). 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=47977 
 
2.Approve agenda [8:05 am PT]
 
3.Approve minutes from previous meeting(s) [8:10 am PT]
a.Minutes from March 07, 2019 TC meeting: not yet available 
 
4.Review action items [Action item list: https://www.oasis-open.org/apps/org/workgroup/odata/members/action_items.php?sort_field=due_closed_date] [8:15am PT]
a.Upcoming
i.#0037 Concept for Google Protocol Buffers as a data format  Hubert Heijkers  2019-03-28
b.In progress
i.#0036 Register the OData- headers and preferences with IANA  Mark Biamonte  2018-07-26
 
5.Issues [8:20 am PT]
a.APPLIED
i.ODATA-1289 Capabilities: use Edm.Boolean instead of Core.Tag as a type for properties
1.https://github.com/oasis-tcs/odata-vocabularies/pull/42/files 
ii.ODATA-1273 Define mapping of permission scopes to resources
1.https://github.com/oasis-tcs/odata-vocabularies/pull/35/files 
 
b.V4.01: NEW or OPEN
i.ODATA-1284 Allow referencing properties of "outer" entity in expressions nested within $expand
ii.ODATA-1292 CSDL 7.2.1 Nullable: improve wording
iii.ODATA-1291 ETags for Collections
iv.ODATA-1286 What is the meaning of year 0, and negative years
 
v.ODATA-1064 Add ability to annotate collections to return only count and NextLink
vi.ODATA-1005 Make sure we have capabilities for all new 4.01 functionality
 
c.Data Aggregation: NEW or OPEN
i.ODATA-1218 Transformations for recursive hierarchy processing
ii.ODATA-945 Correct examples 53 and 54
 
d.Vocabularies: NEW or OPEN with concrete proposal
i.ODATA-1287 Annotate a property as "late updatable"
ii.ODATA-1285 ODATA-1099 / Add ReadByKeyRestrictions similar to ReadRestrictions
1.https://github.com/oasis-tcs/odata-vocabularies/pull/41/files 
iii.ODATA-1264 CRUDQ descriptions on entity sets
1.https://github.com/oasis-tcs/odata-vocabularies/pull/40/files 
 
e.Vocabularies: NEW or OPEN that need more discussion
i.ODATA-1275 Describing and querying "JSON properties"
ii.ODATA-1214 Annotate constructor actions
iii.ODATA-1140 ODATA-884 / Add details to HttpResponse
iv.ODATA-1107 Introduce instance annotation to specify which types an instance "implements"
v.ODATA-1060 Improve specification of element response requirements
vi.ODATA-884 Allow describing possible responses to requests for a particular resource (public comment c201510e00019)
 
6.Next meetings [9:50 am PT]
a.Thursday March 21, 2019 during 8-10 am PDT (16:00-18:00 CET)  Europe still on winter time
b.Thursday March 28, 2019 during 8-10 am PDT (16:00-18:00 CET)  Europe still on winter time
c.Thursday April 04, 2019 during 8-10 am PDT (17:00-19:00 CET)
 
7.AOB and wrap up [9:55 am PT]
 
[2] References
Chat room: https://soaphub.org/conf/room/odatatc 
Conference call & Screen sharing: https://lync.co.sap.com/meet/ralf.handl/Q4QB1098 
Conference call details: https://www.oasis-open.org/apps/org/workgroup/odata/download.php/63673/latest/TC%20meeting%20dial-in%20details.htm 
 
[3] Timeline
https://www.oasis-open.org/committees/download.php/64563/TC%20Timeline%202019-01-23.docx

 

[16:01] Ralf Handl (SAP): Voting Members: 2 of 9 (22%) (used for quorum calculation)
[16:03] Ralf Handl (SAP): Voting Members: 3 of 9 (33%) (used for quorum calculation)
[16:06] Ralf Handl (SAP): Voting Members: 5 of 9 (55%) (used for quorum calculation)

 

[16:07] anonymous morphed into Hubert Heijkers (IBM)

 

[16:09] Ralf Handl (SAP): Achieved quorum: yes
[16:09] Ralf Handl (SAP): 2.Approve agenda [8:05 am PT]
[16:10] Ralf Handl (SAP): Propose to skip:
v.ODATA-1064 Add ability to annotate collections to return only count and NextLink
vi.ODATA-1005 Make sure we have capabilities for all new 4.01 functionality
[16:10] Ralf Handl (SAP): Instead do:
ii.ODATA-1285 ODATA-1099 / Add ReadByKeyRestrictions similar to ReadRestrictions
1.https://github.com/oasis-tcs/odata-vocabularies/pull/41/files 
iii.ODATA-1264 CRUDQ descriptions on entity sets
1.https://github.com/oasis-tcs/odata-vocabularies/pull/40/files
[16:10] Ralf Handl (SAP): Agenda is approved with these changes
[16:10] Ralf Handl (SAP): 3.Approve minutes from previous meeting(s) [8:10 am PT]
a.Minutes from March 07, 2019 TC meeting: not yet available
[16:10] Ralf Handl (SAP): 4.Review action items [Action item list: https://www.oasis-open.org/apps/org/workgroup/odata/members/action_items.php?sort_field=due_closed_date] [8:15am PT]
a.Upcoming
i.#0037 Concept for Google Protocol Buffers as a data format  Hubert Heijkers  2019-03-28
b.In progress
i.#0036 Register the OData- headers and preferences with IANA  Mark Biamonte  2018-07-26
[16:11] Ralf Handl (SAP): Feedback from Mark Nottingham on header registration
[16:12] Ralf Handl (SAP): Mike to follow up
[16:13] Ralf Handl (SAP): 5.Issues [8:20 am PT]
a.APPLIED
i.ODATA-1289 Capabilities: use Edm.Boolean instead of Core.Tag as a type for properties
1.https://github.com/oasis-tcs/odata-vocabularies/pull/42/files
[16:16] Ralf Handl (SAP): I move to merge https://github.com/oasis-tcs/odata-vocabularies/pull/42 and close ODATA-1289 as applied

 

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

 

[16:17] Ralf Handl (SAP): No objection, motion passes
[16:17] Ralf Handl (SAP): ii.ODATA-1273 Define mapping of permission scopes to resources
1.https://github.com/oasis-tcs/odata-vocabularies/pull/35/files
[16:22] Ralf Handl (SAP): <Property Name="RestrictedProperties" Type="Collection(Edm.PropertyPath)" >
[16:22] Ralf Handl (SAP): Hubert: can we reference dynamic properties here?
[16:22] Ralf Handl (SAP): Ralf: yes, why not
[16:24] Ralf Handl (SAP): Mike: open new issue to point out in CSDL that PropertyPath can reference dynamic properties
[16:25] Ralf Handl (SAP): Saurabh to update the pull request
[16:25] Ralf Handl (SAP): b.V4.01: NEW or OPEN
i.ODATA-1284 Allow referencing properties of "outer" entity in expressions nested within $expand
[16:25] Ralf Handl (SAP): https://issues.oasis-open.org/browse/ODATA-1284
[16:27] Ralf Handl (SAP): we could introduce aliases and use them:
 
GET Foo?$expand=Bar($alias=b;$expand=Baz($filter=Qux eq b/Qux))
[16:35] Ralf Handl (SAP): Mike: $previous instead of $outer?
[16:42] Ralf Handl (SAP): Hubert likes $alias better than $outer
[16:43] Ralf Handl (SAP): Mike: $alias would need precedence rules if the alias name already exists on that level
[16:47] Ralf Handl (SAP): Mike: $outer is more constraint and solves the problem at hand
[16:47] Ralf Handl (SAP): Mike: $outer is more constraint and solves the problem at hand
[16:47] Ralf Handl (SAP): Mike: $alias is more powerful and has bigger impact
[16:47] Ralf Handl (SAP): Postponed to next week
[16:47] Ralf Handl (SAP): Postponed to next week
[16:47] Ralf Handl (SAP): ii.ODATA-1292 CSDL 7.2.1 Nullable: improve wording
[16:47] Ralf Handl (SAP): https://issues.oasis-open.org/browse/ODATA-1292
[16:49] Ralf Handl (SAP): ODATA-1292 is OPEN

 

[16:49] Mike Pizzo (Microsoft): I move we resolve ODATA-1292 as proposed.

 

[16:49] Gerald Krause (SAP): I second.

 

[16:50] Ralf Handl (SAP): ODATA-1292 is RESOLVED as proposed
[16:50] Ralf Handl (SAP): ODATA-1292 is RESOLVED as proposed
[16:50] Ralf Handl (SAP): ODATA-1292 is RESOLVED as proposed
[16:50] Ralf Handl (SAP): ODATA-1292 is RESOLVED as proposed
[16:50] Ralf Handl (SAP): ODATA-1292 is RESOLVED as proposed
[16:50] Ralf Handl (SAP): iii.ODATA-1291 ETags for Collections
[16:50] Ralf Handl (SAP): https://issues.oasis-open.org/browse/ODATA-1291
[16:55] Ralf Handl (SAP): Hubert: always returning the @etag seems expensive
[16:55] Ralf Handl (SAP): Mike: could include @etag only if navigation property is selected or expanded
[17:09] Ralf Handl (SAP): 1.1.1 Header ETag
A response MAY include an ETag header, see [RFC7232]. Services MUST include this header if they require an ETag to be specified when modifying the resource.
Services MUST support specifying the value returned in the ETag header in an If-None-Match header of a subsequent Data Request for the resource. Clients MUST specify the value returned in the ETag header, or star (*), in an If-Match header of a subsequent Data Modification Request or Action Request in order to apply optimistic concurrency in updating, deleting, or invoking an action bound to the resource.
[17:18] Ralf Handl (SAP): 8.2.4 Header If-Match
As defined in [RFC7232], a client MAY include an If-Match header in a request to GET, PUT, PATCH or DELETE. The value of the If-Match request header MUST be an ETag value previously retrieved for the resource, or * to match any value.
If an operation on an existing resource requires an ETag, (see Core.OptimisticConcurrency in [OData-VocCore]) and the client does not specify an If-Match request header in a Data Modification Request or in an Action Request bound to the resource, the service responds with a 428 Precondition Required and MUST ensure that no observable change occurs as a result of the request.
[17:20] Ralf Handl (SAP): Maybe add new text to explain intention of optimistic concurrency
[17:20] Ralf Handl (SAP): - server decides whether to use it
[17:20] Ralf Handl (SAP): - if used, server must send ETags and should/must annotate metadata
[17:20] Ralf Handl (SAP): - if used, requests without if-match, or with non-matching ETag will fail
[17:21] Ralf Handl (SAP): - presence of ETag response header alone does not imply optimistic concurrency, ETag may just be for caching/conditional GET
[17:21] Ralf Handl (SAP): ODATA-1291 is OPEN
[17:36] Ralf Handl (SAP): I move to resolve ODATA-1291 with the updated proposal

 

[17:37] Mike Pizzo (Microsoft): I second

 

[17:37] Ralf Handl (SAP): ODATA-1291 is RESOLVED with the updated proposal
[17:39] Ralf Handl (SAP): d.Vocabularies: NEW or OPEN with concrete proposal
[17:39] Ralf Handl (SAP): ii.ODATA-1285 ODATA-1099 / Add ReadByKeyRestrictions similar to ReadRestrictions
1.https://github.com/oasis-tcs/odata-vocabularies/pull/41/files

 

[17:46] Mike Pizzo (Microsoft): Simpler may be to make ReadByKeyRestrictions as a property of ReadRestrictions?
[17:48] Mike Pizzo (Microsoft): Issue: ReadRestrictionsType would then be recursive.  Could solve with defining a base type for ReadByKeyRestrictions, or just say property doesn't apply when used in that context.

 

[17:49] Ralf Handl (SAP): Types:
[17:49] Ralf Handl (SAP): - ReadRestrictions as now
[17:49] Ralf Handl (SAP): - ReadCollectionRestrictions with base type ReadRestrictions and additional property ReadByKeyRestrictions of type ReadRestrictions

 

[17:50] Mike Pizzo (Microsoft): Saurabh: If there are ReadRestrictions and ReadByKeyRestrictions, how do they composed?
[17:51] Mike Pizzo (Microsoft): Mike: for simplicity, I would say that ReadByKeyRestrictions override ReadRestrictions, as opposed to compose.
[17:54] Mike Pizzo (Microsoft): We could say that only properties specified in ReadByKeyRestrictions replace any properties specified in ReadRestrictions.
[17:55] Mike Pizzo (Microsoft): Saurabh will take a stab at creating samples to compare different approaches.

 

[17:56] Ralf Handl (SAP): 6.Next meetings [9:50 am PT]
a.Thursday March 21, 2019 during 8-10 am PDT (16:00-18:00 CET)  Europe still on winter time
b.Thursday March 28, 2019 during 8-10 am PDT (16:00-18:00 CET)  Europe still on winter time
c.Thursday April 04, 2019 during 8-10 am PDT (17:00-19:00 CET)
[17:56] Ralf Handl (SAP): 7.AOB and wrap up [9:55 am PT]
[17:56] Ralf Handl (SAP): Meeting is adjourned

 

 

From: odata@lists.oasis-open.org <odata@lists.oasis-open.org> On Behalf Of Handl, Ralf
Sent: Mittwoch, 13. März 2019 10:57
To: odata@lists.oasis-open.org
Subject: [CAUTION] [odata] Agenda for OData TC meeting on 2019-03-14

 

Here [1] is a draft agenda for the OData TC (Technical Committee) meeting scheduled on Thursday March 14, 2019 during 8-10 am PDT (16:00-18:00 CET). 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]

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

 

2.        Approve agenda [8:05 am PT]

 

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

    1. Minutes from March 07, 2019 TC meeting: not yet available

 

4.        Review action items [Action item list: https://www.oasis-open.org/apps/org/workgroup/odata/members/action_items.php?sort_field=due_closed_date] [8:15am PT]

    1. Upcoming

                                  i.    #0037 Concept for Google Protocol Buffers as a data format – Hubert Heijkers – 2019-03-28

    1. In progress

                                  i.    #0036 Register the OData- headers and preferences with IANA – Mark Biamonte – 2018-07-26

 

5.        Issues [8:20 am PT]

    1. APPLIED

                                  i.    ODATA-1289 Capabilities: use Edm.Boolean instead of Core.Tag as a type for properties

        1. https://github.com/oasis-tcs/odata-vocabularies/pull/42/files

                                 ii.    ODATA-1273 Define mapping of permission scopes to resources

        1. https://github.com/oasis-tcs/odata-vocabularies/pull/35/files

 

    1. V4.01: NEW or OPEN

                                  i.    ODATA-1284 Allow referencing properties of "outer" entity in expressions nested within $expand

                                 ii.    ODATA-1292 CSDL 7.2.1 Nullable: improve wording

                                iii.    ODATA-1291 ETags for Collections

                                iv.    ODATA-1286 What is the meaning of year 0, and negative years

 

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

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

 

    1. Data Aggregation: NEW or OPEN

                                  i.    ODATA-1218 Transformations for recursive hierarchy processing

                                 ii.    ODATA-945 Correct examples 53 and 54

 

    1. Vocabularies: NEW or OPEN with concrete proposal

                                  i.    ODATA-1287 Annotate a property as "late updatable"

                                 ii.    ODATA-1285 ODATA-1099 / Add ReadByKeyRestrictions similar to ReadRestrictions

        1. https://github.com/oasis-tcs/odata-vocabularies/pull/41/files

                                iii.    ODATA-1264 CRUDQ descriptions on entity sets

        1. https://github.com/oasis-tcs/odata-vocabularies/pull/40/files

 

    1. Vocabularies: NEW or OPEN that need more discussion

                                  i.    ODATA-1275 Describing and querying "JSON properties"

                                 ii.    ODATA-1214 Annotate constructor actions

                                iii.    ODATA-1140 ODATA-884 / Add details to HttpResponse

                                iv.    ODATA-1107 Introduce instance annotation to specify which types an instance "implements"

                                 v.    ODATA-1060 Improve specification of element response requirements

                                vi.    ODATA-884 Allow describing possible responses to requests for a particular resource (public comment c201510e00019)

 

6.        Next meetings [9:50 am PT]

    1. Thursday March 21, 2019 during 8-10 am PDT (16:00-18:00 CET) – Europe still on winter time
    2. Thursday March 28, 2019 during 8-10 am PDT (16:00-18:00 CET) – Europe still on winter time
    3. Thursday April 04, 2019 during 8-10 am PDT (17:00-19:00 CET)

 

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

 

[2] References

 

[3] Timeline

 



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