Skip to content

Meetings 2021 2022

Peter Van den Bosch edited this page Jun 20, 2023 · 1 revision

Meeting 2022-12-06

  • Current WG status:
    • number of open issues: 24 (1 closed, 1 opened)
    • styleguide and openapi schemas updates
      • updated guide published with #92
      • openapi-problem 1.3.0 released with InputValidationProblemResponse
  • WG Communication:
    • PR #99 with typo fix
    • issue #98 on special chars in sorting parameter values
  • experiences with applying REST guide within organization
  • review of pull requests:
    • PR approved for #96 don't require authN/authZ for swagger/openapi access
    • PR approved for #67 representing non-API-specific problems and trace IDs in OpenAPI
  • Closed issues
    • #92 Allow response body for resource creation
  • Issues discussed:
    • #34 styleguide compliance validator - status update
    • #94 Naming convention for codes
    • #98 special chars in sorting parameter values
  • next meeting: 2023-02-15

Meeting 2022-10-26

  • Validation of agenda
  • Current WG status:
    • number of open issues: 24 (1 closed, 1 opened)
    • styleguide and openapi schemas updates
      • openapi-problem/openapi-common with doc href links to belgif.be
      • openapi-organization-identifier and openapi-employment-identifier
  • WG communication:
    • PSD2 financial standards: some banks define APIs with money as string (like openapi-money), some as number. The PSD2 standard doesn't define types.
  • review of pull requests:
    • validated openapi-problem PR6 Add a problem response type for InputValidationProblem
    • validated PR95 Allow response body for resource creation
  • Overview of new issues
    • #96 don't require authN/authZ for swagger/openapi access
  • Closed issues:
    • #91 move REST guide to belgif.be - completed
  • Issues discussed:
    • #96 don't require authN/authZ for swagger/openapi access
    • #34 styleguide compliance validator
    • #67 representing non-API-specific problems and trace IDs in OpenAPI
  • Postponed: #94 Naming convention for codes
  • next meeting: date and issues to discuss

Meeting 2022-06-15

  • Validation of agenda
  • Current WG status:
    • number of open issues
    • styleguide and openapi schemas updates
  • review of pull requests:
    • #92 Create resource: allow returning resource representation (PR #95)
  • Overview of new issues
    • SocSec defined standards for history, locks, bookmarks. Do we review them and add to G-Cloud standards?
  • Issues to discuss:
    • #91 move REST guide to belgif.be
    • #34 styleguide compliance validator
    • #94 Naming convention for codes
  • next meeting: date and issues to discuss

Meeting 2022-03-30

  • Validation of agenda
  • Current WG status:
    • number of open issues: 30 (4 new, 3 closed)
    • styleguide updates: new version published 2022-01-12
  • pull requests were reviewed and approved:
    • #74 problem response for (non-schema) input validation - Peter
    • #79 decimal numbers - Peter
      • openapi-problem #4: add type for input validation problem
    • #70 interpretation of query parameters - approved with small changes
  • Overview of new issues:
    • #89 track OpenAPI 3.1 support in tooling (backlog)
    • #91 move REST guide to belgif.be
    • #92 Create resource: allow returning resource representation
    • #94 Naming convention for codes
  • Review of openapi types: openapi-money approved (published), others approved, but pending validation of functional WG
  • Issues discussed:
    • #91 move REST guide to belgif.be
    • #92 Create resource: allow returning resource representation
    • #34 styleguide compliance validator
  • next meeting: scheduled June 16th

Meeting 2022-01-12

  • Validation of agenda
  • Current WG status:
    • number of open issues -> postponed
    • styleguide and openapi schemas updates
      • deprecation of CbeNumber
  • Review of pull requests
    • #84 identifiers (PR for #60 numerical identifiers and #81 designing resource identifiers)
    • #74 problem response for (non-schema) input validation => new version next meeting
    • #86 representing deprecation in different OpenAPI versions
    • #88 Support OpenAPI 3.0 throughout the guide
  • Overview of new issues
  • Issues to discuss:
    • #19 REST companies example API (status update) => postponed
    • #70 interpretation of query parameters (split from #69) - Willem => postponed
    • #25 swagger tooling (status update)
    • #79 decimal numbers - Peter
  • next meeting: 16/3

Meeting 2021-10-20

  • Validation of agenda
  • Current WG status:
    • number of open issues
    • styleguide and openapi schemas updates
  • Review of pull requests
    • #83 problem type for 503 - Service Unavailable
    • #60 numerical identifiers
    • #81 designing resource identifiers
  • Overview of new issues
  • Issues to discuss:
    • #19 REST companies example API (status update)
    • #70 interpretation of query parameters (split from #69) - Willem
    • #25 swagger tooling (status update)
    • #74 problem response for (non-schema) input validation - Peter
  • next meeting: date and issues to discuss

Meeting 2021-09-08

  • Validation of agenda
  • Current WG status:
    • number of open issues: 27 (+1), 9 in progress, 18 on backlog; 3 new, 1 closed
    • styleguide updates: new version was published 2021-06-25
  • Overview of new issues:
    • #81 designing resource identifiers - split from #60
    • #82 create belgif-openapi-bom
    • #83 problem type for 503 - Service Unavailable
  • Issues discussed:
    • #83 problem type for 503 - Service Unavailable
    • #25 swagger tooling (status update)
    • #60 numerical identifiers
    • #81 designing resource identifiers
    • #19 REST companies example API (status update)
    • #70 interpretation of query parameters - Willem
  • next meeting: 2021-10-20

Meeting 2021-06-23

  • Validation of agenda
  • REST standards on ReUse website
  • Current WG status:
    • number of open issues: 26 (=), 9 in progress, 17 on backlog
  • new issues: none
  • review of (unpublished) styleguide changes: problem type identifiers #39, charset guidelines #75
  • Issues discussed:
    • #60 numerical identifiers
  • next meeting: 2021-09-08

Meeting 2021-04-28

  • Validation of agenda
  • REST standards presentation - feedback
  • Current WG status:
    • number of open issues: 26 (+1), 9 in progress, 17 on backlog
    • styleguide updates (not yet published - $ref values fixed and StopLight not open-source)
    • data types: new issue on Money type
  • Overview of new issues:
    • #79 decimal numbers
    • #78 fix of $ref example values
  • Issues discussed:
    • #75 consistent use of charset in all JSON media types - PR #77 - Peter
    • #39 problem type identifier - conclusions - Peter
    • #60 numerical identifiers
  • next meeting: 2021-06-23

Meeting Problem Identifier 2021-03-24 (agenda)

Meeting 2021-02-25

  • Validation of agenda
  • Preparation of presentation to promote REST standards
  • OpenAPI 3.1
  • Current WG status:
    • number of open issues: 25 (+6,-3), 9 in progress, backlog 16 (+3)
    • data types: released on GitHub and Maven Central
    • styleguide update: 4 new standardized problem types
  • Overview of new issues:
    • #70 interpretation of query parameters (split from #69)
    • #72 extend missing scope problem
    • #73 document usage of select for collections
    • #74 problem response for (non-schema) input validation
    • #75 consistent use of charset in all JSON media types 
    • #76 use select also to add fields in the response, not normally returned
  • Issues discussed:
    • #19 REST companies example API (status update)
    • #39 problem type identifier - Peter
      • will be continued in separate meeting
    • #75 consistent use of charset in all JSON media types - Peter
  • Discussion postponed on:
    • #70 interpretation of query parameters (split from #69) - Willem
    • #25 swagger tooling
    • #67 representing unexpected failures and trace IDs in OpenAPI - Peter
    • #74 problem response for (non-schema) input validation - Peter
    • #60 integer vs. string and gCloud schemas for common business data - Peter
  • next meeting: date and issues to discuss