RE: Agenda for OData TC meeting on 2020-02-13

[‎13.‎02.‎2020 17:03]

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

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

[‎13.‎02.‎2020 17:03]

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

[‎13.‎02.‎2020 17:04]

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

[‎13.‎02.‎2020 17:04]

Achieved quorum: yes

[‎13.‎02.‎2020 17:05]

2. Approve agenda [8:05 am]

Add pull request: https://github.com/oasis-tcs/odata-vocabularies/pull/66

[‎13.‎02.‎2020 17:06]

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

a. Minutes from February 06, 2020 TC meeting: https://www.oasis-open.org/committees/download.php/66654/Minutes%20of%202020-02-06%20Meeting%20%23283.docx

[‎13.‎02.‎2020 17:06]

Minutes are approved

[‎13.‎02.‎2020 17:07]

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 – 2020-06-30

ii. #0037 Concept for binary data format – Hubert Heijkers – 2020-06-30

iii. #0040 Register Repeatability headers with IANA – Mark Biamonte – 2020-03-31

[‎13.‎02.‎2020 17:07]

iii. Registration request document sent of to Chet Ensign

[‎13.‎02.‎2020 17:07]

He has to check whether a Committee Note is sufficient for registration with IANA

[‎13.‎02.‎2020 17:07]

5. Vocabularies: Release 4.0 [8:20 am]

a. Draft Release

i. https://github.com/oasis-tcs/odata-vocabularies/releases/tag/untagged-9f4b21323fd08002db47

b. Example Release in forked repository

i. https://github.com/ralfhandl/odata-vocabularies/releases

[‎13.‎02.‎2020 17:08]

Version 4.0 Errata 03

ralfhandl drafted this 10 days ago

This release consists of the vocabulary versions in this repository that most closely resemble the snapshot published with OData Version 4.0 plus Errata 03.

The actual vocabulary revisions comprising OData Version 4.0 plus Errata 03 are available at http://docs.oasis-open.org/odata/odata/v4.0/errata03/os/complete/vocabularies/

[‎13.‎02.‎2020 17:09]

https://github.com/oasis-tcs/odata-vocabularies/tags

[‎13.‎02.‎2020 17:15] Mike Pizzo:

I move we publish the first release of our 4.0 vocabularies.

[‎13.‎02.‎2020 17:15] Mark Biamonte:

I second

[‎13.‎02.‎2020 17:15]

No objection, motion passes

https://github.com/oasis-tcs/odata-vocabularies/releases

[‎13.‎02.‎2020 17:16]

6. Issues [8:30 am]

a. APPLIED

i. ODATA-1275 Describe structure of "JSON properties"

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

[‎13.‎02.‎2020 17:19] Ericson, George:

Motion to approve and close OData-1275 as applied.

[‎13.‎02.‎2020 17:20] Mike Pizzo:

I second

[‎13.‎02.‎2020 17:20]

Motion passes

[‎13.‎02.‎2020 17:20]

b. Vocabularies: NEW or OPEN with concrete proposal

i. ODATA-1355 Generalize Validation.Minimum and Validation.Maximum to Edm.PrimitiveType

[‎13.‎02.‎2020 17:21]

ODATA-1355 is OPEN

[‎13.‎02.‎2020 17:32]

https://docs.oasis-open.org/odata/odata-csdl-xml/v4.01/odata-csdl-xml-v4.01.html#sec_UnderlyingPrimitiveType

[‎13.‎02.‎2020 17:32]

For a type definition with underlying type Edm.PrimitiveType no facets are applicable, neither in the definition itself nor when the type definition is used, and these should be ignored by the client.

[‎13.‎02.‎2020 17:35] Mike Pizzo:

I move to resolve ODATA-1335 as proposed.

[‎13.‎02.‎2020 17:36] Ericson, George:

I second

[‎13.‎02.‎2020 17:39] Mike Pizzo:

I move to accept the application of ODATA-1335 in https://github.com/oasis-tcs/odata-vocabularies/pull/65/files and close ODATA-1335 as applied.

[‎13.‎02.‎2020 17:39]

ODATA-1335 is RESOLVED as proposed

[‎13.‎02.‎2020 17:40] Mike Pizzo:

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

[‎13.‎02.‎2020 17:40] Ericson, George:

I second

[‎13.‎02.‎2020 17:40]

No objections, motion passes

[‎13.‎02.‎2020 17:41]

ii. ODATA-1300 Capabilities: clarify CountRestrictions and ExpandRestrictions

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

[‎13.‎02.‎2020 17:48] Ericson, George:

Motion to resolve ODATA-1300 as proposed.

[‎13.‎02.‎2020 17:48] Krause, Gerald:

I second

[‎13.‎02.‎2020 17:48]

ODATA-1300 is RESOLVED as proposed

[‎13.‎02.‎2020 17:49] Mike Pizzo:

I move to accept the application of ODATA-1300 in https://github.com/oasis-tcs/odata-vocabularies/pull/65/files and close ODATA-1300 as applied.

[‎13.‎02.‎2020 17:49] Krause, Gerald:

I second

[‎13.‎02.‎2020 17:49]

No objections, motion passes

[‎13.‎02.‎2020 17:58]

https://github.com/oasis-tcs/odata-vocabularies/pull/66

[‎13.‎02.‎2020 17:59] Mike Pizzo:

I move we approve and merge the changes in
https://github.com/oasis-tcs/odata-vocabularies/pull/66.

[‎13.‎02.‎2020 17:59] Krause, Gerald:

I second

[‎13.‎02.‎2020 17:59]

No objections, motion passes

[‎13.‎02.‎2020 18:00]

c. V4.01: NEW or OPEN

i. ODATA-1353 Clarity for "@odata.type" in request payloads

[‎13.‎02.‎2020 18:01]

ODATA-1353 is OPEN

[‎13.‎02.‎2020 18:03] Ericson, George:

Motion to resolve ODATA-1353 as proposed.

[‎13.‎02.‎2020 18:04] Mike Pizzo:

I second

[‎13.‎02.‎2020 18:04]

ODATA-1353 is RESOLVED as proposed

[‎13.‎02.‎2020 18:04]

d. V4.02: NEW or OPEN with concrete proposal

i. ODATA-1354 Add support for SoundsLike expressions

[‎13.‎02.‎2020 18:10] Stefan:

For german https://en.wikipedia.org/wiki/Cologne_phonetics ;)

[‎13.‎02.‎2020 18:12]

ODATA-1354 is OPEN

[‎13.‎02.‎2020 18:17]

7. REST Profile for OData [8:55 am]

a. Brainstorming

i. How to name it?

ii. How to publish it?

iii. Poster services and tools?

iv. What is the MVP to launch?

v. What experiences/tools do we need to make the right first impression?

[‎13.‎02.‎2020 18:17] Mike Pizzo:

Some suggested names:
• "REST API for Data" ("Rapid")
• "Simple Query Rest API" (SQRAPI "scrappy")
• "Simple Open API" (SOAPI "soapy")
• "Simple OpenData Api for REST ("SOAR")
• "Modern Open Data Api Language" (MODAL)
• "Open Data API Profile" (ODAP)
• "Data API" (DAPI)
• "Profile for OpenData" (POD)
• RESTQ ("Rescue") (RESQ?)
• SODA ("Simple Open Data API") (taken for dog rescue)
• "Simple Query Open Protocol" (SQOP "scope")
• RESTQPRO ("Rescue Pro") (Rest Query Profile)
• RESTFull/RESTFul
• Quest (Qu[ery] + [R]EST) (taken)
• SQRL ("Squirrel") Simple Query REST Language (taken by Secure, Quick, Reliable Login)
• "Simple ? API" SNAPI "snappy"
• RESTPro, REST-P
• REST-EZ, EZ-REST
• ORQL (Open REST Query Language)
• OGL (Open/OData Graph Language)
• RGL (REST Graph Language)
• RestQuery
• QREST ("crest")
• DataREST
• REST-D
• 4REST/ForREST/FoREST
• Data4REST ("Data forest")
• Open4REST ("Open forest")
• RDQL
• EzApi
• Q-EZ (Query Easy -- "Queasy")
• EZ-Q (Easy Query)
• LogiQL
• RESTable
• IQL
• CloudQL
• 4RESTQL ("forest-QL")

[‎13.‎02.‎2020 18:20] Stefan:

SODA is favorite of Stefan too

[‎13.‎02.‎2020 18:20]

Mine, too

[‎13.‎02.‎2020 18:22] Ramesh Reddy:

[‎13.‎02.‎2020 18:22] Mike Pizzo:

SODA ("Simple Open Data API")

[‎13.‎02.‎2020 18:24]

No Title

b. OASIS Open Repositories

i. https://www.oasis-open.org/resources/open-repositories

1. initiated by a TC, initially maintained by TC members, may survive the initiating TC

2. available at https://github.com/oasis-open/odata-xxx - name MUST start with TC shortname

a. Example: https://github.com/oasis-open/cti-stix-visualization

3. anyone can contribute who has signed a CLA – in contrast to TC repos at https://github.com/oasis-tcs, where only TC members can contribute

4. uses Open Source license, e.g. Apache 2.0, different from TC IPR policy (in our case: RF on RAND)

[‎13.‎02.‎2020 18:26]

c. OASIS Open Projects

i. https://oasis-open-projects.org/projects/

1. similar to a TC, geared towards producing software, with Project Governing Board, Technical Steering Committee, Marketing Group, chairs, maintainers, …

2. needs one or more sponsor organizations, e.g. IBM, MSFT, SAP would have to pay minimum USD 25.000 annually

[‎13.‎02.‎2020 18:32] Stefan:

Stefan also in favor of open repos

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.

[‎13.‎02.‎2020 18:34] Stefan:

I second

[‎13.‎02.‎2020 18:36]

https://www.oasis-open.org/resources/open-repositories/cla/individual-cla

https://www.oasis-open.org/resources/open-repositories/cla/entity-cla

[‎13.‎02.‎2020 18:39]

Mike to check with Chet whether open repositories can be set up "hidden" until they have interesting content

[‎13.‎02.‎2020 18:39]

iii. Poster services and tools?

[‎13.‎02.‎2020 18:39]

Repositories

[‎13.‎02.‎2020 18:39]

odata-soda as a master repo

[‎13.‎02.‎2020 18:41]

Or rather smaller repos, odata-soda-validator, odata-soda-cool-tool, ...

[‎13.‎02.‎2020 18:41]

https://oasis-open.github.io/cti-stix-visualization/

[‎13.‎02.‎2020 18:44]

Mike to check with Chet whether we can have a "vanity URL" for the github pages site of an open repository

[‎13.‎02.‎2020 18:48]

https://oasis-tcs.github.io/odata-vocabularies/

[‎13.‎02.‎2020 18:50] Mike Pizzo:

main repo: https://github.com/oasis-open/odata-soda

[‎13.‎02.‎2020 18:51] Mike Pizzo:

SODA-API.org as vanity?

[‎13.‎02.‎2020 18:52]

https://github.com/oasis-open/cti-taxii-server

[‎13.‎02.‎2020 18:52]

https://medallion.readthedocs.io/

[‎13.‎02.‎2020 18:52] Stefan:

soda.dev ?

Not connected

So ...

[‎13.‎02.‎2020 18:53] Mike Pizzo:

or soda.net?

[‎13.‎02.‎2020 18:54]

soda.dev

[‎13.‎02.‎2020 18:55]

https://domains.google/tld/dev/

[‎13.‎02.‎2020 18:58]

http://soda.net/

[‎13.‎02.‎2020 19:00]

8. Next meetings [9:50 am]

a. Thursday February 20, 2020 during 8-10 am PST (17:00-19:00 CET)

[‎13.‎02.‎2020 19:00]

Mike can't attend

[‎13.‎02.‎2020 19:01]

b. Thursday February 27, 2020 during 8-10 am PST (17:00-19:00 CET)

[‎13.‎02.‎2020 19:01]

Mike will moderate, Ralf can't attend

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

[‎13.‎02.‎2020 19:01]

Meeting is adjourned

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

From: odata@lists.oasis-open.org <odata@lists.oasis-open.org> On Behalf Of Handl, Ralf
Sent: Mittwoch, 12. Februar 2020 17:22
To: odata@lists.oasis-open.org
Subject: [CAUTION] [odata] Agenda for OData TC meeting on 2020-02-13

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=49708

2. Approve agenda [8:05 am]

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

a. Minutes from February 06, 2020 TC meeting: https://www.oasis-open.org/committees/download.php/66654/Minutes%20of%202020-02-06%20Meeting%20%23283.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 – 2020-06-30

ii. #0037 Concept for binary data format – Hubert Heijkers – 2020-06-30

iii. #0040 Register Repeatability headers with IANA – Mark Biamonte – 2020-03-31

5. Vocabularies: Release 4.0 [8:20 am]

a. Draft Release

i. https://github.com/oasis-tcs/odata-vocabularies/releases/tag/untagged-9f4b21323fd08002db47

b. Example Release in forked repository

i. https://github.com/ralfhandl/odata-vocabularies/releases

6. Issues [8:30 am]

a. APPLIED

i. ODATA-1275 Describe structure of "JSON properties"

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

b. Vocabularies: NEW or OPEN with concrete proposal

i. ODATA-1355 Generalize Validation.Minimum and Validation.Maximum to Edm.PrimitiveType

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

ii. ODATA-1300 Capabilities: clarify CountRestrictions and ExpandRestrictions

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

c. V4.01: NEW or OPEN

i. ODATA-1353 Clarity for "@odata.type" in request payloads

d. V4.02: NEW or OPEN with concrete proposal

i. ODATA-1354 Add support for SoundsLike expressions

7. REST Profile for OData [8:55 am]

a. Brainstorming

i. How to name it?

ii. How to publish it?

iii. Poster services and tools?

iv. What is the MVP to launch?

v. What experiences/tools do we need to make the right first impression?

b. OASIS Open Repositories

i. https://www.oasis-open.org/resources/open-repositories

1. initiated by a TC, initially maintained by TC members, may survive the initiating TC

2. available at https://github.com/oasis-open/odata-xxx - name MUST start with TC shortname

a. Example: https://github.com/oasis-open/cti-stix-visualization

3. anyone can contribute who has signed a CLA – in contrast to TC repos at https://github.com/oasis-tcs, where only TC members can contribute

4. uses Open Source license, e.g. Apache 2.0, different from TC IPR policy (in our case: RF on RAND)

c. OASIS Open Projects

i. https://oasis-open-projects.org/projects/

1. similar to a TC, geared towards producing software, with Project Governing Board, Technical Steering Committee, Marketing Group, chairs, maintainers, …

2. needs one or more sponsor organizations, e.g. IBM, MSFT, SAP would have to pay minimum USD 25.000 annually

8. Next meetings [9:50 am]

a. Thursday February 20, 2020 during 8-10 am PST (17:00-19:00 CET)

a. Thursday February 27, 2020 during 8-10 am PST (17:00-19:00 CET)

a. Thursday March 05, 2020 during 8-10 am PST (17:00-19:00 CET)

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

[2] References

Conference call, Chat & 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/66650/TC-Timeline-2020-02-05.docx

odata message