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-07-18 - chat transcript


[‎18.‎07.‎2019 17:02] 

Voting Members: 3 of 10 (30%) (used for quorum calculation) 

 

[‎18.‎07.‎2019 17:03] 

Voting Members: 4 of 10 (40%) (used for quorum calculation) 

 

[‎18.‎07.‎2019 17:04] 

Voting Members: 5 of 10 (50%) (used for quorum calculation) 

This message wasn't sent to Ericson, George.

[‎18.‎07.‎2019 17:04] 

Voting Members: 6 of 10 (60%) (used for quorum calculation) 

 

[‎18.‎07.‎2019 17:04] 

Voting Members: 7 of 10 (70%) (used for quorum calculation) 

 

[‎18.‎07.‎2019 17:04] 

Voting Members: 8 of 10 (80%) (used for quorum calculation) 

 

[‎18.‎07.‎2019 17:04] 

Quorum achieved: yes!

 

[‎18.‎07.‎2019 17:05] 

     1. Roll call [8:00 am]

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

 

[‎18.‎07.‎2019 17:05] 

     2. Approve agenda [8:05 am]

 

[‎18.‎07.‎2019 17:05] 

Agenda is approved

 

[‎18.‎07.‎2019 17:05] 

     3. Approve minutes from previous meeting(s)

          a. Minutes from July 11, 2019 TC meeting: https://www.oasis-open.org/committees/download.php/65603/Minutes%20of%202019-07-11%20Meeting%20%23264.docx 

 

[‎18.‎07.‎2019 17:06] 

Minutes are approved

 

[‎18.‎07.‎2019 17:06] 

     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:15 am]

          a. Upcoming

              i.   #0039 Concept for Compact JSON data format – Hubert Heijkers – 2019-10-31

              ii.  #0037 Concept for binary data format – Hubert Heijkers – 2020-03-26

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

 

[‎18.‎07.‎2019 17:08] 

Mike: register odata-prefixed versions of headers and preferences

 

[‎18.‎07.‎2019 17:09] 

No objections, move forward registering only the prefixed versions

 

[‎18.‎07.‎2019 17:11] 

    5. Issues [8:20 am]

         a. APPLIED

              i.   ODATA-1304 Improve descriptions on Capabilities.NavigationRestrictionsType

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

 

[‎18.‎07.‎2019 17:15]  Mike Pizzo: 

I move we accept the application of https://github.com/oasis-tcs/odata-vocabularies/pull/51/files and close ODATA-1304 as applied.

 

[‎18.‎07.‎2019 17:15]  Ericson, George: 

Second

 

[‎18.‎07.‎2019 17:15] 

No objections, motion passes

 

[‎18.‎07.‎2019 17:15] 

              ii.  ODATA-1316 Should support multiple permissions for read/write

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

 

[‎18.‎07.‎2019 17:18]  Hubert Heijkers: 

I move we accept the application of https://github.com/oasis-tcs/odata-vocabularies/pull/54/files and close ODATA-1316 as applied

 

[‎18.‎07.‎2019 17:18]  Ericson, George: 

Second

 

[‎18.‎07.‎2019 17:18] 

No objections, motion passes

 

[‎18.‎07.‎2019 17:19] 

         b. V4.01: NEW or OPEN

              i.   ODATA-1321 Prefer:respond-async on individual requests within a batch request

 

[‎18.‎07.‎2019 17:21] 

ODATA-1321 is OPEN

 

[‎18.‎07.‎2019 17:29] 

George: would be nice to have sequence diagrams for the different cases of processing a batch request

 

[‎18.‎07.‎2019 17:41] 

Relax processing of dependent requests to "may be executed async even without preference!

 

[‎18.‎07.‎2019 17:41]  Hubert Heijkers: 

If an individual request depends on a request that is executed asynchronously, then the dependent request MAY also executed asynchronously even if it does not specify the respond-async preference, or the service may respond with a 412 Precondition Failed.

 

[‎18.‎07.‎2019 17:44] 

Or some other 4xx that matches the use case, e.g. 424 Failed Dependency

 

[‎18.‎07.‎2019 17:44]  Hubert Heijkers: 

I'd be tempted to say that having a dependent request without a respond-async header be dependent on a request that has that preference is by itself a invalid request.

 

[‎18.‎07.‎2019 17:54]  Mike Pizzo: 

The issue is not with having an async request within a batch, the issue is with having a dependency on an async request.

It doesn't sound like anyone has requirements to support dependencies on async requests, so simplest may be to disallow declaring dependencies on an async request.

 

[‎18.‎07.‎2019 17:56]  Mike Pizzo: 

we can only allow this in a json batch response. not allowed as part of a changeset.

 

[‎18.‎07.‎2019 18:00] 

Remove third and last sentence in 8.2.8.8 Preference respond-async

The action couldn’t be completed. Please try again later.

[‎18.‎07.‎2019 18:00] 

Add text stating the restrictions in sections on multipart batch response

The action couldn’t be completed. Please try again later.

[‎18.‎07.‎2019 18:01] 

In JSON Format: forbid respond-async for requests that have a dependency or are within a change set

The action couldn’t be completed. Please try again later.

[‎18.‎07.‎2019 18:03] 

Mike: shorten third paragraph to "The respond-async preference MAY be used for batch requests."

The action couldn’t be completed. Please try again later.

[‎18.‎07.‎2019 18:04] 

The respond-async preference MAY be used for batch requests, in which case it applies to the batch request as a whole and not to individual requests within the batch.

The action couldn’t be completed. Please try again later.

[‎18.‎07.‎2019 18:05]  Mike Pizzo: 

In Protocol: preference respond-async, remove references to use for single requests within a batch; clarify that use on a batch applies to the entire batch:
"The respond-async preference MAY be used for batch requests, in which case it applies to the batch request as a whole and not to individual requests within the batch."

In description of multipart batch, prohibit use of respond-async for individual requests within a batch

In JSON Format, allow use of respond-async for individual requests as long as they are not within an atomicity group and have no dependencies

 

[‎18.‎07.‎2019 18:07]  Mike Pizzo: 

In JSON Format, allow use of respond-async for individual requests as long as they are not within an atomicity group and nothing depends on it.

 

We saved this conversation. You'll see it soon in the Conversations tab in Skype for Business and in the Conversation History folder in Outlook.

[‎18.‎07.‎2019 18:11]  Mike Pizzo: 

Modified JSON description: In JSON Format, allow use of respond-async for individual requests as long as they are not within an atomicity group. If a request depends on a request that is executed asynchronously, then it should fail with 424 failed dependency.

 

[‎18.‎07.‎2019 18:11]  Hubert Heijkers: 

I propose to resolve ODATA-1321 as per the amended proposal

 

[‎18.‎07.‎2019 18:12]  Ericson, George: 

Second

 

[‎18.‎07.‎2019 18:12] 

ODATA-1321 is RESOLVED as proposed

 

[‎18.‎07.‎2019 18:13] 

              ii.  ODATA-1320 edm.xsd: attribute edm:Annotations/@Target does not cover all allowed targets

                   1. https://github.com/oasis-tcs/odata-csdl-schemas/pull/7/files 

 

[‎18.‎07.‎2019 18:17] 

miscellaneous.xml 513-515 is nonsense, remove (can't annotate a parameter of a parameter-less overload)

 

[‎18.‎07.‎2019 18:18] 

Same for 504-506

 

[‎18.‎07.‎2019 18:18]  Mike Pizzo: 

Correction: 531-533 and 504-506 should be removed.

 

[‎18.‎07.‎2019 18:19] 

    6. Next meetings [9:50 am]

         a.  Thursday July 25, 2019 during 8-10 am PDT (17:00-19:00 CEST)

         b.  Thursday September 12, 2019 during 8-10 am PDT (17:00-19:00 CEST)

         c.  Thursday September 19, 2019 during 8-10 am PDT (17:00-19:00 CEST)

 

[‎18.‎07.‎2019 18:20] 

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

 

[‎18.‎07.‎2019 18:20] 

Meeting is adjourned!

 

 

 

From: odata@lists.oasis-open.org <odata@lists.oasis-open.org> On Behalf Of Handl, Ralf
Sent: Mittwoch, 17. Juli 2019 17:39
To: odata@lists.oasis-open.org
Subject: [CAUTION] [odata] Agenda for OData TC meeting on 2019-07-18

 

Here [1] is a draft agenda for the OData TC (Technical Committee) meeting scheduled on Thursday July 18, 2019 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]

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

 

     2. Approve agenda [8:05 am]

 

     3. Approve minutes from previous meeting(s)

          a. Minutes from July 11, 2019 TC meeting: https://www.oasis-open.org/committees/download.php/65603/Minutes%20of%202019-07-11%20Meeting%20%23264.docx

 

     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:15 am]

          a. Upcoming

              i.   #0039 Concept for Compact JSON data format – Hubert Heijkers – 2019-10-31

              ii.  #0037 Concept for binary data format – Hubert Heijkers – 2020-03-26

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

 

    5. Issues [8:20 am]

         a. APPLIED

              i.   ODATA-1304 Improve descriptions on Capabilities.NavigationRestrictionsType

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

              ii.  ODATA-1316 Should support multiple permissions for read/write

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

 

         b. V4.01: NEW or OPEN

              i.   ODATA-1321 Prefer:respond-async on individual requests within a batch request

              ii.  ODATA-1320 edm.xsd: attribute edm:Annotations/@Target does not cover all allowed targets

                   1. https://github.com/oasis-tcs/odata-csdl-schemas/pull/7/files

 

         c. Vocabularies: NEW or OPEN that need more discussion

              i.   ODATA-1300 Capabilities: clarify CountRestrictions and ExpandRestrictions

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

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

              iii.  ODATA-1214 Annotate constructor actions

              iv. ODATA-1140 Add details to HttpResponse

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

              vi. ODATA-1060 Improve specification of element response requirements

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

 

    6. Next meetings [9:50 am]

         a.  Thursday July 25, 2019 during 8-10 am PDT (17:00-19:00 CEST)

         b.  Thursday September 12, 2019 during 8-10 am PDT (17:00-19:00 CEST)

         c.  Thursday September 19, 2019 during 8-10 am PDT (17:00-19:00 CEST)

 

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

 

[2] References

 

[3] Timeline



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