-
Notifications
You must be signed in to change notification settings - Fork 4
Meetings 2019 2020
Peter Van den Bosch edited this page Dec 1, 2020
·
2 revisions
Meetings of 2019-2020 (most recent first):
- Validation of agenda
- Current WG status:
- number of open issues (11 -> 9) vs backlog (13 -> 13)
- styleguide updates: 2 new updates published on 09/09/2020 and 04/11/2020
- data types:
- added health check types (openapi-common)
- Gender -> GenderCode (openapi-person-v2)
- Promoted to stable: BelgianRegionCode, MunicipalityCode, Year
- Belgian API community: https://apicommunity.be/
- Overview of new issues (3):
- Issues to discuss:
- #27 publish gCloud common JSON schemas - Peter
- #19 REST companies example API (status update) – Willem
- #69 combining query parameters with AND/OR - Willem
- #39 problem code - Peter
- #36 standardized problem types for all http status codes - Peter
- gCloud schemas for common business data and #60 integer vs. string - Peter
- #25 swagger tooling
- #67 representing unexpected failures and trace IDs in OpenAPI - Peter
- next meeting: 25/2/2021
- Validation of agenda
- Current WG status:
- issue numbers
- 2 new issues
- 24 open issues rest-guide ; 11 in progress
- 11 open issues openapi schemas
- styleguide: new version was published on 3/8
- issue numbers
- review organization of WG
- Overview of new issues:
- Issues to discuss:
- #27 publish gCloud common JSON schemas - Peter
- #19 REST companies example API (status update) – Willem
- #65 removing selection of items from a collection - Chrysa
- #40 update tables with http status codes and verbs - Chrysa
- #13 health check – Willem
- #24 Notifications - Virginie
- #39 problem code
- #36 standardized problem types for all http status codes
- #26 gCloud schemas for common business data and #60 integer vs. string - Peter
- #25 swagger tooling
- next meeting: 4/11 14h-16h
- Validation of agenda
- Current WG status:
- 4 new issue, 1 closed
- 24 open issues, from which 12 are in progress
- styleguide updates:
- data type changes (see #26): YearMonth promoted to stable
- change status codes to string types in OpenAPI examples
- Add Apache License 2.0 to source code
- Overview of new issues:
- Issues discussed:
- #27 publish gCloud common JSON schemas - Peter
- #54 compare and reconcile belgif and Flanders REST guidelines – Bert
- #19 REST companies example API (status update) – Willem
- #13 health check – Willem
-
#25 swagger tooling and #34 styleguide validation tool
- #34 was moved from "in progress" to backlog
- #26 gCloud schemas for common business data and #60 integer vs. string - Peter
- Postponed to next meeting due to lack of time:
- next meeting: 9/9 14h-16h
- Validation of agenda
- Current WG status:
- 1 new issue, 2 closed
- 22 open issues, from which 9 are in progress
- styleguide updates:
- add references to GitHub project
- data type changes (see #26)
- Overview of new issues:
- #55 allow OpenAPI 3.0
- Issues discussed:
- #55 allow OpenAPI 3.0 - Peter
- #19 REST companies example API (status update) – Willem => no news
- #27 publish gCloud common JSON schemas - Peter
- #33 DigiPolis REST guide and #54 compare and reconcile belgif and Flanders REST guidelines – Bert
- #13 health check – Willem
- #25 swagger tooling and #34 styleguide validation rules
- #39 problem code
- #26 gCloud schemas for common business data - Peter
- next meeting: 27/5 14h-16h
- Current WG status:
- 23 issues, from which 8 in progress
- styleguide update published 10/1/2020
- moved to github
- 13 data types were promoted to stable
- Validation of agenda
- Overview of new issues:
- Issues discussed:
- #45 brief overview of FHIR standards – Virginie
- #19 REST companies example API (status update: no progress yet) – Willem
- #33 DigiPolis REST guide (status update) – Bert
- #35 styleguide, schemas and vocabularies platforms & #27 publish gCloud common JSON schemas - Peter
- #13 health check – Willem
- #25 swagger tooling
- #34 styleguide validation rules
- Postponed to next meeting:
- #39 problem code
- next meeting: 25/3 14h-16h
- Welcome and WG organization
- New participants: Wallonia, Flanders, Brussels, SFPD
- WG organization: see ppt and wiki page
- Overview of feedback on [email protected]
- Unpublished changes to guide were reviewed
- updated rules: naming of JSON properties and naming of JSON data types: no digits as first letter and no dots in names
- added 413 Payload Too Large to list of HTTP status codes
- updated Resource URI notation rule: no trailing slashes in URIs
- added rule: default values in OpenAPI specification
- added Controller resource archetype and move all archetypes to Resources chapter
- Overview of new issues: #36 -> #45
- Issues discussed (see GitHub issues for more info):
- #35 styleguide, schemas and vocabularies platforms - Move to GitHub belgif approved. GitLab only for automated builds.
- #19 – REST companies example API – a Smals developer will work on this. Estimated in about 2 months
- #33 – DigiPolis REST guide. Comparison was made which led to some updates in gCloud guide or new work items. But incompatibilities remain. Informatie Vlaanderen will contact DigiPolis to raise awareness of gCloud REST guide + comparison. A new issue was created to attempt reconciliation of gCloud and Informatie Vlaanderen guides (#54)
- Issue #47 has been created to resolve conflicts between gcloud REST and ICEG URI standards
- #26 gCloud schemas for common business data (Peter)
- Many types graduated from beta to stable status
- We should find a way to link from Swagger data types to full descriptions of concepts (output of functional or ICEG workgroups, or other existing standards) => issue #46 created
- Postponed to next meeting:
- #25 swagger tooling
- #34 styleguide validation rules
- #13 health check – Willem
- #45 brief overview of FHIR standards – Virginie
Tasks:
- styleguide updates:
- issue preparation:
- #3 non-CRUD actions/controller resources - reopened issue => prepare feedback (all)
- #33 comparison with Digipolis style guide => prepare feedback (all)
- #27 publishing of JSON schemas: using links vs artifactory? => feedback (all)
- #19 REST companies mock API => add as new git project (Willem), prepare review (all)
- #25 swagger tooling: pros/cons of openapi-generator vs swagger-toolgen
- sharing of Smals extensions for maven code generation plugin (Willem)
Agenda:
- status of tasks
- followup on evolution of:
- #3 non-CRUD actions/controller reosurces
- #33 comparison with Digipolis style guide
- #25 swagger tooling
- #26 gCloud schemas for common business data (Peter)
- #27 publishing of JSON schemas – create maven artifacts (Peter)
- #19 review REST companies mock API (Willem)
- next meeting: agenda + date
Tasks:
- styleguide updates:
- #18 (Steve) – query parameters
- #13 (Willem) – monitoring
- #23 (Willem) - error handling
- #28 (Peter) - various styleguide updates based on review of eHealth pilot APIs
- issue preparation:
- #19 REST companies mock API => add as new git project (Willem), prepare review (all)
- #27 publishing of JSON schemas: using links vs artifactory? => feedback (all)
- #3 non-CRUD actions/controller resources - reopened issue => prepare feedback (all)
- #25 swagger tooling: pros/cons of openapi-generator vs swagger-toolgen
- #22 styleguide validation tool: create first beta release (Willem)
- sharing of Smals extensions for maven code generation plugin (Willem)
Agenda:
- status of tasks
- followup on evolution of:
- #22 styleguide validation tool: status of implementation
- #25 swagger tooling
- #26 gCloud schemas for common business data (Peter)
- #27 publishing of JSON schemas – create maven artifacts (Peter)
- #19 review REST companies mock API (Willem)
- next meeting: agenda + date
Tasks:
- styleguide updates:
- #18 (Steve) – query parameters
- #13 (Willem) – monitoring
- #30 (Peter) – retrieve partial resource (fields/select)
- Review pilot APIs, to be uploaded then reviewed by all:
- REST companies mock API #19 => as new git project (Willem)
- eHealth keys API => attach to issue #28 (Virginie)
- issue preparation:
- #24 notifications and REST (Willem)
- #23 error handling (Willem)
- #27 publishing of JSON schemas – create maven artifacts (Peter)
Agenda:
- review eHealth pilot APIs: #28 (Virginie, Hannes)
- ehBox
- etkdepot
- status of tasks
- new styleguide published for #30 and previously discussed issues
- Willem and Steve's issues remain TODO. Discussion of #23, #19 postponed to meeting+1, #24 to meeting+2
- Vlaanderen: will provide feedback on REST styleguide, comparing with DigiPolis Antwerpen
- followup on evolution of:
- #22 styleguide validation tool: status of implementation
- #25 swagger tooling
- #26 gCloud schemas for common business data (Peter)
- #27 publishing of JSON schemas – create maven artifacts (Peter)
- next meeting: agenda + date
Tasks:
- styleguide updates:
- #18 (Steve) – query parameters
- #13 (Willem) – monitoring
- #29 (Peter) – organization of JSON Schema files
- #21 (Peter) – trace id
- Review pilot APIs (all), to be uploaded:
- REST mock API => attach to issue #19 or in git (Willem)
- eHealth keys(?) API => attach to issue #28 (Virginie)
- check for “fields” query param documentation (Peter)
- preparation of issues on agenda => owner + all
Agenda:
- status of tasks:
- monitoring: some additional changes discussed before merging into styleguide
- discuss and decide on issues:
- #26 gCloud schemas for common business data (Peter): presented, continued next time
- #28 and #19: review pilot APIs (Willem, Virginie): eHealth keys API presented, continued next time
- #24 notifications and REST (Willem): postponed
- #23 error handling: postponed
- followup on evolution of:
- #22 styleguide validation tool: status of implementation
- #25 swagger tooling: some updates, to be included in styleguide
- #27 publishing of JSON schemas
- any progress on other issues; any new issues?
- next meeting: agenda + date