RE: Agenda for OData TC meeting on 2019-10-10

[‎10.‎10.‎2019 17:03]

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

[‎10.‎10.‎2019 17:03]

Voting Members: 4 of 9 (44%) (used for quorum calculation)

[‎10.‎10.‎2019 17:04]

Voting Members: 5 of 9 (55%) (used for quorum calculation)

[‎10.‎10.‎2019 17:04]

Quorum achieved: yes

[‎10.‎10.‎2019 17:04]

2. Approve agenda [8:05 am]

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

3. Approve minutes from previous meeting(s)

a. Minutes from September September 26, 2019 TC meeting: https://www.oasis-open.org/committees/download.php/65969/Minutes%20of%202019-09-26%20Meeting%20%23269.docx

[‎10.‎10.‎2019 17:09]

Minutes are approved

[‎10.‎10.‎2019 17:09]

No Title

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

[‎10.‎10.‎2019 17:12]

i. Won't happen this year, Hubert to set new date

[‎10.‎10.‎2019 17:12]

iii. Mark and Mike working on a reply to the IANA comments

[‎10.‎10.‎2019 17:12]

5. Repeatable Requests [8:20 am]

a. Document Walkthrough

i. https://www.oasis-open.org/committees/download.php/65983/repeatable-requests-v1.0-wd01-2019-09-27.docx

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.

[‎10.‎10.‎2019 17:22] Mike Pizzo:

I don't think it's legal to $select control information like @Core.ContentID, that may be represented differently in different formats (and would not want to encourage that pattern if it was supported). I would prefer instead to say that the @Core.ContentID is always returned if specified in the request.

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.

[‎10.‎10.‎2019 17:54] Mike Pizzo:

Need to spell out behavior of repeatable requests that are members of an atomicity group, are dependent on other requests, or have other requests dependent upon them.

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

Matt will follow up with Evan and present the next iteration next week

[‎10.‎10.‎2019 18:02]

Postpone #6 after #7 Isszues

[‎10.‎10.‎2019 18:02]

No Title

7. Issues [9:40 am]

a. APPLIED

i. None

b. V4.01: NEW or OPEN

i. ODATA-1335 ABNF Does not allow selecting instance annotations

ii. ODATA-1333 Add Terms, Abbreviated Terms, and Symbols sections to specifications

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

i. ODATA-1335 ABNF Does not allow selecting instance annotations

[‎10.‎10.‎2019 18:05]

http://docs.oasis-open.org/odata/odata/v4.01/csprd05/part2-url-conventions/odata-v4.01-csprd05-part2-url-conventions.html#_Toc14103726

[‎10.‎10.‎2019 18:06] Mike Pizzo:

The $select system query option allows clients to request a specific set of properties for each entity or complex type.
The $select query option is often used in conjunction with the $expand system query option, to define the extent of the resource graph to return ($expand) and then specify a subset of properties for each resource in the graph ($select). Expanded navigation properties MUST be returned, even if they are not specified in $select.
The [OData-ABNF] select syntax rule defines the formal grammar of the $select query option.
The value of $select is a comma-separated list of select items. Each select item is one of the following:
· a path, to include a property,
· a star (*), to include all declared or dynamic properties of the type, or
· a qualified schema name followed by a dot (.) followed by a star (*) to request all applicable actions or functions from that schema
A path consists of segments separated by a forward slash (/). Segments are either names of single- or collection-valued complex properties, instance annotations, or type-cast segments consisting of the qualified name of a structured type that is derived from the type identified by the preceding path segment to reach properties defined on the derived type.
A path can end with
· the name of a property or non-entity-valued instance annotation of the identified structured instance,
· the qualified name of a bound action,
· the qualified name of a bound function to include all matching overloads, or
· the qualified name of a bound function followed by parentheses containing the comma-separated lists of non-binding parameters identifying a single overload.

[‎10.‎10.‎2019 18:08] Mike Pizzo:

ODATA-1335 closed without ation by submitter.

[‎10.‎10.‎2019 18:08]

ii. ODATA-1333 Add Terms, Abbreviated Terms, and Symbols sections to specifications

[‎10.‎10.‎2019 18:08] Mike Pizzo:

(previous ODATA-1335 closed without action by submitter)

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.

[‎10.‎10.‎2019 18:22]

https://issues.oasis-open.org/browse/ODATA-1327

[‎10.‎10.‎2019 18:23] Ericson, George:

Note: OData_Dictionary introduced

[‎10.‎10.‎2019 18:23]

Extend applicability of Core.MediaType and Core.AcceptableMediaTypes to non-stream (string/binary) properties and terms

[‎10.‎10.‎2019 18:24]

Missed extending the AppliesTo to allow MediaType / AcceptableMediaTypes to be applied to Term elements.

[‎10.‎10.‎2019 18:27] Ericson, George:

Move to resolve ODATA 1327 as proposed and to merge the pull request.

[‎10.‎10.‎2019 18:27] Borges, Matt:

I second

[‎10.‎10.‎2019 18:27]

ODATA-1327 is RESOLVED as proposed

[‎10.‎10.‎2019 18:28] Ericson, George:

Move to close ODATA 1327 as applied.

[‎10.‎10.‎2019 18:28] Borges, Matt:

I second

[‎10.‎10.‎2019 18:28] Mike Pizzo:

I second

[‎10.‎10.‎2019 18:29]

ODATA-1327 is CLOSED as applied

[‎10.‎10.‎2019 18:32]

6. Use of new Github “landing repo” [9:20 am]

a. Repo URL

i. https://github.com/oasis-tcs/odata

b. Open questions

i. Section “Further Description of this Repository”: who wants to craft a proposal?

ii. GitHub Pages: full master branch or just /docs folder?

iii. Directory structure and initial content

[‎10.‎10.‎2019 18:33]

6.b.i proposed content

[‎10.‎10.‎2019 18:34]

- links to our other repos

[‎10.‎10.‎2019 18:34]

- description of the directory structure

[‎10.‎10.‎2019 18:34]

- guidelines for use in this repo

[‎10.‎10.‎2019 18:37]

- guideline for lifecycle and labelling of Github issues in this project - issues only for things in this repo

[‎10.‎10.‎2019 18:38]

Content proposals

[‎10.‎10.‎2019 18:39]

- one-pagers for specific topics (server-driven paging, media entities versus stream properties)

[‎10.‎10.‎2019 18:39]

- FAQ

[‎10.‎10.‎2019 18:48]

ii. GitHub Pages: full master branch or just /docs folder?

[‎10.‎10.‎2019 18:49]

Proposal: use /docs folder of master branch

[‎10.‎10.‎2019 18:50]

No objections

[‎10.‎10.‎2019 18:50]

iii. Directory structure and initial content

[‎10.‎10.‎2019 18:52]

Ralf to find out whether all content on Github Pages needs to be under /docs or whether it can reference stuff from sibling directories

[‎10.‎10.‎2019 18:53]

e.g. can master/docs/README.md reference/link to master/something/foo.md

[‎10.‎10.‎2019 18:54]

depending on this have folders under /docs or directly on root

[‎10.‎10.‎2019 18:54]

Folders

[‎10.‎10.‎2019 18:54]

/dictionary

[‎10.‎10.‎2019 18:54]

/FAQ

[‎10.‎10.‎2019 18:54]

/one-pager

[‎10.‎10.‎2019 18:56]

Discussion on /dictionary versus /glossary

[‎10.‎10.‎2019 18:58]

8. Next meetings [9:50 am]

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

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

c. Thursday October 31, 2019 during 8-10 am PDT (16:00-18:00 CEST) – one hour earlier in Europe!

[‎10.‎10.‎2019 18:59]

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

[‎10.‎10.‎2019 19:00]

Hierarchies as topic for next week

[‎10.‎10.‎2019 19:00]

Meeting is adjourned

From: odata@lists.oasis-open.org <odata@lists.oasis-open.org> On Behalf Of Handl, Ralf
Sent: Dienstag, 8. Oktober 2019 10:26
To: odata@lists.oasis-open.org
Subject: [CAUTION] [odata] Agenda for OData TC meeting on 2019-10-10