Agenda for OData TC meeting on 2020-05-14

Here [1] is a draft agenda for the OData TC (Technical Committee) meeting scheduled on Thursday May 14, 2020 during 8-10 am PDT (17:00-19:00 CEST).

For TC timeline, see [2].

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

2. Approve agenda [8:05 am]

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

a. Minutes from May 07, 2020 TC meeting: https://www.oasis-open.org/committees/download.php/67159/Minutes%20of%202020-05-07%20Meeting%20%23296.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. #0041 Create Open Repo for REST Profile – Mike Pizzo – 2020-05-04

ii. #0040 Register Repeatability headers with IANA – Mark Biamonte – 2020-05-28

iii. #0039 Concept for Compact JSON data format – Hubert Heijkers – 2020-06-30

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

5. Issues [8:20 am]

d. Vocabularies: NEW or OPEN with concrete proposal

i. ODATA-1365 Enhance Validation.AllowedValue to have optional symbolic name

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

ii. ODATA-1358 Detach textual descriptions from operation restriction terms in Capability vocabulary

e. Vocabularies: NEW or OPEN that need more discussion

i. ODATA-1336 Querying “JSON properties”

ii. ODATA-1326 Enhance syntax of term Validation.OpenPropertyTypeConstraint

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

iii. ODATA-1253 Abstract type definition Core.Number as a super-type of all numeric types

iv. ODATA-1214 Annotate constructor actions

v. ODATA-1140 Add details to HttpResponse

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

vii. ODATA-1060 Improve specification of element response requirements

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

f. Data Aggregation: NEW or OPEN

i. ODATA-1349 Calculate Custom Aggregates from Aggregated Instances

ii. ODATA-1332 Support augmenting entities with aggregated values from related entities

iii. ODATA-1218 Enhance hierarchy processing

iv. ODATA-945 Correct examples 53 and 54

6. RAPID Profile for OData [8:50 am]

a. Temporary Repo

i. https://github.com/standardapi/odata-rapid-pro

b. Request an OASIS Open Repository

i. Repository name

1. odata-rapid-pro

ii. Open Source License

1. Apache 2

iii. Purpose statement

1. Rest API Design (RAPID) Profile

RAPID is a simple profile for building well designed APIs that can scale to the level of functionality required for any situation. By following RAPID conventions, services are able to leverage common libraries and tools, and can share their information in a discoverable and interoperable way.

Because the RAPID profile is based on, and compatible with, the industry standard OData protocol, services following RAPID conventions know that, as their needs grow, there are well-defined conventions and semantics that allow them to seamlessly and incrementally grow without having to rewrite as their needs evolve.

iv. Description (fewer than 300 characters)

1. OASIS TC Open Repository: Rest API Design (RAPID) Profile

v. Initial Maintainers

1. Christof Sprenger, https://github.com/chrisspre

2. George Ericson, https://github.com/GEricson

3. Hubert Heijkers, https://github.com/Hubert-Heijkers

4. Mark Biamonte, https://github.com/markbnc

5. Michael Pizzo, https://github.com/mikepizzo

6. Ralf Handl, https://github.com/ralfhandl

7. Ramesh Reddy, https://github.com/rareddy

8. Stefan Hagen, https://github.com/sthagen

9. Wojtek Trocki, https://github.com/wtrocki